| Author |
Topic |
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
 Posted - 2008-10-29 : 14:34:22
|
| We are doing a DB migration from a 32 bit server to 64 bit server. Both the servers are SQL2K5. Do I need to consider anything in this case or a simple detach/attach will do?------------------------I think, therefore I am - Rene Descartes |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-10-29 : 15:32:23
|
| Better to do with Backup/Restore and change you compatibility level to 90 (make sure your apps works fine).Rebuild indexes if they are fragmented. |
 |
|
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
Posted - 2008-10-29 : 15:39:39
|
| Compatibility is 90 on both the servers! Only difference is with the processors.------------------------I think, therefore I am - Rene Descartes |
|
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2008-10-29 : 15:45:01
|
Just a question for understanding please...level 80 = sql server 2000level 90 = sql server 2005Why should someone set level 90 on an sql server 2005?Webfred
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2008-10-29 : 15:46:02
|
Or does it mean don't set level to 80 or less...?Webfred
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-10-29 : 15:48:37
|
| I know that.Sorry Ravilobo, I thought you are upgrading from 80 to 90 according to previous post.Then you should be good to go. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-10-29 : 15:51:37
|
quote:
Originally posted by webfred
Just a question for understanding please...level 80 = sql server 2000level 90 = sql server 2005Why should someone set level 90 on an sql server 2005?Webfred
No, you're never too old to Yak'n'Roll if you're too young to die.
I was referring to this one.Didn't read question properly? http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=113498 |
|
|
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
Posted - 2008-10-29 : 15:58:43
|
| ha ha ;-)------------------------I think, therefore I am - Rene Descartes |
|
|
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
Posted - 2008-10-29 : 15:59:14
|
quote:
Originally posted by webfredOr does it mean don't set level to 80 or less...?
Sometimes there is a need for DBs to be in lower versions though they have been migrated. mainly because the front-end apps support only lower version. By default in SQL2K5 compatibility is 90, however you may have a need to set it to lower versions, 80(SQL2K), 70 (SQL 7.) etc. One good example for this is, SQL2K5 doesn’t support “*= “ and “=*” for OUTER JOINS. When I migrated a SQL2K DB to SQL2K5 I found that many of the SPS with “*=” code are failing. Now I have set the compatibility to 80; my dev team is doing the sp change. once they are set , I will upgrade the compatibility. ------------------------I think, therefore I am - Rene Descartes |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-10-29 : 16:00:45
|
quote:
Originally posted by ravilobo
quote:
Originally posted by webfredOr does it mean don't set level to 80 or less...?
Sometimes there is a need for DBs to be in lower versions though they have been migrated. mainly because the front-end apps support only lower version. By default in SQL2K5 compatibility is 90, however you may have a need to set it to lower versions, 80(SQL2K), 70 (SQL 7.) etc. One good example for this is, SQL2K5 doesn’t support “*= “ and “=*” for OUTER JOINS. When I migrated a SQL2K DB to SQL2K5 I found that many of the SPS with “*=” code are failing. Now I have set the compatibility to 80; my dev team is doing the sp change. once they are set , I will upgrade the compatibility. ------------------------I think, therefore I am - Rene Descartes
I agree. |
|
|
|
saurabhsrivastava
Posting Yak Master
216 Posts |
Posted - 2008-10-29 : 16:05:16
|
quote:
Originally posted by sodeep
Better to do with Backup/Restore and change you compatibility level to 90 (make sure your apps works fine).Rebuild indexes if they are fragmented.
Any specific reason to do it with Backup restore instead of using Attach/dettach method |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-10-29 : 16:08:53
|
quote:
Originally posted by saurabhsrivastava
quote:
Originally posted by sodeep
Better to do with Backup/Restore and change you compatibility level to 90 (make sure your apps works fine).Rebuild indexes if they are fragmented.
Any specific reason to do it with Backup restore instead of using Attach/dettach method
Less downtime |
|
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2008-10-29 : 16:11:42
|
quote:
Originally posted by sodeep
quote:
Originally posted by ravilobo
quote:
Originally posted by webfredOr does it mean don't set level to 80 or less...?
Sometimes there is a need for DBs to be in lower versions though they have been migrated. mainly because the front-end apps support only lower version. By default in SQL2K5 compatibility is 90, however you may have a need to set it to lower versions, 80(SQL2K), 70 (SQL 7.) etc. One good example for this is, SQL2K5 doesn’t support “*= “ and “=*” for OUTER JOINS. When I migrated a SQL2K DB to SQL2K5 I found that many of the SPS with “*=” code are failing. Now I have set the compatibility to 80; my dev team is doing the sp change. once they are set , I will upgrade the compatibility. ------------------------I think, therefore I am - Rene Descartes
I agree.
Thanks sodeep and ravilobo, that is what I expected.
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2008-10-29 : 16:13:14
|
| always migrate with backup/restore.in case of attach/detach you could end with an unusble database if something goes wrong._______________________________________________Causing trouble since 1980Blog: http://weblogs.sqlteam.com/mladenpSpeed up SSMS development: www.ssmstoolspack.com <- version 1.1 out! |
|
|
|
|
32 -> 64