Menu
Got myself in a bit of a pickle here ... working on a CMS project, under the assumption that sql server 2008 was greenlighted as the db of choice. Well it wasn't, we now have to backport all of our content out SQL Server 2008 and into SQL Server 2005.
A simple backup/restore procedure yields: "RESTORE HEADERONLY is terminating abnormally. (Microsoft SQL Server, Error: 3241)".
Unfortunately, exporting the data to an excel spreadsheet yields multiple OLE errors which I believe is actually a problem in the db of the cms.
Does anyone out there have other approaches they would like to recommend for this task? Thanks in advance
360
Just start with a new Windows Server 2022 image, and install SQL Server 2019. Then do a backup/restore of all your user databases from your SQL Server 2008 R2 to the new machine. Consider updating the compatibilty level, as well as other database-scoped settings.
When it restores the SQL Server 2008 or SQL Server 2008 R2 database backup to SQL Server 2016 or 2017, SQL Server has to upgrade the internal version of the databases. One of the version upgrade steps was optimized to shorten the upgrade time.
Here are the basic steps we need to follow: Script the database schema and data from the higher version of SQL Server by using the Generate Scripts Wizard in SSMS. Connect to the lower version of SQL Server, and run the SQL scripts that were generated in the previous step, to create the database schema and data.
Automate SQL Server 2008 Database Import to SQL Server 2014 Go through the steps given below sequentially to import SQL Server Database 2008 to SQL Server 2014 with ease. Open the software, Click on Browse to select the database file, Select the Standard Recovery Mode and click Recover.
Use RedGate:
tool for comparing and deploying SQL Server database contents.
You can work with live databases, backups, or SQL scripts in source control. Damaged or missing data can be restored to a single row, without the need for a full database recovery.
SQL Data Compare helps you compare and deploy changes quickly, simply, and with zero errors...
73
There is no way to do this by default. You can generate scripts for 2008 database on 2008 server and then execute these scripts on 2005 version. Note that you’ll have to manually review scripts and remove all parts that are unique to 2008 version.
Another way is to use third party tools such as Red Gate or ApexSQL Diff (move schema) and ApexSQL Data Diff (move data).
24
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
