May 2, 2012 at 5:36 pm
Hello,
We know that in SQL Server, it is not possible to restore a backup copy of database from higher version(2008) to lower version (2000,2005). But, still we can do using generate scripts with schema and other information. My question is, after we generate scripts and pull the data, do we encounter any issues with database. Also, if we have packages designed in 2008, can we export those packages to 2005?
May 2, 2012 at 7:22 pm
DBA_SQL (5/2/2012)
Hello,We know that in SQL Server, it is not possible to restore a backup copy of database from higher version(2008) to lower version (2000,2005). But, still we can do using generate scripts with schema and other information. My question is, after we generate scripts and pull the data, do we encounter any issues with database. Also, if we have packages designed in 2008, can we export those packages to 2005?
The question is a bit vague...but let's see...provided you were not using data-features not available on the target platform (e.g. DATE data type) if you rebuild all schema and data from a 2008 database into a 2005 or 2000 database you will now have your data in a 2005 or 2000 database. Not much to say there.
Once you have your schema and data in place on the new platform issues you may encounter beyond that would be in accessing the data via code, whether that be T-SQL stored in the database (e.g. stored proc) or from data drivers in your client application. There are some language features available only in 2008 (e.g. MERGE).
Regarding "packages", I assume you mean SSIS packages. Those cannot be easily downgraded. If going to SQL 2005 you can port those using BIDS 2005, or if going all the way back to 2000 you can use a DTS designer to port them.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
May 2, 2012 at 9:54 pm
Thank you for your information and sorry for confusion. Yes, I do know we will encounter datatype issues while downgrading. What my question is what issues do we see when downgrading SSIS packages, and what steps do we need to consider in downgrading SSIS Packages.
May 2, 2012 at 10:11 pm
DBA_SQL (5/2/2012)
Thank you for your information and sorry for confusion. Yes, I do know we will encounter datatype issues while downgrading. What my question is what issues do we see when downgrading SSIS packages, and what steps do we need to consider in downgrading SSIS Packages.
As far as i know you'll have to recreate (port) those by hand. You may find a third party option that can convert them, but it is not supported as part of any Microsoft tool of which I am aware.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
May 3, 2012 at 5:49 am
SSIS is just like the database, you can't go backwards on the versions, so you'll have to move them by hand too.
In addition to data types, make sure you didn't count on any of the T-SQL enhancements such as compound operators, @2 += 2, the MERGE statement, stuff like that.
You'll need a pretty thorough test.
"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
May 3, 2012 at 6:15 am
Yeah let me consider the points which you have informed. I will work on this challenging part and will let you know with update. Thanks for responses.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply