October 18, 2010 at 4:41 am
Hi friends,
I have a plan to upgrade my DB's from sql2000 to 2008, but i don't know what will happen after that.
will all my Triggers and SP's work?
what is the risk?
What will happen if I restore them on 64bit?
Best Regards,
Ashkan
October 18, 2010 at 4:50 am
- Start with SQLServer upgrade advisor ( http://www.microsoft.com/downloads/en/details.aspx?FamilyId=F5A6C5E9-4CD9-4E42-A21C-7291E7F0F852&displaylang=en )
- prepare for security impact, try to optimize service account setup and implement best practises.
- 64-bit is only a other version of the software.
Your db data will not be affected, but will gain because of 64-bit advantages.
There an a number of threads at SSC concering upgrades (2005/2008). It may be worth reading some.
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
October 20, 2010 at 6:17 am
Thanks dude;)
really helpful.
Best Regards,
Ashkan
October 21, 2010 at 9:49 am
I've done this fairly recently and will be doing it again in a couple weeks. As previously suggested, the upgrade adviser is really handy.
There are two things I would watch out for:
1. Transferring logins - if you use SQL authentication, you'll need to transfer logins. You'll see scripts on the internet that create and use sp_help_revlogins and sp_hexadecimal stored procedures. You cannot use this to transfer logins directly from 2000 to 3008 because the encryption SQL uses changed between versions. Also, if you try to use the Transfer Logins task in SSIS, it will assign a random password to the logins (and not tell you what it is). The solution I came up with was to transfer the logins from 2000 to 2005 and then from 2005 to 2008. Of course, if you know the passwords for your logins, you can just recreate them...
2. When going from 32 bit to 64 bit, watch out to any OBDC drivers that might be used to access the database. 32 bit drivers cannot be used to connect to 64 bit SQL Server.
I wrote a couple of blog posts that go into these issues in more detail:
http://shaunjstuart.com/archive/2010/08/transferring-logins-from-sql-2000-to-2008/%5B/url%5D
http://shaunjstuart.com/archive/2010/09/too-many-bits/%5B/url%5D
October 21, 2010 at 9:56 am
Nice article, Shaun.:smooooth:
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
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply