I've created a Backup of a Database on a server with SQL Server 2008 R2.
I wish to restore this onto a server that is running SQL Server 2008.
I've received the error:
"The database was backed up on a server running version 10.50.4000.
That version is incompatible with this server, which is running
version 10.00.5500."
Is it possible to produce a version 10.00.5500 compatible backup from 10.50.4000.
If not what other options do I have, or other ways to create the database.
I have tried to use the Copy Database task, but also received errors.
This is not possible. At least, you won't be able to use the backup to restore on an older version.
Nenad Zivkovic provided a good link and there are several ways out of this situation listed:
Upgrade the older version of SQL Server to be at the same level as the newer SQL Server.
Script out the objects from the newer database and then usp a bcp process to extract the data from the newer database and import it into the older database.
Use the SQL Server Import and Export Wizard to build an SSIS package to move the data (it will move the data only).
Build a custom SSIS package to do the data move.
Use replication to move the data from the newer database to the older one.
Use some other form of scripting, such as with PowerShell, to keep the databases in sync.
(Source: http://www.mssqltips.com/sqlservertip/2675/why-cant-i-restore-a-database-to-an-older-version-of-sql-server/)
Related
I installed SQL Server 2014 Express. It doesn't have SSIS, so I installed SQL Server 2014 evaluation. I still don't see SSIS. Am I installing it in a wrong way or does SSIS come only with purchased SQL Server 2014 Standard edition and above.
I need to load multiple flat files into a database so I can work on them together.
Express version comes without SSIS. Actually there is not free version of SSIS. You need either SQL Server Standard, Developer, or Enterprise edition to get access to BIDS. If you have Visual Studio then you can download SQL Server Data Tools and you will be able to create SSIS projects
if you have Visual Studio 2013, then download and install this: http://www.microsoft.com/en-us/download/details.aspx?id=42313
SSIS is only available in the Enterprise, Business Intelligence and Standard editions. It should be available in the evaluation though as the evaluation is based on the Enterprise version (with a 180-day trial time).
It might be that you have to explicitly select to install the component (I haven't used the trial version in many years and honestly don't remember).
See this for more information: Features Supported by the Editions of SQL Server 2014
SSIS comes with SQL Server Developer edition which is inexpensive. Developer comes with all the features of Enterprise I believe.
SSIS IS NOT FREE !! We have to buy atleast the standard edition of Sql Server which is too costly if you are working for a small company.
Best way to load multiple files into a database without SSIS is to merge all files with same columns together in excel Merging files
and then load that big file into the database using Sql Server Import & Export.
Formatting columns may be tricky.
This question already has answers here:
Azure SQL Database Bacpac Local Restore
(6 answers)
Closed 9 years ago.
I'm trying to get up and running with Windows Azure but finding the database side extremely frustrating. I need to export my local database to a bacpac file from SQL 2008 and then import into Azure. I would also like to be able to export from Azure and then import to my local database for debugging.
I have found a few tutorials online for achieving this but every time I get part way through one of them I eventually hit a section that requires a step where the information or download is marked as outdated! it seems to have changed quite a bit over time and I can't find an up to date resource
Can anyone provide an updated link on how to do this?
Thanks
I had the same issues, all documentation on importing/exporting .bacpac mostly reference SQL 2012. I needed to export a sql 2008 R2 express database to azure as well as to be able to export from azure to my local devlopment environment.
I found the SQL Database Migration Wizard v3.9.9 & v4.0.12 to do the trick.
Download Link: http://sqlazuremw.codeplex.com/releases/view/32334
Also download the documentation and it will go through the migration of .bacpac to and from the azure and your local server. What is great about the tool is it will perform a compatibility check on the database to ensure it is ready to deploy to azure.
There is also another command line tool I investigated sqlpackage.exe that can be downloaded as part of Microsoft SQL Server Data Tools
Download Link: http://msdn.microsoft.com/en-us/data/hh297027
Below is an example of exporting a .bacpac file:
sqlpackage.exe /a:Export /ssn:SERVERNAME\sqlexpress /sdn:SOURCEDATABASENAME /su:DATABASEUSER /sp:DATABASEPASSWORD /tf:c:\SOURCEDATABASENAME.bacpac
I needed to export a SQL Azure database and then import it into a local SQL 2008 R2 server (Note I am also using Visual Studio 2010). Microsoft certainly went out of their way to make this a painful task, however, I was able to do it by doing the following:
Goto think link http://msdn.microsoft.com/en-us/jj650014 and install the SQL Server Data Tools for Visual Studio 2010
This will install on your local drive. In my case here is where it put it: C:\Program Files (x86)\Microsoft SQL Server\110\DAC\bin
Browse to this via the command line or powershell
You are going to want to execute the SqlPackage.exe
Open up this link to see a list of all the parameter options for SqlPackage.exe (http://msdn.microsoft.com/en-us/library/hh550080(v=vs.103).aspx)
Here is my command line that I needed to execute to import a .bacpac file into my local SQL 2008 R2 server:
.\SqlPackage.exe /a:Import /sf:C:\mydatabasefile.bacpac /tdn:NorthWind /tsn:BINGBONG
/tdn is the name of the database you want your bacpac file to restore to.
/tsn is the name of your SQL server.
You can see all these parameter descriptions on the link from #5.
While converting database project to SSDT and upgrading to SQL Server 2012 I need deployment script to work for both SQL Server 2008 and 2012.
I am using sqlpackage.exe /Action:Publish to deploy the latest database bits.
In sqlproj project properties I do see a target platform dropdown with options 2005/2008/2012 sql server. Does it generate a different dacpac if I change this target platform? Do I need to carry two versions of dacpac for each sql server version?
Or will the same dacpac work for any version of sql server?
I know this is 11 months old, but there is an option when you come to deployment specifically for this scenario - AllowIncompatiblePlatform.
//Set Deployment Options
DacDeployOptions dacOptions = new DacDeployOptions();
dacOptions.AllowIncompatiblePlatform = true;
Without setting the option I can deploy a 2008 dac to sql2012, but it will error if I deploy a 2012 dac to sql2008 with:
Microsoft.Data.Tools.Schema.Sql.Deployment.DeploymentCompatibilityException:
A project which specifies SQL Server 2012 as the target platform cannot be published to SQL Server 2008.
Setting the option means I do not get this error and can deploy to previous versions (back to 2005 I believe). NB You may also need to set the option TreatVerificationErrorsAsWarnings to true - YMMV.
The short answer is yes - different DACPACs for different SQL Server editions. Bob Beuachemin wrote a useful blog post about DAC Fx3.0 vs. DAC 2.0
From the command line using SqlPackage.exe, use the p:AllowIncompatiblePlatform option. A warning will still be shown but it will continue. This works from a SQL Server 2012 dacpac going to SQL Sever 2008 R2.
SqlPackage.exe /Action:Publish
/SourceFile:"testdb.dacpac"
/TargetDatabaseName:testDb
/p:AllowIncompatiblePlatform=true
/TargetServerName:"testserver"
I get the below mentioned while restoring a database back-up file to my system. Actually the back-up has been taken in other system and I'm trying to restore that file to my systems' sql server. Could anybody assist me in explaining what the error is and how to rectify? Please...
Error:
"System.Data.SqlClient.SqlError: The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.2531. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. (Microsoft.SqlServer.Smo)"
Thank You.
You SQL Server where you want to restore the database is older then the origin.
So to restore this database, you have to use a newer version.
Go to downloads.microsoft.com and get the SQL Express version of the latest, install it on any machine and restore. You can even install on the same machine.
If you cant udpate your SQL Server, you can connect both DB's then and use DTS to move the data back to your "old sql system".
Maybe a stupid question but... I created an SSIS package using VS2008 Professional. I want to deploy and execute it on a server running SQL Server 2005. When I try to run it I get an error stating the version of the Execute Package Utility on the server is different than the version of the package I'm trying to execute (makes sense, since I created the package with the newer version of VS).
To my knowledge Microsoft doesn't simply provide a download of the EPU to "upgrade" it, so how do I execute the package on a server that's running the previous version of SQL Server? Do I need to install a "throwaway" copy of SQL 2008 just to update the package, or what? On my workstation (which has VS2008) it runs fine against SQL 2005.
Unfortunately, you can't do this. It makes no sense since you can run SSIS against different databases (what if you were running a package on a server that didn't even use SQL Server?) but you'll get that version error if you created it in BIDS 2008.
You can try installed the Express edition of SQL Server 2008 and see if the included dtexec will work. Unfortunately, the configuration you are attempting to run is not supported and will likely incur errors.
As I'm about to embark on the same type of project, so the solution seems to be to use VS2005 to create the SSIS package, and and do the deployment. The package is still executable through our VS2008 code, but just can't create/deploy to 2005.
WHY?! OH WHY!? :(