There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.
SQL Upgrade 2008 to 2012
Hi,
We are currently in progress of upgrading our new web-apps to take advantage of .net 4.5
As it stands we can just mount our current sql 2008r2 databases into SQL 2012 and all will work fine after our tests. The question is, should we also rebuild the database directly in 2012 rather then 're-moun' the old ones? Are there any differences to building it fresh in 2012?
Performance? Optimisations? Features?
or is it just a waste of time and go ahead and mount the 'older' 2008 r2 databases?
Thanks!
We are currently in progress of upgrading our new web-apps to take advantage of .net 4.5
As it stands we can just mount our current sql 2008r2 databases into SQL 2012 and all will work fine after our tests. The question is, should we also rebuild the database directly in 2012 rather then 're-moun' the old ones? Are there any differences to building it fresh in 2012?
Performance? Optimisations? Features?
or is it just a waste of time and go ahead and mount the 'older' 2008 r2 databases?
Thanks!
Asked:
-
4
3
1 Solution
Yes that's correct.
My developers were saying that just mounting it may not bring all the optimization a that rebuilding it in SQL 2012 would do.. I'm not too sure about databases but they have no problems just mounting it. It was just advice that it would probably be better in the long run to have it built straight up using 2012.
Is this true?
My developers were saying that just mounting it may not bring all the optimization a that rebuilding it in SQL 2012 would do.. I'm not too sure about databases but they have no problems just mounting it. It was just advice that it would probably be better in the long run to have it built straight up using 2012.
Is this true?
I don't think this is true. I believe the mount is enough. You might also run a Job after mounting it on SQL2012:
a. Check DB Integrity,
b. Rebuild+Reorganize Index,
c. Update Statistics.
Once you have run these tasks, you should be more than OK.
a. Check DB Integrity,
b. Rebuild+Reorganize Index,
c. Update Statistics.
Once you have run these tasks, you should be more than OK.
I apologize fro the delay...
Your question "Do you have any links that may help?":
My answers:
a. If you search for links suggesting a rebuild instead of a mount, I don't have any and you probably won't find any official documents suggesting you to run a rebuild since the mount is fully supported by MS.
b. If you search for links about the DB Integrity, Index, and Statistics, the SQL Books Online are the best source and you'll find almost any useful information.
Your question "Do you have any links that may help?":
My answers:
a. If you search for links suggesting a rebuild instead of a mount, I don't have any and you probably won't find any official documents suggesting you to run a rebuild since the mount is fully supported by MS.
b. If you search for links about the DB Integrity, Index, and Statistics, the SQL Books Online are the best source and you'll find almost any useful information.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
If this is it, I would mount the DBs into SQL2012. I see no need to "rebuild".
Take care of the compatibility level of each DB.