We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

SQL Dbase Migration

Medium Priority
428 Views
Last Modified: 2012-05-07
Hello Experts,
I just realized that while I am able to develop in SQL 2008 using capatibility mode for SQL 2005 any .bak file I create is only compatible with SQL 2008.   So my next thought was to use SQL Server Management Studio to create a script that was for SQL 2005 and just save both the data and the dependant objects.  It works fine until I actually try and run the script, the file size for the script is ~445MB and it has several inserts to address the data.  When I try and run it I get an error, "The operation could not be completed.  Not enought storage is available to complete the operation".

Suffice it to say I have plenty of MEM and storage available and I also allowed for unrestricted growth.  After some research it would seem that SQL Server Management Studio doesn't handle large script files very well.  Sure enough when I just saved everything except the data I was able to create the dbase.

So here's my question, how the heck do I move a SQL 2008 capatible SQL 2005 file to an actual SQL 2005 server including the data?
SQL-Error.bmp
Comment
Watch Question

Melih SARICAMelih SARICA
CERTIFIED EXPERT

Commented:
did u try Copy Database option or import export option on SSMS(managment Studio) ?

Author

Commented:
No, I haven't tried that...actually I thought I run into the same limitations I had with the .bak file.  Namely that any file, regardless of the type, would be native SQL 2008 and would therefore not work with SQL 2005...this is the case with the .mdf and .ldf files.  

Commented:
Copy database has an option to copy objects also.  This option scripts out the objects and copies them using an SSIS package.  There are two options available where the second option is the attach/detach method which will not work for you.
The import/export option is basically the same - just using SSIS to transfer the objects.
 

Commented:
Another option would be to use a tool like Redgates SQL Compare and SQL Data Compare.  These tools are well worth the money spent.
There is also ApexSQL - and various tools at www.codeplex.com that can also do this.

Author

Commented:
Can you be more specific, which specific tools should I look at?
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Author

Commented:
What should be clarified is the perspecitve of this resolution.  I was trying to get a large script to run that contained inserts for the dbase data.  Instead I created a much smaller script to recreate an empty dbase (tables, relationship, stored procedures, views & object dependancies) in SQL 2005.  Then I used RedGate SQL Data Compare to migrate this data from the original SQL 2008 dbase to the newly created SQL 2005 dbase.  Once in SQL 2005 I was able to create a viable SQL 2005 .bak.  So essentially wilje was suggesting I look at this as a data migration effort...just took me a little while to figure out that perspective since my focus was on getting the large script to work in terms of some sort of work around.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.