Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to:
Azure SQL Database
A single database is fully managed platform as a service (PaaS) database as a service (DbaaS) that is ideal storage engine for the modern cloud-born applications. In this section, you'll learn how to quickly configure and create a single database in Azure SQL Database.
In this section, you'll see an overview of available articles that can help you to quickly get started with single databases. The following quickstarts enable you to quickly create a single database, configure a server-level firewall rule, and then import a database into the new single database using a .bacpac
file:
- Create a single database using the Azure portal.
- After creating the database, you would need to secure your database by configuring firewall rules.
You can use PowerShell or the Azure CLI to create, configure, and scale your database.
- Create and configure a single database using PowerShell or Azure CLI
- Update your single database and scale resources using PowerShell or Azure CLI
These quickstarts enable you to quickly create or import your database to Azure using a .bacpac
file. However, .bacpac
and .dacpac
files are designed to quickly move databases across different versions of SQL Server and within Azure SQL, or to implement continuous integration in your DevOps pipeline. However, this method is not designed for migration of your production databases with minimal downtime, because you would need to stop adding new data, wait for the export of the source database to a .bacpac
file to complete, and then wait for the import into Azure SQL Database to complete. All of this waiting results in downtime of your application, especially for large databases. To move your production database, you need a better way to migrate that guarantees minimal downtime of migration. For this, use the Data Migration Service (DMS) to migrate your database with the minimal downtime. DMS accomplishes this by incrementally pushing the changes made in your source database to the single database being restored. This way, you can quickly switch your application from source to target database with the minimal downtime.
- Features comparison: Azure SQL Database and Azure SQL Managed Instance
- Tutorial: Secure a database in Azure SQL Database
- Configure and manage content reference - Azure SQL Database
- Azure PowerShell samples for Azure SQL Database
- the Azure CLI
- Create and manage servers and single databases in Azure SQL Database