SQL Server 2005
-
How many of you already use SQL Server 2005 in production?
My company does not even install SQL Server 2005 yet, are we too late?
How big is the learning curve moving from SQL Server 2000 to SQL Server 2005? I told my boss it was very different, he just ignored me and thought we could move everything from SQL Server 2000 to 2005 in no time, and no training required.
-
You’re never too late. If you/your company are happy with the results of your production servers why do fast upgrades.
The new version have quite good functionalities and extended other ones that are nice to the dbas.
We already have half of our park running 2005. We were early adopters.
Only now, some of the projects that use those servers start to take advantage of the new functionalities.
Feel free to contact me,
PaL
email:pal_soft@hotmail.com
www: will be available soon
-
As for the learning curve part. I just recently started using 2005 but since 99% of what worked on 2000 works on 2005 the basic learning curve is quite easy to take... But to learn the new features of 2005 I'd sincerely suggest at least getting a good book if a class is out of the question.
-
When I started my new job as DBA,one of the first things my boss had me do was build a SQL 2k5 machine for test. We have had this setup for 3 months and have just given access to the developers for testing out the new features. There are differences in 2005 that you would need to fully test out. One of the ones I am running into is SQL mail features. They are different and in new locations. So go slow on getting 2005 into production to make sure nothing breaks when you install. As for the rest, I love 2005 and am just enjoying some of the new features and ways of viewing things. Planning upgrades to the production systems is on my list of things to do next.
-
I am evaluating Version 2005 right now for an eventual upgrade. What I have not seen yet is a comparison/contrast of different upgrade strategies that would make my job a bit easier.
How have members making the upgrade to version 2005 done...
1. Running a straight "Upgrade" of an existing server box from 2000 to 2005?
2. Migrating from an instance of 2000 to an instance of 2005 residing on the same box? (Detach from 2000/Attach to 2005/blow away 2000 instance and software)
3. Detach 2000 DB, backup to tape, blow box away, clean install, restore 2000 DB from tape, reattach to 2005.
I think there are a lot of fence sitters out there who cannot afford to drop $25,000 on a new box who are looking for a solid upgrade strategy from Version 2000 to version 2005 on an existing box.
-
NEVER do an upgrade if you can possibly avoid it (applies to SQL Server, operating systems, whatever). Get a fresh install on a new box, migrate the data, and wipe the old box clean for reuse after you are convinced the new one is working.
If you can't afford the new box, get plenty of backups of the old one. Since you can't assume the upgrade won't destroy your system, you can't afford to do it unless you are prepared to wipe it clean and reinstall the old system. This means you are also prepared to use option 3, wipe the box and do a clean install of 2005.
Options 1 and 2 may work in many instances, but if you ever have problems you won't know if it is because of something that didn't upgrade properly. You would have to be exceptionally optimistic (and secure in your job) to do this on a production system.
-
The learning curve to migrate to SQL 2005 is not large. Download the Upgrade Advisor from Microsoft and run it on your existing databases to see what issues you might have. For instance, the old *= and =* outer join systax won't work in SQL 2005 unless you use a database compatibility mode. Many system tables are different, but this shouldn't affect normal queries.
There is a lot to learn about the new features of SQL 2005 if you want to take full advantage of them. Beat on the boss to cough up $2000 or so to send you to the PASS conference, but if that fails you'll just have to read Books On Line all day for the next few years.
-
Scott,
Thanks for your input. Option 3 is the cleanest way to go. It is exactly how I upgraded from SQL Server 7 to Version 2000. That time, I had the luxury of a new box so I could simply detach from Version 7 on the old box, copy to the new box and reattach to Version 2000.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply