Going from SP1 to SP4

What should be done prior to going from SQL 2ksp1 to SQL2kSP4? I more
of a cisco guy who recently inherited backup duties and in looking over
the SQL server I see its out of date in regards to updates.Backup your databases and verify the backups, Backup the OS and verify it.
the upgrade path is fairly smooth.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<sandsdenver@.hotmail.com> wrote in message
news:1163045560.451617.245780@.k70g2000cwa.googlegroups.com...
> What should be done prior to going from SQL 2ksp1 to SQL2kSP4? I more
> of a cisco guy who recently inherited backup duties and in looking over
> the SQL server I see its out of date in regards to updates.
>|||Hi
Along with Hilary's comments you should really regression test your
application against this new configuration as well. Machines that have the
client tools installed should also be upgraded. You may wish to also look at
applying some of the post SP4 hotfixes, if you use AWE then you should be at
least on version 2040.
John
"sandsdenver@.hotmail.com" wrote:

> What should be done prior to going from SQL 2ksp1 to SQL2kSP4? I more
> of a cisco guy who recently inherited backup duties and in looking over
> the SQL server I see its out of date in regards to updates.
>|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eJCQCY7AHHA.3540@.TK2MSFTNGP03.phx.gbl...
> Backup your databases and verify the backups, Backup the OS and verify it.
> the upgrade path is fairly smooth.
>
Note however I believe it WILL require all your full text indexes to be
rebuilt. (I believe SP3 started that.)
And also keep an eye out for cross-database ownership chaining.
Otherwise, do the normla, backup, do it, and move on.
Very painless. Did this on our cluster server without a single hitch.

> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> <sandsdenver@.hotmail.com> wrote in message
> news:1163045560.451617.245780@.k70g2000cwa.googlegroups.com...
>