Please share advice about upgrading to SQL 2005

I'm about to start using SQL 2005 on new hardware. I'm sure I'm not alone.
I thought perhaps people here might share their experiences about upgrading
to 2005 (whether on new hardware or not), and what tips they'd give to
others. Invariably, something goes wrong in the course of a major database
upgrade, and I'm wondering what those things have been for people here.Are you running side-by-side (another instance) or upgrading an
existing 2K instance? I've been running side-by-side on my workstation
since Nov. and have noticed almost no issues.
Also - are you using clustering at all? Don't run a 2K & 2005 on the
same cluster. We've had some issues with that & saw in a Microsoft
sponsored class that was a no-no. Other than that, we love 2005. The
upgrade advisor seems to work well too.
HK wrote:
> I'm about to start using SQL 2005 on new hardware. I'm sure I'm not alone
.
> I thought perhaps people here might share their experiences about upgradin
g
> to 2005 (whether on new hardware or not), and what tips they'd give to
> others. Invariably, something goes wrong in the course of a major databa
se
> upgrade, and I'm wondering what those things have been for people here.|||I'll pull a development database, that has good data, from 2000, attach it
to the new hardware that is running 2005, and make it live for production.
The client application connection strings will change, of course. No
clustering is involved at this moment.
How do you start the Upgrade Advisor? I haven't tried that. The
UI/documentation is, thus far, very lousy for a new version that is 5 years
along. I didn't know there was one.
"Corey Bunch" <unc27932@.yahoo.com> wrote in message
news:1141686052.211469.242010@.z34g2000cwc.googlegroups.com...
> Are you running side-by-side (another instance) or upgrading an
> existing 2K instance? I've been running side-by-side on my workstation
> since Nov. and have noticed almost no issues.
> Also - are you using clustering at all? Don't run a 2K & 2005 on the
> same cluster. We've had some issues with that & saw in a Microsoft
> sponsored class that was a no-no. Other than that, we love 2005. The
> upgrade advisor seems to work well too.
> HK wrote:
alone.[vbcol=seagreen]
upgrading[vbcol=seagreen]
database[vbcol=seagreen]
>|||SQL 2005 Upgrade Advisor is a separate download:
http://www.microsoft.com/downloads/...&DisplayLang=en
*mike hodgson*
http://sqlnerd.blogspot.com
HK wrote:

>I'll pull a development database, that has good data, from 2000, attach it
>to the new hardware that is running 2005, and make it live for production.
>The client application connection strings will change, of course. No
>clustering is involved at this moment.
>How do you start the Upgrade Advisor? I haven't tried that. The
>UI/documentation is, thus far, very lousy for a new version that is 5 years
>along. I didn't know there was one.
>
>"Corey Bunch" <unc27932@.yahoo.com> wrote in message
>news:1141686052.211469.242010@.z34g2000cwc.googlegroups.com...
>
>alone.
>
>upgrading
>
>database
>
>
>|||Assuming no syntax errors are present that aren't supported in 2005,
then I think you should be fine. Although, I think it leaves it in 80
(2000) compatability mode if you restore/attach. You might want to go
check the db options after you've done it and try & push it up to 2005.
The upgrade advisor is a must though. Try the link that Mike sent.