Migrating From SQl 2005 to 2008
-
We're about to migrate from 2005 to 2008. Is there anything we should be aware of regarding sql code or anything functional that changed? Are we going to have to refactor our store procs and views to make them work?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
We're about to migrate from 2005 to 2008. Is there anything we should be aware of regarding sql code or anything functional that changed? Are we going to have to refactor our store procs and views to make them work?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997It's been a couple of years, but it was pretty slick. There is an update advisor that notes code that is being depreciated. I'v heard that you should check with any third party software you have to make sure it will work with 2008--we did not have that issue. If changing servers, check orphaned logins.
Soon...very soon...http://CraptasticNation.blogspot.com/[^]
-
It's been a couple of years, but it was pretty slick. There is an update advisor that notes code that is being depreciated. I'v heard that you should check with any third party software you have to make sure it will work with 2008--we did not have that issue. If changing servers, check orphaned logins.
Soon...very soon...http://CraptasticNation.blogspot.com/[^]
I agree with leckey. The deprecated items can be a pain but not hard to change. Do not forget to set options like xp_cmdshell if you use it.
-
We're about to migrate from 2005 to 2008. Is there anything we should be aware of regarding sql code or anything functional that changed? Are we going to have to refactor our store procs and views to make them work?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Been down that road twice now and not had any problems - seems fairly easy with no gotchas either time.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
-
We're about to migrate from 2005 to 2008. Is there anything we should be aware of regarding sql code or anything functional that changed? Are we going to have to refactor our store procs and views to make them work?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997This was one of our simplest upgrades ever, there was no problem with deprecated code, smooth as cream.
Never underestimate the power of human stupidity RAH
-
This was one of our simplest upgrades ever, there was no problem with deprecated code, smooth as cream.
Never underestimate the power of human stupidity RAH
Hello, It is best practise to run Upgrade Advisor before starting an upgrade. Please refer to SQL Server 2008 Upgrade Advisor download links. I have done this upgrade a few times without any problem. I hope it will be easy for your case also
