Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Service Packs

Status
Not open for further replies.

tc3596

Technical User
Mar 16, 2001
283
I have SQL Server 2000 Standard Edition with no SP's currently installed (product level = RTM). After obtaining SP3a, do I need to install it on the server and all the clients? Also, would you recommend a db backup before applying? Thanks for your assistance and everyone on this board. It is truly a wonderful service.
 
Also, all clients only have the Client Network Utility installed. I noticed on Microsofts site that there are 3 files to download.

sql2kasp3.exe sql2kdesksp3.exe sql2ksp3.exe

Do I need all 3 of these installed on the server and clients?

 
sql2ksp3.exe is the actual SP3 for SQL Server. Install that on the server and any clients running the Client Tools.

sql2kdesksp3.exe is the SP3 for MSDE (desktop edition). Apply this to any MSDE installations you have.

sql2kasp3.exe is for the SQL Server Analysis tool (I believe).

There should be a read-me file that explains the three files and when to use them.

-SQLBill
 
Thanks. We aren't using Analysis Services and each client has only the client network utility installed. So, I believe I can just install the sql2ksp3.exe on each client and Server. Do you think a db backup is necessary?
 
What do you mean by "client network utility"? Are you talking about Enterprise Manager and Query Analyzer?

I don't think a DB backup is "necessary". But it's good practice. I back my databases up before applying ANY patch/service pack. While I didn't have any problems with the Service Pack, that doesn't mean it went smoothly for everyone else or that it will go smoothly for you.

-SQLBill
 
Client Network Utility is what connects the client to the server. You can set an alias for the server there. It lists the protocols to use for connectivity (i.e. Named Pipes or TCP/IP)
 
Okay, that's not part of SQL Server (at least I'm not familiar with it if it is). You shouldn't need to run the service pack on the client side.

-SQLBill
 
SQLBill,
It is a part of SQL Server. I'm referring to MS SQL Server 2000. Go look under programs or any client and look under Microsoft Sql Server, you'll find it there. If not, then we are talking about 2 different things. This is the MS SQL Server forum.
 
Yeah, I just found out I was wrong. I was looking at the read me file for SP3 and found:

SP3 updates:
the database engine
database client tools and utilities such as Enterprise Manager and osql
database client connectivity components

So, yes it should be applied to the client side as well.

-SQLBill
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top