August 29, 2005 at 3:15 pm
Like many Part Time DBA's my primary access to my SQL Server is via 2 primary client tools: Query Analyzer & Enterprise Manager, running on a local PC, NOT on the SQL Server.
It is a mystery to me after reading dozens of MS instructional pages regarding their SQL 2000 service packs, whether any of the typically 3 different service pack files should be installed to the client, and if so which ones.
My specific questions are:
1. Which service pack files (if any) need be installed on the client?
SP3 includes 3 files:
| • | Sql2ksp3.exe. Updates for database components. |
| • | Sql2kasp3.exe. Updates for Analysis Services components. |
| • | Sql2kdesksp3.exe. Updates for Microsoft SQL Server 2000 Desktop Engine (MSDE 2000). |
SP4 includes 4 files:
Sql2k32sp4.exe. Updates for 32-bit database components. | |
| • | Sql2k32asp4.exe. Updates for Analysis Services components. |
| • | Sql2kdesksp4.exe. Updates for Microsoft SQL Server 2000 Desktop Engine (MSDE 2000). |
| • | Sql2k64sp4.exe. Updates for 64-bit database components. |
2. Must there be compatibility between the service pack level of the clients and the server(s)?
I apologize for asking what may to some seem a question with an obvious answer. I simply am not the world's best-informed dba & have spent 2 hours going cross-eyed trying to find any instruction on this on MS's site without success. It's time to throw myself at the mercy of kind peers who may have discovered the answers ahead of me.
Thanks,
August 29, 2005 at 9:38 pm
The service packs are intended to update the components of each of the related products that you have installed - either on your workstation or on the server.
e.g. If you have installed SQL Server components on your workstation (such as Enterprise Manager), Sql2ksp3.exe and Sql2k32sp4.exe should be applied.
The service packs contain the necessary logic to determine which components of the products are installed and will only update those.
Additionally, if you are applying SP4, you do not need to have applied SP3. SP4 includes everything from SP1, SP2 and SP3. (The same applies to any SQL service pack)
As for compatibility, generally, I would encourage you to keep workstations and servers on the same service pack. This is not mandatory but keeps everything in step.
The exception to this is Analysis Server. If you install SP3 on the server, install it on your workstation first. There are a number of security changes implemented and if you are not at the correct SP, you may find that you get errors when attempting to connect to cubes using Analysis Manager.
August 30, 2005 at 12:29 am
Following on from happycat59, for example, SP3a introduced new options such as (R-click on a server in EM, properties) "Enable the error reporting feature" that will only be seen in EM if you patch your client tools.
Also, system stored procs may change and they fix things in the APIs such as DMO, and EM uses these, so it would be best to always patch teh server and clöients to teh same. This includes hotfixes (as per hotfix 818/819 for SP3a which was a client tools patch)
Cheers
August 30, 2005 at 10:58 am
Would this also apply to workstations that have only the client network utility installed. Should we go around and upgrade these when ever we upgrade the server?
Thanks
August 31, 2005 at 1:44 am
I wouldn't because it is only this utility, not the full tool set.
Actually, most clients have this (or similar) as part of MDAC. Go to "Data Sources (ODBC)", goto create a DSN, enter any old rubbish, click next and click "CLient Configuration" button and there you go...
If you mean "Client connectivity only" option, this really only loads older DLLS such as DB-LIB for legacy apps.
I would only install the latest patch when I set up the client but not again with any new packs, and I probably don't need to do it then
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply