June 30, 2005 at 11:08 am
Our clients have SQL Server 7.0 Client Utilities installed. We will be upgrading to 2000 in a couple months. The server upgrade will be a snap, but how could I upgrade 200 clients without touching each one individually?
Thanks!
June 30, 2005 at 11:11 am
Generally speaking, in the absence of a software management server of some sort, you don't.
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/
June 30, 2005 at 12:54 pm
Thanks for the tip. Are there any recommendations for this type of technology (company or software)?
Not having a test environment to try this, will SQL 7.0 client talk with 2000 server?
Thanks!
June 30, 2005 at 1:47 pm
Yes a SQL 7.0 Client will talk to an SQL 2000 DB.
May have problems if server is NOT the default instance; if not default instance you need MDAC 2.6 and changes to client network configuration and client can then connect using alias.
Tim S
IIRC the SQL 7.0 EM will NOT connect to an SQL 8.0 Server.
July 1, 2005 at 9:47 am
For software updates and management I'd suggest SMS (Microsoft Systems Management Server). It allows you to inventory the environment, package updates and roll out upgrades to software.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
July 1, 2005 at 9:52 am
Well. I guess if you are admin on all client machines you could easily write a WMI script that run a SILENT install on every client machine. But I guess that would be defined under 'touching each one individually'.
July 1, 2005 at 11:47 am
I always refer to it as the "tour of the desks" when an application is installed manually, vs pushing a package out via active directory or sysinternals pstools or another management system.
Lowell
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply