Skip to content

Latest commit

 

History

History
301 lines (174 loc) · 14.6 KB

import-bacpac-file-create-new-database.md

File metadata and controls

301 lines (174 loc) · 14.6 KB
title description author ms.author ms.reviewer ms.date ms.service ms.subservice ms.topic ms.collection ms.custom f1_keywords helpviewer_keywords monikerRange
Import a BACPAC File to Create a New Database
Import a BACPAC File to create a new database.
WilliamDAssafMSFT
wiassaf
drskwier, randolphwest, maghan
03/11/2025
sql
sql-database-projects
how-to
data-tools
ignite-2024
sql13.swb. importdac.results.f1
sql13.swb.importdac.settings.f1
sql13.swb.importdac.storagebrowser.f1
sql13.swb.importdac.results.f1
sql13.swb.importdac.progress.f1
sql13.swb. importdac.summary.f1
sql13.swb.importdac.summary.f1
sql13.swb. importdac.progress.f1
sql13.swb.importdac.welcome.f1
sql13.swb. importdac.settings.f1
sql13.swb.dbdeployment.settings.f1
sql13.swb.dbdeployment.progress.f1
sql13.swb.dbdeployment.summary.f1
sql13.swb.dbdeployment.results.f1
sql13.swb.dbdeployment.welcome.f1
Data-tier application
SQL Server DAC
Migrate database
DAC
deploy database wizard
database deploy [SQL Server]
=azuresqldb-current || >=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-current || =fabric

Import a BACPAC file to create a new database

[!INCLUDE SQL Server Azure SQL Database Azure SQL Managed Instance FabricSQLDB]

Import a .bacpac file - to create a copy of the original database, with the data, on a new instance of the Database Engine, or to Azure SQL Database. An export operation can be combined with an import operation to migrate a database between instances or to create a copy of a database deployed in Azure SQL Database. Options for easily importing a .bacpac include:

  1. the Import Data-tier Application Wizard in SQL Server Management Studio
  2. the Deploy Database to Microsoft Azure SQL Database Wizard in SQL Server Management Studio to deploy a database between an instance of the [!INCLUDE ssDE] and a [!INCLUDE ssazure-sqldb] server, or between two [!INCLUDE ssazure-sqldb] servers
  3. the SqlPackage command-line utility

Before You Begin

The import process builds a new database in two stages.

  1. The import creates a new database using the database model definition stored in the .bacpac export file, the same way a .dacpac deploy creates a new database from the definition in a .dacpac file.

  2. The import bulk copies in the data from the .bacpac export file.

Database Options and Settings

By default, the database created during the import has all of the default settings from the CREATE DATABASE statement, except that the database collation and compatibility level are set to the values defined in the .bacpac export file. A .bacpac export file uses the values from the original database.

Some database options, such as TRUSTWORTHY, DB_CHAINING, and HONOR_BROKER_PRIORITY, can't be adjusted as part of the import process. Physical properties, such as the number of filegroups, or the numbers and sizes of files can't be altered as part of the import process. After the import completes, you can use the ALTER DATABASE statement, [!INCLUDE ssManStudioFull], or [!INCLUDE ssNoVersion] PowerShell to tailor the database. For more information, see Databases.

Security

To improve security, SQL Server Authentication logins are stored in a .bacpac export file without a password. When the file is imported, the login is created as a disabled login with a generated password. To enable the logins, sign in with ALTER ANY LOGIN permission and use ALTER LOGIN to enable the login and assign a new password. This extra step isn't needed for Windows Authentication logins because their passwords aren't managed by SQL Server.

Permissions

A .bacpac can only be imported by members of the sysadmin or serveradmin fixed server roles, or by logins that are in the dbcreator fixed server role and have ALTER ANY LOGIN permissions. The built-in [!INCLUDE ssNoVersion] system administrator account named sa can also import a .bacpac. Importing a .bacpac with logins to [!INCLUDE ssSDS] requires membership in the loginmanager or serveradmin roles. Importing a .bacpac without logins to [!INCLUDE ssSDS] requires membership in the dbmanager or serveradmin roles.

The Deploy Database to Microsoft Azure SQL Database Wizard in SQL Server Management Studio requires more permissions to export the source database. The login requires at least ALTER ANY LOGIN and database scope VIEW DEFINITION permissions, as well as SELECT permissions on sys.sql_expression_dependencies. Members of the securityadmin fixed server role who are also members of the database_owner fixed database role are permitted to export a .bacpac. Members of the sysadmin fixed server role or the built-in SQL Server system administrator account named sa can also export a .bacpac.

Import wizard

Use the Import Data-tier Application Wizard

To launch the wizard, use the following steps:

  1. Connect to the instance of [!INCLUDE ssNoVersion], whether on-premises or in [!INCLUDE ssSDS].

  2. In Object Explorer, right-click on Databases, and then select the Import Data-tier Application menu item to launch the wizard.

  3. Complete the wizard dialogs:

Introduction Page

This page describes the steps for the Data-tier Application Import Wizard.

Options

  • Do not show this page again. - Select the check box to stop the Introduction page from being displayed in the future.

  • Next - Proceeds to the Import Settings page.

  • Cancel - Cancels the operation and closes the wizard.

Import Settings Page

Use this page to specify the location of the .bacpac file to import.

  • Import from local disk - Select Browse... to navigate the local computer, or specify the path in the space provided. The path name must include a file name and the .bacpac extension.

  • Import from Azure - Imports a .bacpac file from a Microsoft Azure container. You must connect to a Microsoft Azure container to validate this option. The Import from Azure option also requires that you specify a local directory for the temporary file. The temporary file will be created at the specified location and will remain there after the operation completes.

    When browsing Azure, you're able to switch between containers within a single account. You must specify a single .bacpac file to continue the import operation. You can sort columns by Name, Size, or Date Modified.

    To continue, specify the .bacpac file to import, and then select Open.

Database Settings Page

Use this page to specify details for the database that will be created.

For a local instance of SQL Server:

  • New database name - Provide a name for the imported database.

  • Data file path - Provide a local directory for data files. Select Browse... to navigate the local computer, or specify the path in the space provided.

  • Log file path - Provide a local directory for log files. Select Browse... to navigate the local computer, or specify the path in the space provided.

To continue, select Next.

For an Azure SQL Database:

Validation Page

Use this page to review any issues that block the operation. To continue, resolve blocking issues and then select Re-run Validation to ensure that validation is successful.

To continue, select Next.

Summary Page

Use this page to review the specified source and target settings for the operation. To complete the import operation using the specified settings, select Finish. To cancel the import operation and exit the wizard, select Cancel.

Progress Page

This page displays a progress bar that indicates the status of the operation. To view detailed status, select the View details option.

To continue, select Next.

Results Page

This page reports the success or failure of the import and creates database operations, showing the success or failure of each action. Any action that encountered an error has a link in the Result column. Select the link to view a report of the error for that action.

Select Close to close the wizard.

Deploy Database wizard

Limitations

The Deploy Database wizard supports deploying a database:

The wizard doesn't support deploying databases between two instances of the [!INCLUDE ssDE].

An instance of the [!INCLUDE ssDE] must be running [!INCLUDE ssVersion2005] Service Pack 4 (SP4) or later to work with the wizard. If a database on an instance of the [!INCLUDE ssDE] contains objects not supported on [!INCLUDE ssazure-sqldb], you can't use the wizard to deploy the database to [!INCLUDE ssazure-sqldb]. If a database on [!INCLUDE ssazure-sqldb] contains objects not supported by [!INCLUDE ssNoVersion], you can't use the wizard to deploy the database to instances of [!INCLUDE ssNoVersion].

Use the Deploy Database Wizard

To migrate a database using the Deploy Database Wizard

  1. Connect to the location of the database you want to deploy. You can specify either an instance of [!INCLUDE ssDE] or a [!INCLUDE ssazure-sqldb] server.

  2. In Object Explorer, expand the node for the instance that has the database.

  3. Expand the Databases node.

  4. Right-click the database you want to deploy, select Tasks, and then select Deploy Database to Microsoft Azure SQL Database

  5. Complete the Wizard dialogs:

Introduction Page

This page describes the steps for the Deploy Database Wizard.

Options

  • Do not show this page again. - Select the check box to stop the Introduction page from being displayed in the future.

  • Next - Proceeds to the Deployment Settings page.

  • Cancel - Cancels the operation and closes the Wizard.

Deployment Settings Page

Use this page to specify the destination server and to provide details about your new database.

Local host:

  • Server connection - Specify server connection details and then select Connect to verify the connection.

  • New database name - Specify a name for the new database.

[!INCLUDE ssSDS] database settings:

  • [!INCLUDE ssSDS] edition - Select the edition of [!INCLUDE ssSDS] from the dropdown list.

  • Maximum database size - Select the maximum database size from the dropdown list.

Other settings:

  • Specify a local directory for the temporary file, which is the .bacpac archive file. The file will be created at the specified location and will remain there after the operation completes.

Summary Page

Use this page to review the specified source and target settings for the operation. To complete the deploy operation using the specified settings, select Finish. To cancel the deploy operation and exit the Wizard, select Cancel.

Progress Page

This page displays a progress bar that indicates the status of the operation. To view detailed status, select the View details option.

Results Page

This page reports the success or failure of the deploy operation, showing the results of each action. Any action that encountered an error has a link in the Result column. Select the link to view a report of the error for that action.

Select Finish to close the Wizard.

SqlPackage CLI

Use SqlPackage

SqlPackage initiates the actions specified using the parameters, properties, and SQLCMD variables specified on the command line. The command line syntax is as follows:

SqlPackage /Action:Import {parameters} {properties}

More information on the available parameters and properties can be found in the SqlPackage import documentation.

Related content