Make backups portable to on-premise SQL
Get this message when attempting to restore an SMI backup to on-premise SQL:
The database was backed up on a server running version 15.00.0700. That version is incompatible with this server, which is running version xx.xx.xxxx. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.
Lock in is risky for customers for a number of reasons. A workaround is using BACPAC but getting an established database into a state where BACPAC doesn't spew errors is difficult in our experience.
Thanks for the feedback.
We assume that you are talking about ability to restore native backup (.bak files) taken from SQL MI to SQL Server 2017/2019.
It’s a tough one unfortunately. Native backup contains binary data, and never been backwards compatible. E.g. you can’t restore backup from SQL 2012 on SQL 2008. Same logic applies here.
SQL MI gets updates faster SQL Server, as soon we check-in code, it gets deployed with the next wave of updates on Azure. Same as SQL DB.
Theoretically if you take backup of SQL MI now, and wait until SQL Server version release catch up, then you will be able to restore it.
Can you please let us know what kind of issues with BACPAC you are encountering?
Also, you can consider making transaction replication from SQL MI on on-prem as a way to move data around.
Anthony Genovese commented
Ultimately, I need a way to snapshot and move data. It needs to be as easy and as quick as a backup and restore is right now.
The DDL layer is simple. Schema compare & dac pacs get you where you need to go. But storing and moving that data seems to be the hard part. What I want is something packaged all together that easy to use and automate. And quick.
While it is true that the DB Engine of SMI may be changing frequently...the Internal Database Version number should not be changing frequently. It would be extremely helpful if the Internal Database Version number used in SMI was coordinated with the latest Internal Database Version number used on the latest version of SQL Server On-Premise (or IaaS). This of tremendous value for folks that want to push forward into hybrid cloud, but are fearful of an inability to return back fully in tack. BACPAC and Replication are not solutions, they are half-baked work arounds. If they were solutions then there would be no need for backup to exist in SQL Server at all.
We got the information that DMS should do the job. The feature should be implemented some time in Q2/Q3. Can you confirm this?
Or the option or opportunity to upgrade on premise version to match the MI version. Some off MI platform development, POCing, and testing is useful.
Our use case for this request would be to be able to restore an archived backup of a database from within the past 3-7 years to be able to answer auditing questions. We would prefer not to have to create a new managed instance for this. Transaction replication would not work, BACPAC might work but is not ideal.