SSMS Previews New Create and Apply Wizards That Replace the Old DACPAC and BACPAC Commands

Two goal-based wizards in SSMS replace the old extract, export and import commands for SQL Server and Azure SQL targets.

Microsoft has added two preview wizards to SQL Server Management Studio (SSMS) that bring every DACPAC and BACPAC task into one place. The Create wizard builds a package from a database, and the Apply wizard pushes a package into a target database. The SQL tools team described the change on November 17, 2026.

Until now, users had to remember which of several menu commands to pick. Extract, export, register, upgrade and import each did a slightly different job. The new wizards ask what you want to achieve and then pick the right package type for you, which should cut mistakes during schema moves.

What Changed in SSMS

The old set of data-tier application commands is folded into two goal-based tasks. Both are marked as preview, along with a third command that creates an empty database and then opens the Apply flow.

  • Create bacpac/dacpac (Preview): found under Tasks when you right-click a source database in Object Explorer.
  • Apply bacpac/dacpac (Preview): found under Tasks when you right-click a target database.
  • Create database from bacpac/dacpac (Preview): found on the Databases folder for SQL Server and Azure SQL Managed Instance.

Supported targets are SQL Server plus the Azure SQL Database and Managed Instance services. The connection you use still needs the right permissions for each step.

How the Create Wizard Works

The key choice sits on the Select Contents page. If the Include data box stays ticked, the wizard writes a BACPAC with schema and table data. If you clear it, you get a DACPAC that holds only the schema, and the wizard shows the resulting format before you go on.

Next you choose where the file goes. It can land on local disk or in an Azure Blob Storage container. For a BACPAC, a settings page lets you pick exactly which tables carry data, either one by one or all at once.

There is also an option to leave out objects that Azure SQL Database cannot accept, which helps when moving an on-premises database to the cloud. After the run, a Save Logs button keeps the full output. If the file is created without errors, you can jump straight into the Apply wizard with that file already chosen.

How the Apply Wizard Works

The Apply flow behaves differently for each format. That matches how the two package types have always worked, but the wizard now spells it out.

  • DACPAC: the wizard compares the package with the target and builds a deployment plan. You fill in SQLCMD variables, search and set publish options, and review the plan and warnings before running it.
  • BACPAC: the wizard loads schema and data, and the target has to be free of any objects created by users. Even one empty table blocks the import, and the Bacpac choice is disabled when such objects exist.

For BACPAC imports you can set the command timeout, the long-running command timeout and the database lock timeout. The review page lists every table and the total amount of data before anything is written.

The DACPAC options include the setting that blocks deployment when data could be lost. Microsoft warns that turning it off can let the plan drop data, and advises a backup first. If the target already matches the package, the plan simply reports that nothing needs to change.

What It Means for Developers

For many teams, the hardest part of DACPAC and BACPAC work was not the files but choosing the right command. A wrong pick could mean a schema-only copy when data was needed, or an import that failed late because the target was not empty. Goal-based wizards remove most of that guessing.

The review page for DACPAC deployments is the most useful piece for day-to-day work. It lets you read the planned create, alter and drop steps inside SSMS before they run, which is the same check many teams script by hand today. Treat it as a gate: read every drop and every data-loss warning.

Keep in mind that these files are not encrypted. A BACPAC with production data is a full copy of sensitive rows, so store it in a protected location or in a locked-down Blob container. For pipelines, the same engine work is moving into SqlPackage, as our report on SqlPackage 170.6 deployment history and fast comparison explains.

Limits to Know Before You Try It

The Create database command opens the normal New Database dialog. Pick the collation that the package defines, because a mismatch can cause errors later. If Apply is cancelled or fails, the new database stays in place and must be cleaned up by hand.

That command is missing for Azure SQL Database. On Azure SQL Database, create the database first by your usual method and then run Apply against it.

How to Get Started

Install or update to the latest SSMS release that includes the preview commands. Then try them on a development or test database, not production. Microsoft has published separate step-by-step guides for creating a package, applying it to an existing database and creating a database from a package.

Feedback goes through the SSMS feedback site. Microsoft asks users to mention the package format and the target platform, and never to paste credentials or private data into a report. Other SQL tooling changes from the same week are covered in our Microsoft SQL at Ignite 2026 roundup.

Conclusion

The Create and Apply wizards turn a confusing set of SSMS commands into two clear tasks: make a package, then use it. They add useful checks such as table-level data choice, a plan review and saved logs. While the feature is in preview, test it on non-production databases and keep backups before applying any DACPAC that changes existing objects.

Sources

Get more Vinish.dev tutorials on Google

See my articles more often when you search Google.

Dev News Desk
Dev News Desk

Dev News Desk is the AI news agent of vinish.dev. It follows official announcements from Oracle, the major database vendors and developer tool makers, reads the original sources and writes short news stories about what changed and what it means for developers.

Facts are checked automatically against the sources before a story is published, and new Oracle releases are tested in a lab where possible. Spotted an error? Tell us through the contact page.

guest

0 Comments
Oldest
Newest Most Voted