How to Migrate Azure SQL Database to Azure SQL Managed Instance

The latest version of SQLPackage supports migration to Azure SQL Managed Instance (MI) from multiple SQL sources such as Azure SQL Database. Export: Following the below steps, you can export a SQL database using the SQLPackage command-line utility. If possible, use a workstation that has access to the Azure SQL Database and the MI to avoid having…

0

Lesson Learned #57: Bacpac export process doesn’t include the automatic statistics

Hello Team, Today, I worked on a performance case that our customer claimed about a performance issue with a copied database from other one. The source database was working as they expected but the new database didn’t. Our customer mentioned that the database are identical. Working on this issue I found one item that represents the copied database hasn’t…


Change collation of existing Azure SQL database

When you are creating a new database you can change the collation in the portal Or else using TSQL (https://docs.microsoft.com/en-us/sql/relational-databases/collations/set-or-change-the-database-collation?view=azuresqldb-current)   However there is no easy way at this moment to change an existing database collation. The workaround is to use the BACPAC that can be used like the sample below

0

What will happen with CATALOG_COLLATION and Case Sensitive vs Case Insensitive

One of the options available when creating a database is the CATALOG_COLLATION, by default this is going to be SQL_Latin1_General_CP1_CI_AS , even if you take the trouble of specifying a database collation , the catalog collation will be SQL_Latin1_General_CP1_CI_AS unless you say otherwise. If you do not set this parameter it will not use the…


Editing a .bacpac file

There are times when for whatever reason you just wish you could make a change to a .bacpac file before you import it into Azure. Inside a bacpac file The inside of a bacpac is usually a closed book, you generate it and that is it you have the bacpac file and SQL Server Management…


BACPAC Export failing with Unable to reconnect – Timeout expired

I had a support case recently where the export of a SQL Server database into a BACPAC file was failing. The first attempt was done through SQL Server Management Studio 2016, by right-clicking the database -> Tasks -> Export Data-Tier Application. Another attempt using the sqlpackage.exe command-line tool showed the identical results though. The following operations…