February 3, 2012 at 6:39 am
Hello,
We're about to upgrade from 2000 to 2005. Yep we're a little behind but not our fault, haha.
We've gone over the MSDN upgrade Discontinued, Breaking, Deprecated, etc... But is there anything special we should watch out for, something I might of missed that is all too common for everyone else.
If not, then I'll cross my fingers and we'll pull the trigger, but if so thanks for the warning.
Thank you,
February 3, 2012 at 6:47 am
Are you aware that 2005 is already EOL ?
If you're upgrading, I'd go straight to either 2008 R2, or if you feel adventurous 2012 which comes out in like 2 months.
February 3, 2012 at 6:52 am
Yes we know and it has come up in discussion; the good news is that it's not my decision.
February 3, 2012 at 7:00 am
Ken at work (2/3/2012)
Yes we know and it has come up in discussion; the good news is that it's not my decision.
Lets see what I can remember from our jump from 2000 to 2008 R2, when we did that... most of what hit us was actually the changes from 2000 to 2005 anyway.
The syntax for Query Index hints changed, that hit us pretty hard (and in the process we removed all of them).
xp_sendmail should be pretty much dumped in favor of sp_send_dbmail (which requires smtp properly addressed email addresses, but removes the need for Outlook on the server)
February 3, 2012 at 7:09 am
Before making the upgrade you might want to do some testing.
The Developer Edition of SQL 2005 is I think still available at a cost of about $50 (although not from Microsoft), for example
http://www.oemsoftwarebuy.org/microsoft-sql-server-2005-developer-edition.html
Now the Developer Edition can NOT be utilized by a production system, but in your case. Purchase and install the Developer Edition, restore a backup of your production database to that instance of SQL 2005 and run some tests which might uncover some undiscovered problems.
Also be aware of the compatability level and its effects
For $50 and a little time, it just might save you hours of OT and scrambling when you do go live. (Of course to go live you'll have to purchase a copy of SQL 2005, but you seem willing to do that)
Oh well just a thought.
February 3, 2012 at 7:22 am
Our biggest problems weren't in the database. They were in the code that was written using ancient copies of OLEDB (or whatever the connection system was 12 years ago). The app code needed substantial testing and a few serious rewrites to work with 2005+.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 3, 2012 at 7:27 am
Code issues is one of my main concerns. But we've tested most stored procedures against out test environment.
Can you give me a common example of a OLDB issue or problem?
February 3, 2012 at 7:32 am
Oh man, I don't remember the specifics.
I do remember that we had code that made a call through ADO (I think it was) that retrieved the data structure of a proc. The way that call was made wasn't compatible with the new ADO.NET. They had to rewrite for that. There were a couple of others that escape me. Sorry. It's been a while.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 3, 2012 at 7:55 am
have you any DTS packages?
big jump to SSIS......although 2000DTS can be used under "legacy" iirc.
maybe worth thinking about
________________________________________________________________
you can lead a user to data....but you cannot make them think
and remember....every day is a school day
February 3, 2012 at 7:59 am
Not, we should be good there.
I'll test the ADO connections but so far it looks fine.
February 3, 2012 at 8:07 am
Whatever you do, make sure you start with the appropriate upgrade adviser !
SQLua.exe can be found in the feature packs.
ref: Using Upgrade Advisor to Prepare for Upgrades
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
February 6, 2012 at 8:08 am
thank you for your help everyone,
I appreciate it.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply