Skip to content

Commit e4cd1e2

Browse files
committed
Merge branch 'set3' of https://github.com/CarlRabeler/azure-docs-pr into carl3
2 parents f717fc5 + 0b1c432 commit e4cd1e2

27 files changed

+80
-94
lines changed

articles/azure-sql/azure-sql-iaas-vs-paas-what-is-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Azure SQL Database offers the following deployment options:
8282

8383
### SQL Server on Azure VM
8484

85-
[**SQL Server on Azure VM**](virtual-machines/windows/sql-server-on-azure-vm-iaas-what-is-overview.md) falls into the industry category *Infrastructure-as-a-Service (IaaS)* and allows you to run SQL Server inside a fully-managed virtual machine (VM) in the Azure cloud. Best for migrations and applications requiring OS-level access. SQL virtual machines in Azure are lift-and-shift ready for existing applications that require fast migration to the cloud with minimal changes or no changes. SQL virtual machines offer full administrative control over the SQL Server instance and underlying OS for migration to Azure. Rapid development and test scenarios when you do not want to buy on-premises non-production SQL Server hardware. SQL virtual machines also run on standardized hardware that is owned, hosted, and maintained by Microsoft. When using SQL virtual machines, you can either pay-as-you-go for a SQL Server license already included in a SQL Server image or easily use an existing license. You can also stop or resume the VM as needed. SQL Server installed and hosted in the cloud runs on Windows Server or Linux virtual machines running on Azure, also known as an infrastructure as a service (IaaS). SQL virtual machines are a good option for migrating on-premises SQL Server databases and applications without any database change. All recent versions and editions of SQL Server are available for installation in an IaaS virtual machine. The most significant difference from SQL databases and SQL Managed Instances, is that SQL Server VMs allow full control over the database engine. You can choose when to start maintenance/patching, change the recovery model to simple or bulk-logged, pause or start the service when needed, and you can fully customize the SQL Server database engine. With this additional control comes the added responsibility to manage the virtual machine.
85+
[**SQL Server on Azure VM**](virtual-machines/windows/sql-server-on-azure-vm-iaas-what-is-overview.md) falls into the industry category *Infrastructure-as-a-Service (IaaS)* and allows you to run SQL Server inside a fully-managed virtual machine (VM) in the Azure cloud. Best for migrations and applications requiring OS-level access. SQL virtual machines in Azure are lift-and-shift ready for existing applications that require fast migration to the cloud with minimal changes or no changes. SQL virtual machines offer full administrative control over the SQL Server instance and underlying OS for migration to Azure. Rapid development and test scenarios when you do not want to buy on-premises non-production SQL Server hardware. SQL virtual machines also run on standardized hardware that is owned, hosted, and maintained by Microsoft. When using SQL virtual machines, you can either pay-as-you-go for a SQL Server license already included in a SQL Server image or easily use an existing license. You can also stop or resume the VM as needed. SQL Server installed and hosted in the cloud runs on Windows Server or Linux virtual machines running on Azure, also known as an infrastructure as a service (IaaS). SQL virtual machines are a good option for migrating on-premises SQL Server databases and applications without any database change. All recent versions and editions of SQL Server are available for installation in an IaaS virtual machine. The most significant difference from SQL Database and SQL Managed Instances, is that SQL Server on Azure VMs allow full control over the database engine. You can choose when to start maintenance/patching, change the recovery model to simple or bulk-logged, pause or start the service when needed, and you can fully customize the SQL Server database engine. With this additional control comes the added responsibility to manage the virtual machine.
8686

8787
Optimized for migrating existing applications to Azure or extending existing on-premises applications to the cloud in hybrid deployments. In addition, you can use SQL Server in a virtual machine to develop and test traditional SQL Server applications. With SQL virtual machines, you have the full administrative rights over a dedicated SQL Server instance and a cloud-based VM. It is a perfect choice when an organization already has IT resources available to maintain the virtual machines. These capabilities allow you to build a highly customized system to address your application’s specific performance and availability requirements.
8888

articles/azure-sql/database/doc-changes-updates-release-notes.md

Lines changed: 6 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,36 +1,20 @@
11
---
2-
title: What's new with Azure SQL Database & Azure SQL Managed Instance?
3-
titleSuffix:
4-
description: Learn about new features and improvements for Azure SQL Database & Azure SQL Managed Instance
2+
title: What's new?
3+
titleSuffix: Azure SQL Database & SQL Managed Instance
4+
description: Learn about the new features and improvements for the Azure SQL Database & SQL Managed Instance service and documentation
55
services: sql-database
66
author: stevestein
77
ms.service: sql-database
88
ms.subservice: service
99
ms.custom: sqldbrb=2
1010
ms.devlang:
1111
ms.topic: conceptual
12-
ms.date: 05/20/2020
12+
ms.date: 05/04/2020
1313
ms.author: sstein
1414
---
15-
# What's new in Azure SQL Database & Azure SQL Managed Instance?
16-
17-
This article lists features in public preview and current known issues with Azure SQL Database and Azure SQL Managed Instance.
18-
19-
For SQL Database and SQL Managed Instance updates and improvements, see [SQL Database & SQL Managed Instance service updates](https://azure.microsoft.com/updates/?product=sql-database).
20-
21-
## What's new?
22-
23-
Documentation for Azure SQL Database and Azure SQL Managed Instance has been split into separate sections. We've also updated how we refer to a managed instance from *Azure SQL Database managed instance* to *Azure SQL Managed Instance*.
24-
25-
We've done this because some features and functionality vary greatly between a single database and managed instance, and it's become increasingly more of a challenge to explain complex nuances between Azure SQL Database and Azure SQL Database Managed Instance in individual 'shared' articles.
26-
27-
This clarification between the different Azure SQL options should simplify and streamline the process of working with SQL in Azure, whether that be a single managed database in Azure SQL Database, a fully-fledged managed instance hosting multiple databases in Azure SQL Managed Instance, or the familiar on-premises SQL Server product but hosted on a virtual machine in Azure.
28-
29-
Consider that this is a work in progress and not every document has been updated yet. For example, Transact-SQL (T-SQL) statements, stored procedures, and many features shared between Azure SQL Database and Azure SQL Managed Instance are not yet complete, so please bear with us!
30-
31-
> [!NOTE]
32-
> The features, functionalities, and capabilities of the product are entirely unchanged. You are still able to deploy the same SQL Managed Instance from the same [Azure portal](https://portal.azure.com), and you can still leverage all of the features and functionalities that were previously available prior to the name change.
15+
# What's new in Azure SQL Database & SQL Managed Instance?
3316

17+
This article lists Azure SQL Database and Azure SQL Managed Instance features that are currently in public preview. For SQL Database and SQL Managed Instance updates and improvements, see [SQL Database & SQL Managed Instance service updates](https://azure.microsoft.com/updates/?product=sql-database). For updates and improvements to other Azure services, see [Service updates](https://azure.microsoft.com/updates).
3418

3519
## Features in public preview
3620

articles/azure-sql/database/firewall-create-server-level-portal-quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Sign in to the [Azure portal](https://portal.azure.com/).
3535
3636
Follow these steps to create a server-level IP firewall rule for your client's IP address and enable external connectivity through the Azure SQL Database firewall for your IP address only.
3737

38-
1. After the [prerequisite Azure SQL database](#prerequisites) deployment completes, select **SQL databases** from the left-hand menu and then choose **mySampleDatabase** on the **SQL databases** page. The overview page for your database opens, showing you the fully qualified server name (such as **mynewserver-20170824.database.windows.net**) and provides options for further configuration.
38+
1. After the [database](#prerequisites) deployment completes, select **SQL databases** from the left-hand menu and then choose **mySampleDatabase** on the **SQL databases** page. The overview page for your database opens, showing you the fully qualified server name (such as **mynewserver-20170824.database.windows.net**) and provides options for further configuration.
3939

4040
2. Copy this fully qualified server name to use when connecting to your server and its databases in other quickstarts.
4141

articles/azure-sql/database/logical-servers.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ To create a server (without a database, elastic pool, or data warehouse database
5050

5151
### Create a blank or sample SQL database in Azure SQL Database
5252

53-
To create an Azure SQL database using the [Azure portal](https://portal.azure.com), navigate to a blank SQL Database form and provide the requested information. You can create the resource group and server ahead of time or while creating the database itself. You can create a blank database or create a sample database based on Adventure Works LT.
53+
To create a database in SQL Database using the [Azure portal](https://portal.azure.com), navigate to a blank SQL Database form and provide the requested information. You can create the resource group and server ahead of time or while creating the database itself. You can create a blank database or create a sample database based on Adventure Works LT.
5454

5555
![create database-1](./media/logical-servers/create-database-1.png)
5656

@@ -70,7 +70,7 @@ To manage an existing database, navigate to the **SQL databases** page and click
7070
> [!IMPORTANT]
7171
> To configure performance properties for a database, see [DTU-based purchasing model](service-tiers-dtu.md) and [vCore-based purchasing model](service-tiers-vcore.md).
7272
> [!TIP]
73-
> For an Azure portal quickstart, see [Create an Azure SQL database in the Azure portal](single-database-create-quickstart.md).
73+
> For an Azure portal quickstart, see [Create a database in SQL Database in the Azure portal](single-database-create-quickstart.md).
7474
7575
## Manage servers, databases, and firewalls using PowerShell
7676

@@ -142,7 +142,7 @@ To create and manage servers, databases, and firewalls with Transact-SQL, use th
142142
| --- | --- |
143143
|[CREATE DATABASE (Azure SQL Database)](/sql/t-sql/statements/create-database-transact-sql?view=azuresqldb-current) | Creates a new database in Azure SQL Database. You must be connected to the master database to create a new database.|
144144
|[CREATE DATABASE (Azure Synapse)](/sql/t-sql/statements/create-database-transact-sql?view=azure-sqldw-latest) | Creates a new data warehouse database in Azure Synapse. You must be connected to the master database to create a new database.|
145-
| [ALTER DATABASE (Azure SQL Database)](/sql/t-sql/statements/alter-database-transact-sql?view=azuresqldb-current) |Modifies an Azure SQL database or elastic pool. |
145+
| [ALTER DATABASE (Azure SQL Database)](/sql/t-sql/statements/alter-database-transact-sql?view=azuresqldb-current) |Modifies database or elastic pool. |
146146
|[ALTER DATABASE (Azure SQL Data Warehouse)](/t-sql/statements/alter-database-transact-sql?view=azure-sqldw-latest)|Modifies a data warehouse database in Azure Synapse.|
147147
|[DROP DATABASE (Transact-SQL)](/sql/t-sql/statements/drop-database-transact-sql)|Deletes a database.|
148148
|[sys.database_service_objectives (Azure SQL Database)](/sql/relational-databases/system-catalog-views/sys-database-service-objectives-azure-sql-database)|Returns the edition (service tier), service objective (pricing tier), and elastic pool name, if any, for a database. If logged on to the master database for a server, returns information on all databases. For Azure Synapse, you must be connected to the master database.|

articles/azure-sql/database/quickstart-content-reference-guide.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,8 @@ In this section, you will see an overview of available articles that can help yo
2222

2323
- [Create a single database using the Azure portal](single-database-create-quickstart.md).
2424
- After creating the database, you would need to [secure your database by configuring firewall rules](firewall-create-server-level-portal-quickstart.md).
25-
- If you have an existing database on SQL Server that you want to migrate to Azure, you should install [Data Migration Assistant (DMA)](https://www.microsoft.com/download/details.aspx?id=53595) that will analyze your databases on SQL Server and find any issue that could block migration to the single database deployment option. If you don't find any issue, you can export your database as `.bacpac` file and [import it using the Azure portal or SqlPackage](database-import.md).
25+
- If you have an existing database on SQL Server that you want to migrate to Azure SQL Database, you should install [Data Migration Assistant (DMA)](https://www.microsoft.com/download/details.aspx?id=53595) that will analyze your databases on SQL Server and find any issue that could block migration. If you don't find any issue, you can export your database as `.bacpac` file and [import it using the Azure portal or SqlPackage](database-import.md).
26+
2627

2728
## Automating management operations
2829

@@ -33,13 +34,13 @@ You can use PowerShell or the Azure CLI to create, configure, and scale your dat
3334

3435
## Migrating to a single database with minimal downtime
3536

36-
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 deployment options within Azure SQL Database, 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)](https://docs.microsoft.com/azure/dms/tutorial-sql-server-to-azure-sql?toc=/azure/sql-database/toc.json) 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.
37+
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)](https://docs.microsoft.com/azure/dms/tutorial-sql-server-to-azure-sql?toc=/azure/sql-database/toc.json) 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.
3738

3839
## Hands-on learning modules
3940

4041
The following Microsoft Learn modules help you learn for free about Azure SQL Database.
4142

42-
- [Provision an Azure SQL database to store application data](https://docs.microsoft.com/learn/modules/provision-azure-sql-db/)
43+
- [Provision a database in SQL Database to store application data](https://docs.microsoft.com/learn/modules/provision-azure-sql-db/)
4344
- [Develop and configure an ASP.NET application that queries an Azure SQL Database](https://docs.microsoft.com/learn/modules/develop-app-that-queries-azure-sql/)
4445
- [Secure your Azure SQL Database](https://docs.microsoft.com/learn/modules/secure-your-azure-sql-database/)
4546

articles/azure-sql/database/r-script-create-quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ In this quickstart, you create and run a set of R scripts using Machine Learning
2525
## Prerequisites
2626

2727
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
28-
- An [Azure SQL database](single-database-create-quickstart.md) with a [server-level firewall rule](firewall-create-server-level-portal-quickstart.md)
28+
- A [database in Azure SQL Database](single-database-create-quickstart.md) with a [server-level firewall rule](firewall-create-server-level-portal-quickstart.md)
2929
- [Machine Learning Services](machine-learning-services-overview.md) with R enabled.
3030
- [SQL Server Management Studio](/sql/ssms/sql-server-management-studio-ssms) (SSMS)
3131

articles/azure-sql/database/r-train-score-model-create-quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ In this quickstart, you create and train a predictive model using R, save the mo
2525
## Prerequisites
2626

2727
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
28-
- An [Azure SQL database](single-database-create-quickstart.md) with a [server-level firewall rule](firewall-create-server-level-portal-quickstart.md)
28+
- A [database in Azure SQL Database](single-database-create-quickstart.md) with a [server-level firewall rule](firewall-create-server-level-portal-quickstart.md)
2929
- [Machine Learning Services](machine-learning-services-overview.md) with R enabled.
3030
- [SQL Server Management Studio](/sql/ssms/sql-server-management-studio-ssms) (SSMS)
3131

0 commit comments

Comments
 (0)