| Author |
sql server 2005 upgrading
|
|
| Dodo Lurker 2006-10-24, 6:31 pm |
| I am planning to upgrade my production database to sql server 2005 (it's
currently a sql server 2000 machine at service pack 4).
What's the best approach to do this? Should I try to upgrade it directly
on the production server using the sql server 2005 install or should I
create a new fresh sql server 2005 instance and and backup and restore
my databases to it? My fear is that I hit a glitch during an upgrade that
I can't figure out. What is the recommended approach?
Also, what are best practices for upgrading to 2005? I know that
the statistics should be updated (I read that somewhere). What gotchas
should I be aware of?
TIA
Dave L.
| |
| David Browne 2006-10-24, 6:31 pm |
|
"Dodo Lurker" <none@noemailplease> wrote in message
news:t7GdnWJ44vYJFon
YnZ2dnUVZ_uWdnZ2d@co
mcast.com...
>I am planning to upgrade my production database to sql server 2005 (it's
> currently a sql server 2000 machine at service pack 4).
>
> What's the best approach to do this? Should I try to upgrade it directly
> on the production server using the sql server 2005 install or should I
> create a new fresh sql server 2005 instance and and backup and restore
> my databases to it? My fear is that I hit a glitch during an upgrade
> that
> I can't figure out. What is the recommended approach?
>
> Also, what are best practices for upgrading to 2005? I know that
> the statistics should be updated (I read that somewhere). What gotchas
> should I be aware of?
>
Upgrading to SQL Server 2005
http://www.microsoft.com/sql/soluti...de/default.mspx
David
| |
| Dodo Lurker 2006-10-24, 6:31 pm |
| Hi David
Thank you, I have read this already. I'm looking for people who've
actually gone through the process and have
tips they could share.
I did one test on a test machine and I had problems with the dot net beta
framework that I already had on my machine. I had to reformat the box
because I could not figure out what the problem was. I spent countless
hours
searching through the knowledge base.
I can't afford downtime for more than a couple of hours over a weekend
night.
"David Browne" <davidbaxterbrowne no potted meat@hotmail.com> wrote in
message news:OvXhGRs3GHA.2420@TK2MSFTNGP02.phx.gbl...
>
>
> "Dodo Lurker" <none@noemailplease> wrote in message
> news:t7GdnWJ44vYJFon
YnZ2dnUVZ_uWdnZ2d@co
mcast.com...
directly[color=darkr
ed]
>
> Upgrading to SQL Server 2005
> http://www.microsoft.com/sql/soluti...de/default.mspx
>
>
> David
>
| |
| Rob Roberts 2006-10-24, 6:31 pm |
| We did an in-place upgrade from SQL Server 2000 SP4 to SQL Server 2005, and
it all went very smoothly. I ran the Upgrade Advisor first, which
identified a couple of issues that needed to be taken care of before the
upgrade. I went through all of Microsoft's Pre- and Post-Upgrade Checklist
tasks when doing the upgrade. And I actually did the whole thing first on a
test server before doing it on our actual production server. It did take
more than a couple of hours, though. I think it took around four hours to
do the upgrade on the production server, including installing SP1.
--Rob Roberts
"Dodo Lurker" <none@noemailplease> wrote in message
news:Yo6dnROLjO53E4v
YnZ2dnUVZ_umdnZ2d@co
mcast.com...
> Hi David
>
> Thank you, I have read this already. I'm looking for people who've
> actually gone through the process and have
> tips they could share.
>
> I did one test on a test machine and I had problems with the dot net beta
> framework that I already had on my machine. I had to reformat the box
> because I could not figure out what the problem was. I spent countless
> hours
> searching through the knowledge base.
>
> I can't afford downtime for more than a couple of hours over a weekend
> night.
>
> "David Browne" <davidbaxterbrowne no potted meat@hotmail.com> wrote in
> message news:OvXhGRs3GHA.2420@TK2MSFTNGP02.phx.gbl...
> directly
>
>
|
|
|
|