Azure SQL Database don't have SQL-Agent and also don't support cross-database access, so it is not possible to use DacPac/BacPac nor your database in complete in your scenario.
Use a VM with a full SQL Server, similar to an onpremise solution.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am using sqlpackage
to export and import my Azure SQL Database as .bacpac
files. My database contains:
##MS_JobAccount##
userI need to export the entire database with all objects (including SQL Agent jobs, job-related accounts like ##MS_JobAccount##
, and external users) and be able to import it into a new Azure SQL Database, ensuring that the newly created database is an exact replica of the original database — including all users, permissions, schemas, and job-related objects.
However, I’m encountering issues with SQL Agent-related objects and external users during the import process. Is there a direct and supported way using sqlpackage
to achieve a full export and import of the Azure SQL Database, ensuring that no objects or users are lost in the process?
Would appreciate guidance on the recommended approach to achieve this, especially for databases that rely on SQL Agent-related objects and external users.
Azure SQL Database don't have SQL-Agent and also don't support cross-database access, so it is not possible to use DacPac/BacPac nor your database in complete in your scenario.
Use a VM with a full SQL Server, similar to an onpremise solution.