Merge branch 'main' of https://github.com/MicrosoftDocs/sql-docs-pr into fixes

Author: MashaMSFT

azure-sql/database/auditing-overview.md

@@ -39,7 +39,6 @@ You can use SQL Database auditing to:
 
 ### Auditing limitations
 
-- **User managed identity** authentication type for enabling auditing to **storage behind firewall** is not currently supported.
 - Enabling auditing on a paused **Azure Synapse** is not supported. To enable auditing, resume Azure Synapse.
 - Auditing for **Azure Synapse SQL pools** supports default audit action groups **only**.
 - When you configure the auditing for your [logical server in Azure](logical-servers.md) or Azure SQL Database with log destination as the storage account, the target storage account must be enabled with access to storage account keys. If the storage account is configured to use Azure AD authentication only and not configured for access key usage, the auditing cannot be configured. <!-- REST API reference: - /rest/api/sql/2021-08-01-preview/server-blob-auditing-policies/create-or-update -->

azure-sql/database/high-availability-sla.md

@@ -96,8 +96,9 @@ Consider the following when using zone redundancy:
 
 
 During preview, zone redundancy for SQL Managed Instance is available in the Business Critical service tier and supported in the following regions:
+
 | Geography | Regions supporting zone redundancy for Business Critical service tier |
-|:-- |:-- |
+| :--- | :--- |
 | Europe, Middle East, Africa | North Europe, Norway East, South Africa North, Sweden Central, Switzerland North, West Europe, UAE North, UK South |
 | Americas | Brazil South, Canada Central, East US, South Central US, West US 3 |
 | Asia Pacific | Australia East, East Asia, India Central, Japan East, Korea Central |

azure-sql/database/resource-limits-vcore-single-databases.md

@@ -217,8 +217,6 @@ The [serverless compute tier](serverless-tier-overview.md) is currently availabl
 <sup>2</sup> Besides local SSD IO, workloads will use remote [page server](hyperscale-architecture.md#page-server) IO. Effective IOPS will depend on workload. For details, see [Data IO Governance](resource-limits-logical-server.md#resource-governance), and [Data IO in resource utilization statistics](hyperscale-performance-diagnostics.md#data-io-in-resource-utilization-statistics).   
 <sup>3</sup> Latency is 1-2 ms for data on local compute replica SSD, which caches most used data pages. Higher latency for data retrieved from page servers. 
 
-## Hyperscale - provisioned compute - Gen5
-
 ## <a id="hyperscale---provisioned-compute---gen5"></a>Hyperscale - provisioned compute - standard-series (Gen5)
 
 ### <a id="gen5-hardware-part-1-2"></a>Hyperscale Standard-series (Gen5) compute generation (part 1 of 2)
@@ -1174,4 +1172,4 @@ This section includes details on previously available hardware.
 - For information about general Azure limits, see [Azure subscription and service limits, quotas, and constraints](/azure/azure-resource-manager/management/azure-subscription-service-limits).
 - For information about resource limits on a server, see [overview of resource limits on a server](resource-limits-logical-server.md) for information about limits at the server and subscription levels.
 - [ALTER DATABASE - Azure SQL Database](/sql/t-sql/statements/alter-database-transact-sql?view=azuresqldb-current&preserve-view=true)
-- [CREATE DATABASE - Azure SQL Database](/sql/t-sql/statements/create-database-transact-sql?view=azuresqldb-current&preserve-view=true)
+- [CREATE DATABASE - Azure SQL Database](/sql/t-sql/statements/create-database-transact-sql?view=azuresqldb-current&preserve-view=true)

azure-sql/managed-instance/log-replay-service-migrate.md

@@ -42,7 +42,7 @@ Make sure that you meet the following requirements for SQL Server:
 - A log backup (not split for a transaction log file).
 - For SQL Server versions 2008 to 2016, take a backup locally and [manually upload](#copy-existing-backups-to-your-blob-storage-account) it to your Azure Blob Storage account. 
 - For SQL Server 2016 and later, you can [take your backup directly](#take-backups-directly-to-your-blob-storage-account) to your Azure Blob Storage account. 
-- For SQL Server 2022, you can choose to use a managed identity instead of a shared access signature (SAS) token to authenticate to your Azure Blob Storage account. 
+
 
 
 Although having `CHECKSUM` enabled for backups isn't required, we highly recommend it for faster restore operations. 
@@ -314,11 +314,7 @@ After your backups are ready, and you want to start migrating databases to a man
 
 If you're on a supported version of SQL Server (starting with SQL Server 2012 SP1 CU2 and SQL Server 2014), and your corporate and network policies allow it, you can take backups from SQL Server directly to your Blob Storage account by using the native SQL Server [BACKUP TO URL](/sql/relational-databases/backup-restore/sql-server-backup-to-url) option. If you can use `BACKUP TO URL`, you don't need to take backups to local storage and upload them to your Blob Storage account.
 
-When you take native backups directly to your Blob Storage account, you have to authenticate to the storage account. You can do so by using a SAS token or, if you're on SQL Server 2022, you can also use a managed identity.  
-
-
-
-### [SAS token](#tab/sas-token)
+When you take native backups directly to your Blob Storage account, you have to authenticate to the storage account. 
 
 Use the following command to create a credential that imports the SAS token to your SQL Server instance: 
 
@@ -331,20 +327,6 @@ SECRET = '<SAS_TOKEN>';
 For detailed instructions working with SAS tokens, review the tutorial [Use Azure Blob Storage with SQL Server](/sql/relational-databases/tutorial-use-azure-blob-storage-service-with-sql-server-2016#1---create-stored-access-policy-and-shared-access-storage).
 
 
-
-### [Managed identity](#tab/managed-identity)
-
-SQL Server 2022 has added support for managed identities. If you're on SQL Server 2022, you can authenticate to your storage account by using a managed identity. 
-
-Use the following command to create a credential that uses the managed identity on your SQL Server instance: 
-
-```sql
-CREATE CREDENTIAL [https://<mystorageaccountname>.blob.core.windows.net/<containername>] 
-WITH IDENTITY = 'MANAGED IDENTITY'
-```
-
----
-
 After you've created the credential to authenticate your SQL Server instance with Blob Storage, you can use the [BACKUP TO URL](/sql/relational-databases/backup-restore/sql-server-backup-to-url) command to take backups directly to the storage account. `CHECKSUM` is recommended, but not required. 
 
 

azure-sql/managed-instance/managed-instance-link-feature-overview.md

@@ -28,7 +28,7 @@ The link supports single node SQL Server instances without existing availability
 
 The link feature currently offers the following functionality:
 
-- **One-way replication (SQL Server versions 2017 to 2019)**: Use the link feature to replicate data one way from a SQL Server instance to your managed instance. Although you can manually fail over to your managed instance if there's a disaster, doing so breaks the link, and failing back isn't supported. 
+- **One-way replication (SQL Server versions 2016 to 2019)**: Use the link feature to replicate data one way from a SQL Server instance to your managed instance. Although you can manually fail over to your managed instance if there's a disaster, doing so breaks the link, and failing back isn't supported. 
 - **Disaster recovery (SQL Server 2022)**: Use the link feature to replicate data from a SQL Server 2022 instance to your managed instance, manually fail over to your managed instance during a disaster, and fail back to the SQL Server instance after you've mitigated the disaster.  
 
     This feature is currently in limited public preview. [You must sign up for limited public preview](https://aka.ms/mi-link-dr-preview-signup) so that the product group can configure your environment for the preview. 

docs/azure-data-studio/extensions/sql-database-project-extension-sdk-style-projects.md

@@ -1,21 +1,21 @@
 ---
 title: Use SDK-style projects with the SQL Database Projects extension
-description: Getting started using SDK-style SQL projects with the SQL Database Projects extension for Azure Data Studio or VS Code
+description: Getting started using SDK-style SQL projects with the SQL Database Projects extension for Azure Data Studio or Visual Studio Code
 author: dzsquared
 ms.author: drskwier
 ms.reviewer: maghan
-ms.date: 5/24/2022
+ms.date: 2/14/2023
 ms.service: azure-data-studio
 ms.topic: conceptual
 ms.custom: intro-get-started
 ---
 
 # Use SDK-style SQL projects with the SQL Database Projects extension (Preview)
 
-This article introduces [Microsoft.Build.Sql](https://www.nuget.org/packages/Microsoft.Build.Sql) for SDK-style SQL projects  in the SQL Database Projects extension in Azure Data Studio or VS Code. SDK-style SQL projects are especially advantageous for applications shipped through pipelines or built in cross-platform environments.  The initial announcement is available in [TechCommunity](https://techcommunity.microsoft.com/t5/azure-sql-blog/microsoft-build-sql-the-next-frontier-of-sql-projects/ba-p/3290628).
+This article introduces [Microsoft.Build.Sql](https://www.nuget.org/packages/Microsoft.Build.Sql) for SDK-style SQL projects in the SQL Database Projects extension in Azure Data Studio or Visual Studio Code. SDK-style SQL projects are especially advantageous for applications shipped through pipelines or built in cross-platform environments.  The initial announcement is available in [TechCommunity](https://techcommunity.microsoft.com/t5/azure-sql-blog/microsoft-build-sql-the-next-frontier-of-sql-projects/ba-p/3290628).
 
 > [!NOTE]
-> The SDK-style SQL projects is currently in preview. 
+> Microsoft.Build.Sql is currently in preview. 
 
 ## Create an SDK-style database project
 
@@ -29,23 +29,132 @@ By default the selection for **SDK-style project (Preview)** is checked. When th
 
 ### From an existing database
 
-In the **Project** view, select the **Import Project from Database** button and connect to a SQL Server.  Once the connection is established, select a database from the list of available databases and set the name of the project.  Select a target structure of the extraction.  
+In the **Project** view, select the **Create Project from Database** button and connect to a SQL Server.  Once the connection is established, select a database from the list of available databases and set the name of the project.  Select a target structure of the extraction.  
 
 By default the selection for **SDK-style project (Preview)** is checked. When the dialog is completed, the new project is opened and contains SQL scripts for the contents of the selected database.
 
 ## Build and publish
 
-From the Azure Data Studio and VS Code interfaces, building and publishing an SDK-style SQL project is completed in the same way as the previous SQL project format. For more on this process, see [Build and Publish a Project](sql-database-project-extension-build.md).
+From the Azure Data Studio and Visual Studio Code interfaces, building and publishing an SDK-style SQL project is completed in the same way as the previous SQL project format. For more on this process, see [Build and Publish a Project](sql-database-project-extension-build.md).
 
 To build an SDK-style SQL project from the command line on Windows, macOS, or Linux, use the following command:
 
 ```bash
-dotnet build /p:NetCoreBuild=true
+dotnet build
 ```
 
-The `.dacpac` resulting from building an SDK-style SQL project is compatible with tooling associated with the data-tier application framework (`.dacpac`, `.bacpac`), including [SqlPackage](../../tools/sqlpackage/sqlpackage-publish.md).
+The `.dacpac` file resulting from building an SDK-style SQL project is compatible with tooling associated with the data-tier application framework (`.dacpac`, `.bacpac`), including [SqlPackage](../../tools/sqlpackage/sqlpackage-publish.md) and GitHub [sql-action](https://github.com/azure/sql-action).
+
+## Project capabilities
+In SQL projects there are several capabilities that can be specified in the `.sqlproj` file that impact the database model either at project build or deployment.  The following sections describe some of these capabilities that are available for Microsoft.Build.Sql projects.
+
+### Target platform
+The target platform property is contained in the `DSP` tag in the `.sqlproj` file under the `<PropertyGroup>` item.  The target platform is used during project build to validate support for features included in the project and is added to the `.dacpac` file as a property.  By default, during deployment, the target platform is checked against the target database to ensure compatibility.  If the target platform is not supported by the target database, the deployment fails unless an override [publish option](../../tools/sqlpackage/sqlpackage-publish.md) is specified.
+
+```xml
+<Project DefaultTargets="Build">
+  <Sdk Name="Microsoft.Build.Sql" Version="0.1.9-preview" />
+  <PropertyGroup>
+    <Name>AdventureWorks</Name>
+    <DSP>Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider</DSP>
+  </PropertyGroup>
+```
+
+Valid settings for the target platform are:
+- `Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider`
+- `Microsoft.Data.Tools.Schema.Sql.Sql130DatabaseSchemaProvider`
+- `Microsoft.Data.Tools.Schema.Sql.Sql140DatabaseSchemaProvider`
+- `Microsoft.Data.Tools.Schema.Sql.Sql150DatabaseSchemaProvider`
+- `Microsoft.Data.Tools.Schema.Sql.Sql160DatabaseSchemaProvider`
+- `Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider`
+- `Microsoft.Data.Tools.Schema.Sql.SqlDwDatabaseSchemaProvider`
+
+### Database references
+The database model validation at build time can be extended past the contents of the SQL project through database references. Database references specified in the `.sqlproj` file can reference another SQL project or a `.dacpac` file, representing either another database or more components of the same database.
+
+The following attributes are available for database references that represent another database:
+- **DatabaseSqlCmdVariable:** the value is the name of the variable that is used to reference the database
+    - Reference setting: `<DatabaseSqlCmdVariable>SomeOtherDatabase</DatabaseSqlCmdVariable>`
+    - Usage example: `SELECT * FROM [$(SomeOtherDatabase)].dbo.Table1`
+- **ServerSqlCmdVariable:** the value is the name of the variable that is used to reference the server where the database resides. used with DatabaseSqlCmdVariable, when the database is in another server.
+    - Reference setting: `<ServerSqlCmdVariable>SomeOtherServer</ServerSqlCmdVariable>`
+    - Usage example: `SELECT * FROM [$(SomeOtherServer)].[$(SomeOtherDatabase)].dbo.Table1`
+- **DatabaseVariableLiteralValue:** the value is the literal name of the database as used in the SQL project, similar to `DatabaseSqlCmdVariable` but the reference to other database is a literal value
+    - Reference setting: `<DatabaseVariableLiteralValue>SomeOtherDatabase</DatabaseVariableLiteralValue>`
+    - Usage example: `SELECT * FROM [SomeOtherDatabase].dbo.Table1`
+
+In a SQL project file, a database reference is specified as an `ArtifactReference` item with the `Include` attribute set to the path of the `.dacpac` file.
+
+```xml
+  <ItemGroup>
+    <ArtifactReference Include="SampleA.dacpac">
+      <DatabaseSqlCmdVariable>DatabaseA</DatabaseSqlCmdVariable>
+    </ArtifactReference>
+  </ItemGroup>
+</Project>
+```
+
+### Package references
+Package references are used to reference NuGet packages that contain a `.dacpac` file and are used to extend the database model at build time similarly as a [database reference](#database-references).
+
+The following example from a SQL project file references the `Microsoft.SqlServer.Dacpacs` [package](https://www.nuget.org/packages/Microsoft.SqlServer.Dacpacs) for the `master` database.
+
+```xml
+  <ItemGroup>
+    <PackageReference Include="Microsoft.SqlServer.Dacpacs" Version="160.0.0" />
+  </ItemGroup>
+</Project>
+```
+
+In addition to the attributes available for [database references](#database-references), the following `DacpacName` attribute can be specified to select a `.dacpac` from a package that contains multiple `.dacpac` files.
+
+```xml
+  <ItemGroup>
+    <PackageReference Include="Microsoft.SqlServer.Dacpacs" Version="160.0.0" />
+      <DacpacName>msdb</DacpacName>
+    </PackageReference>
+  </ItemGroup>
+</Project>
+```
+
+### SqlCmd variables
+SqlCmd variables can be defined in the `.sqlproj` file and are used to replace tokens in SQL objects and scripts during `.dacpac` [deployment](../../tools/sqlpackage/sqlpackage-publish.md#sqlcmd-variables). The following example from a SQL project file defines a variable named `EnvironmentName` that available for use in the project's objects and scripts.
+
+```xml
+  <ItemGroup>
+    <SqlCmdVariable Include="EnvironmentName">
+      <DefaultValue>testing</DefaultValue>
+      <Value>$(SqlCmdVar__1)</Value>
+    </SqlCmdVariable>
+  </ItemGroup>
+</Project>
+```
+
+```sql
+IF '$(EnvironmentName)' = 'testing'
+BEING
+    -- do something
+END
+```
+
+When a compiled SQL project (`.dacpac`) is deployed, the value of the variable is replaced with the value specified in the deployment command.  For example, the following command deploys the `AdventureWorks.dacpac` and sets the value of the `EnvironmentName` variable to `production`.
+
+```bash
+SqlPackage /Action:Publish /SourceFile:AdventureWorks.dacpac /TargetConnectionString:{connection_string_here} /v:EnvironmentName=production
+```
+
+### Pre/post-deployment scripts
+Pre- and post-deployment scripts are SQL scripts that are included in the project to be executed during deployment. Pre/post-deployment scripts are included in the `.dacpac` but they are not compiled into or validated with database object model. A pre-deployment script is executed before the database model is applied and a post-deployment script is executed after the database model is applied.  The following example from a SQL project file adds the file `populate-app-settings.sql` as post-deployment script.
+
+```xml
+  <ItemGroup>
+    <PostDeploy Include="populate-app-settings.sql" />
+  </ItemGroup>
+</Project>
+```
 
 
 ## Next steps
 
 - [Build and Publish a project with the SQL Database Projects extension](sql-database-project-extension-build.md)
+- [Install SqlPackage for deployment from the CLI](../../tools/sqlpackage/sqlpackage-download.md)