Are there any guidelines or best practices for deploying or testing Service Packs? What types of tests should be performed prior to upgrading or do I just trust Microsoft?I always put them on test machines first for a month or so. Enough time that some applications have had a testing cycle, anyway. If there are no major complaints, the first production guinea pig is selected, and watched for a week. If no major problems come up, then the rest of the machines get it. never trust Microsoft. They are human, too...well, half human.|||That's the way to do it. We have dev, test, and production environments. Dev gets the release 1st, and if no one screams after a couple of weeks, we apply it to test. Again, the absence of any wailing and gnashing of teeth means we move to production.
Plus, an added benefit is that you get to practice the install in case something goes horribly wrong (oh my ... would that ever happen?)|||Definitely agree with the two previous posters. In addition, read the release notes, particularly if you have a clustered environment or one where you use replication (upgrades MUST be done in a certain order when replication is involved)
Lempster|||Thank you all!! Pretty much thought so, but just wanted to see how others were handling it. :)
Showing posts with label packs. Show all posts
Showing posts with label packs. Show all posts
Monday, March 19, 2012
Applying service packs
Hi,
I have a production server running SQL 2000 SP2 on Windows 2000 server. I
have to migrate all the databases on this production server to a new server
running SQL Server 2000 SP4 on Windows 2003 Server.
Are there any known issues? How should I proceed ? Apply SP4 on the current
Production Server first and then migrate? Any insight will be greatly
appreciated. Thanks.
I would recommend applying SP4 to the current server before the migration.
This way all your system databases will match between systems.
If you are going to copy the system databases as well (which I would
recommend if you can keep all the directory paths the same) you will need to
do a sp_droplogin and sp_addlogin to change the server's name to the new
server name.
There should be no issues with this migration.
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"sharman" wrote:
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
|||Hello,
Best option:-
1. Install SP4 to current production system
2. Copy the databases to new server.
3. You can also copy the system databases. This will ahelp you not to create
any jobs, DTS, Logins...
Thanks
Hari
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:F892EF13-069B-4E8A-9DB7-0EF942C90450@.microsoft.com...
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new
> server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the
> current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
I have a production server running SQL 2000 SP2 on Windows 2000 server. I
have to migrate all the databases on this production server to a new server
running SQL Server 2000 SP4 on Windows 2003 Server.
Are there any known issues? How should I proceed ? Apply SP4 on the current
Production Server first and then migrate? Any insight will be greatly
appreciated. Thanks.
I would recommend applying SP4 to the current server before the migration.
This way all your system databases will match between systems.
If you are going to copy the system databases as well (which I would
recommend if you can keep all the directory paths the same) you will need to
do a sp_droplogin and sp_addlogin to change the server's name to the new
server name.
There should be no issues with this migration.
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"sharman" wrote:
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
|||Hello,
Best option:-
1. Install SP4 to current production system
2. Copy the databases to new server.
3. You can also copy the system databases. This will ahelp you not to create
any jobs, DTS, Logins...
Thanks
Hari
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:F892EF13-069B-4E8A-9DB7-0EF942C90450@.microsoft.com...
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new
> server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the
> current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
Applying Service Packs
When applying service packs to SQL Server (2000 or 2005), does the service
pack need to be applied to the client tools running on indivdual PCs/Laptops
as well? Thanks.
Hello,
May not be required to all desktops. You can install the service packs to
the desktop machines when ever there is a requirement araise.
Thanks
Hari
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
|||Please remember that DTS, as an example, is a client tool. If you have
different version of the client on your workstation and your server you run
the risk of getting totally different DTS packages and therefore results.
In SQL2005 the maintenance plans have changed dramatically between SP1 and
SP2. You cannot administer an SP2 created plan with an SP1 client. If a plan
is created on an SP2 server then you would not be able to maintain it from
an SP1 client.
Our rule is to update the client software when the client accesses an
updated server.
Chris
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
pack need to be applied to the client tools running on indivdual PCs/Laptops
as well? Thanks.
Hello,
May not be required to all desktops. You can install the service packs to
the desktop machines when ever there is a requirement araise.
Thanks
Hari
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
|||Please remember that DTS, as an example, is a client tool. If you have
different version of the client on your workstation and your server you run
the risk of getting totally different DTS packages and therefore results.
In SQL2005 the maintenance plans have changed dramatically between SP1 and
SP2. You cannot administer an SP2 created plan with an SP1 client. If a plan
is created on an SP2 server then you would not be able to maintain it from
an SP1 client.
Our rule is to update the client software when the client accesses an
updated server.
Chris
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
Applying Service Packs
When applying service packs to SQL Server (2000 or 2005), does the service
pack need to be applied to the client tools running on indivdual PCs/Laptops
as well? Thanks.Hello,
May not be required to all desktops. You can install the service packs to
the desktop machines when ever there is a requirement araise.
Thanks
Hari
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.|||Hari Prasad wrote:
> Hello,
> May not be required to all desktops. You can install the service packs to
> the desktop machines when ever there is a requirement araise.
> Thanks
> Hari
> "MACason" <MACason@.discussions.microsoft.com> wrote in message
> news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
>
If you are running SQL2000 Analysis Services and upgrade to AS SP4,
you'll have to upgrade your AS Analysis Manager and client tools to SP 4
as well. If you don't do it, you'll get some strange errors when you try
to connect with the client tools. I'm not aware of any other scenarios
where it causes problems to run a lower SP level on the client, but
there might be...;-).
--
Regards
Steen Schlter Persson
Database Administrator / System Administrator|||Please remember that DTS, as an example, is a client tool. If you have
different version of the client on your workstation and your server you run
the risk of getting totally different DTS packages and therefore results.
In SQL2005 the maintenance plans have changed dramatically between SP1 and
SP2. You cannot administer an SP2 created plan with an SP1 client. If a plan
is created on an SP2 server then you would not be able to maintain it from
an SP1 client.
Our rule is to update the client software when the client accesses an
updated server.
Chris
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
pack need to be applied to the client tools running on indivdual PCs/Laptops
as well? Thanks.Hello,
May not be required to all desktops. You can install the service packs to
the desktop machines when ever there is a requirement araise.
Thanks
Hari
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.|||Hari Prasad wrote:
> Hello,
> May not be required to all desktops. You can install the service packs to
> the desktop machines when ever there is a requirement araise.
> Thanks
> Hari
> "MACason" <MACason@.discussions.microsoft.com> wrote in message
> news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
>
If you are running SQL2000 Analysis Services and upgrade to AS SP4,
you'll have to upgrade your AS Analysis Manager and client tools to SP 4
as well. If you don't do it, you'll get some strange errors when you try
to connect with the client tools. I'm not aware of any other scenarios
where it causes problems to run a lower SP level on the client, but
there might be...;-).
--
Regards
Steen Schlter Persson
Database Administrator / System Administrator|||Please remember that DTS, as an example, is a client tool. If you have
different version of the client on your workstation and your server you run
the risk of getting totally different DTS packages and therefore results.
In SQL2005 the maintenance plans have changed dramatically between SP1 and
SP2. You cannot administer an SP2 created plan with an SP1 client. If a plan
is created on an SP2 server then you would not be able to maintain it from
an SP1 client.
Our rule is to update the client software when the client accesses an
updated server.
Chris
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
Applying service packs
Hi,
I have a production server running SQL 2000 SP2 on Windows 2000 server. I
have to migrate all the databases on this production server to a new server
running SQL Server 2000 SP4 on Windows 2003 Server.
Are there any known issues? How should I proceed ? Apply SP4 on the current
Production Server first and then migrate? Any insight will be greatly
appreciated. Thanks.I would recommend applying SP4 to the current server before the migration.
This way all your system databases will match between systems.
If you are going to copy the system databases as well (which I would
recommend if you can keep all the directory paths the same) you will need to
do a sp_droplogin and sp_addlogin to change the server's name to the new
server name.
There should be no issues with this migration.
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"sharman" wrote:
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new serve
r
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the curren
t
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.|||Hello,
Best option:-
1. Install SP4 to current production system
2. Copy the databases to new server.
3. You can also copy the system databases. This will ahelp you not to create
any jobs, DTS, Logins...
Thanks
Hari
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:F892EF13-069B-4E8A-9DB7-0EF942C90450@.microsoft.com...
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new
> server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the
> current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
I have a production server running SQL 2000 SP2 on Windows 2000 server. I
have to migrate all the databases on this production server to a new server
running SQL Server 2000 SP4 on Windows 2003 Server.
Are there any known issues? How should I proceed ? Apply SP4 on the current
Production Server first and then migrate? Any insight will be greatly
appreciated. Thanks.I would recommend applying SP4 to the current server before the migration.
This way all your system databases will match between systems.
If you are going to copy the system databases as well (which I would
recommend if you can keep all the directory paths the same) you will need to
do a sp_droplogin and sp_addlogin to change the server's name to the new
server name.
There should be no issues with this migration.
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"sharman" wrote:
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new serve
r
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the curren
t
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.|||Hello,
Best option:-
1. Install SP4 to current production system
2. Copy the databases to new server.
3. You can also copy the system databases. This will ahelp you not to create
any jobs, DTS, Logins...
Thanks
Hari
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:F892EF13-069B-4E8A-9DB7-0EF942C90450@.microsoft.com...
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new
> server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the
> current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
Applying service packs
Hi,
I have a production server running SQL 2000 SP2 on Windows 2000 server. I
have to migrate all the databases on this production server to a new server
running SQL Server 2000 SP4 on Windows 2003 Server.
Are there any known issues? How should I proceed ? Apply SP4 on the current
Production Server first and then migrate? Any insight will be greatly
appreciated. Thanks.I would recommend applying SP4 to the current server before the migration.
This way all your system databases will match between systems.
If you are going to copy the system databases as well (which I would
recommend if you can keep all the directory paths the same) you will need to
do a sp_droplogin and sp_addlogin to change the server's name to the new
server name.
There should be no issues with this migration.
--
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"sharman" wrote:
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.|||Hello,
Best option:-
1. Install SP4 to current production system
2. Copy the databases to new server.
3. You can also copy the system databases. This will ahelp you not to create
any jobs, DTS, Logins...
Thanks
Hari
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:F892EF13-069B-4E8A-9DB7-0EF942C90450@.microsoft.com...
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new
> server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the
> current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
I have a production server running SQL 2000 SP2 on Windows 2000 server. I
have to migrate all the databases on this production server to a new server
running SQL Server 2000 SP4 on Windows 2003 Server.
Are there any known issues? How should I proceed ? Apply SP4 on the current
Production Server first and then migrate? Any insight will be greatly
appreciated. Thanks.I would recommend applying SP4 to the current server before the migration.
This way all your system databases will match between systems.
If you are going to copy the system databases as well (which I would
recommend if you can keep all the directory paths the same) you will need to
do a sp_droplogin and sp_addlogin to change the server's name to the new
server name.
There should be no issues with this migration.
--
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"sharman" wrote:
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.|||Hello,
Best option:-
1. Install SP4 to current production system
2. Copy the databases to new server.
3. You can also copy the system databases. This will ahelp you not to create
any jobs, DTS, Logins...
Thanks
Hari
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:F892EF13-069B-4E8A-9DB7-0EF942C90450@.microsoft.com...
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new
> server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the
> current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
Applying Service Packs
When applying service packs to SQL Server (2000 or 2005), does the service
pack need to be applied to the client tools running on indivdual PCs/Laptops
as well? Thanks.Hello,
May not be required to all desktops. You can install the service packs to
the desktop machines when ever there is a requirement araise.
Thanks
Hari
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.|||Hari Prasad wrote:
> Hello,
> May not be required to all desktops. You can install the service packs to
> the desktop machines when ever there is a requirement araise.
> Thanks
> Hari
> "MACason" <MACason@.discussions.microsoft.com> wrote in message
> news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
>> When applying service packs to SQL Server (2000 or 2005), does the service
>> pack need to be applied to the client tools running on indivdual
>> PCs/Laptops
>> as well? Thanks.
>
If you are running SQL2000 Analysis Services and upgrade to AS SP4,
you'll have to upgrade your AS Analysis Manager and client tools to SP 4
as well. If you don't do it, you'll get some strange errors when you try
to connect with the client tools. I'm not aware of any other scenarios
where it causes problems to run a lower SP level on the client, but
there might be...;-).
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||Please remember that DTS, as an example, is a client tool. If you have
different version of the client on your workstation and your server you run
the risk of getting totally different DTS packages and therefore results.
In SQL2005 the maintenance plans have changed dramatically between SP1 and
SP2. You cannot administer an SP2 created plan with an SP1 client. If a plan
is created on an SP2 server then you would not be able to maintain it from
an SP1 client.
Our rule is to update the client software when the client accesses an
updated server.
Chris
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
pack need to be applied to the client tools running on indivdual PCs/Laptops
as well? Thanks.Hello,
May not be required to all desktops. You can install the service packs to
the desktop machines when ever there is a requirement araise.
Thanks
Hari
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.|||Hari Prasad wrote:
> Hello,
> May not be required to all desktops. You can install the service packs to
> the desktop machines when ever there is a requirement araise.
> Thanks
> Hari
> "MACason" <MACason@.discussions.microsoft.com> wrote in message
> news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
>> When applying service packs to SQL Server (2000 or 2005), does the service
>> pack need to be applied to the client tools running on indivdual
>> PCs/Laptops
>> as well? Thanks.
>
If you are running SQL2000 Analysis Services and upgrade to AS SP4,
you'll have to upgrade your AS Analysis Manager and client tools to SP 4
as well. If you don't do it, you'll get some strange errors when you try
to connect with the client tools. I'm not aware of any other scenarios
where it causes problems to run a lower SP level on the client, but
there might be...;-).
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||Please remember that DTS, as an example, is a client tool. If you have
different version of the client on your workstation and your server you run
the risk of getting totally different DTS packages and therefore results.
In SQL2005 the maintenance plans have changed dramatically between SP1 and
SP2. You cannot administer an SP2 created plan with an SP1 client. If a plan
is created on an SP2 server then you would not be able to maintain it from
an SP1 client.
Our rule is to update the client software when the client accesses an
updated server.
Chris
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
Sunday, March 11, 2012
Apply Service Pack Question
I have a couple of servers that are running SQL Server 2000 with no service
packs applied. I would like to apply SP3a to both of them. Are there any
possible/known problems that I should be aware of before attempting this.
This will be my first time doing this type of thing...
Thanks
EricMake sure you really read the documentation and readme etc that comes with the service pack! :-)
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Eric Stewart" <stewarte@.repsilverstate.com> wrote in message
news:uB95tpeZDHA.2236@.TK2MSFTNGP10.phx.gbl...
> I have a couple of servers that are running SQL Server 2000 with no service
> packs applied. I would like to apply SP3a to both of them. Are there any
> possible/known problems that I should be aware of before attempting this.
> This will be my first time doing this type of thing...
> Thanks
> Eric
>
packs applied. I would like to apply SP3a to both of them. Are there any
possible/known problems that I should be aware of before attempting this.
This will be my first time doing this type of thing...
Thanks
EricMake sure you really read the documentation and readme etc that comes with the service pack! :-)
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Eric Stewart" <stewarte@.repsilverstate.com> wrote in message
news:uB95tpeZDHA.2236@.TK2MSFTNGP10.phx.gbl...
> I have a couple of servers that are running SQL Server 2000 with no service
> packs applied. I would like to apply SP3a to both of them. Are there any
> possible/known problems that I should be aware of before attempting this.
> This will be my first time doing this type of thing...
> Thanks
> Eric
>
Subscribe to:
Posts (Atom)