SQL projects feature (#36892)

Author: rwestMSFT

docs/tools/sql-database-projects/concepts/database-references.md

@@ -1,10 +1,10 @@
 ---
 title: Database References Overview
 description: Extend a SQL project with references to additional database components.
-author: dzsquared
-ms.author: drskwier
-ms.reviewer: maghan, randolphwest
-ms.date: 02/06/2026
+author: rwestMSFT
+ms.author: randolphwest
+ms.reviewer: drskwier
+ms.date: 03/11/2026
 ms.service: sql
 ms.subservice: sql-database-projects
 ms.topic: concept-article
@@ -161,6 +161,33 @@ The extension also prompts to select from the following reference locations:
 
 ::: zone-end
 
+:::zone pivot="sq1-sql-server-management-studio"
+
+To add a project reference to a SQL project, add an `<ItemGroup>` item to the `.sqlproj` file with an appropriate reference item for each database reference. For example, the following project reference is added to a SQL project to reference the `WorldWideImporters` project in a different database on a different server:
+
+```xml
+  <ItemGroup>
+    <ProjectReference Include="..\Contoso\WorldWideImporters.sqlproj">
+      <Name>WorldWideImporters</Name>
+      <Project>{d703fc7a-bc47-4aef-9dc5-cf01094ddb37}</Project>
+      <SuppressMissingDependenciesErrors>False</SuppressMissingDependenciesErrors>
+      <ServerSqlCmdVariable>WWIServer</ServerSqlCmdVariable>
+      <DatabaseSqlCmdVariable>WorldWideImporters</DatabaseSqlCmdVariable>
+    </ProjectReference>
+  </ItemGroup>
+```
+
+The project reference is used in a sample view definition in the SQL project:
+
+```sql
+CREATE VIEW dbo.WorldWide_Products
+AS
+SELECT ProductID, ProductName, SupplierID
+FROM [$(WWIServer)].[$(WorldWideImporters)].[Purchasing].[Suppliers]
+```
+
+:::zone-end
+
 ::: zone pivot="sq1-command-line"
 
 To add a project reference to a SQL project, add an `<ItemGroup>` item to the `.sqlproj` file with an appropriate reference item for each database reference. For example, the following project reference is added to a SQL project to reference the `WorldWideImporters` project in a different database on a different server:

docs/tools/sql-database-projects/concepts/package-references.md

@@ -1,18 +1,17 @@
 ---
 title: SQL Projects Package References
 description: Reference database objects with package references.
-author: dzsquared
-ms.author: drskwier
-ms.reviewer: maghan, randolphwest
-ms.date: 10/10/2025
+author: rwestMSFT
+ms.author: randolphwest
+ms.reviewer: drskwier
+ms.date: 03/11/2026
 ms.service: sql
 ms.subservice: sql-database-projects
 ms.topic: concept-article
 ms.collection:
   - data-tools
 ms.custom:
   - ignite-2024
-zone_pivot_groups: sq1-sql-projects-tools
 ---
 
 # SQL projects package references
@@ -66,7 +65,8 @@ The following example includes a package reference to the `Contoso.AdventureWork
 In this example, the AdventureWorks `.dacpac` file is published as a package `Contoso.AdventureWorks` version `1.1.0` to a NuGet feed. The `<DatabaseSqlCmdVariable>` element specifies the name of the database on the same server where the objects in the package are located and would be used to indicate this reference in three-part naming. The [SQLCMD variable](sqlcmd-variables.md) `AdventureDB` is used to set the database name at deployment time and is used in the project similarly to this example query:
 
 ```sql
-SELECT * FROM [$(AdventureDB)].dbo.Customers;
+SELECT *
+FROM [$(AdventureDB)].dbo.Customers;
 ```
 
 The `<DacpacName>` element specifies the name of the `.dacpac` file for the package reference, without the file extension or path. The `<DacpacName>` element is optional and is only required when the name of the `.dacpac` file is different from the name of the package.

docs/tools/sql-database-projects/concepts/pre-post-deployment-scripts.md

@@ -1,10 +1,10 @@
 ---
 title: Pre-Deployment and Post-Deployment Scripts
-description: "Add custom scripts for pre/post-deployment execution."
-author: dzsquared
-ms.author: drskwier
-ms.reviewer: maghan, randolphwest
-ms.date: 01/29/2026
+description: Add custom scripts for pre-deployment and post-deployment execution.
+author: rwestMSFT
+ms.author: randolphwest
+ms.reviewer: drskwier
+ms.date: 03/11/2026
 ms.service: sql
 ms.subservice: sql-database-projects
 ms.topic: concept-article
@@ -106,6 +106,14 @@ The script file is added to the project and opened in the query editor, where yo
 
 ::: zone-end
 
+:::zone pivot="sq1-sql-server-management-studio"
+
+In **Solution Explorer**, right-click the project node and select **Add** > **New Item**. The **Add New Item** dialog appears, select **Show All Templates** > **Table**, then select **Pre-Deployment Script** or **Post-Deployment Script**.
+
+The script file is added to the project and opened in the query editor, where you can complete the script. This script will be executed before or after the deployment plan is executed, every time the project is deployed.
+
+:::zone-end
+
 ::: zone pivot="sq1-command-line"
 
 Edit the `.sqlproj` file directly to add pre-deployment or post-deployment scripts. Add a `<PreDeploy>` or `<PostDeploy>` item to the `<ItemGroup>` section of the `.sqlproj` file.

docs/tools/sql-database-projects/concepts/schema-comparison.md

@@ -1,10 +1,10 @@
 ---
 title: Schema Comparison Overview
 description: Visualize the difference in database models with schema compare.
-author: dzsquared
-ms.author: drskwier
-ms.reviewer: maghan, randolphwest, tsiddique
-ms.date: 02/06/2026
+author: rwestMSFT
+ms.author: randolphwest
+ms.reviewer: drskwier, tsiddique
+ms.date: 03/11/2026
 ms.service: sql
 ms.subservice: sql-database-projects
 ms.topic: overview
@@ -201,9 +201,15 @@ To update the schema of the target, you have two options. You can update the tar
 
 ::: zone-end
 
+:::zone pivot="sq1-sql-server-management-studio"
+
+[!INCLUDE [schema-compare-where-found](../includes/schema-compare-where-found.md)]
+
+:::zone-end
+
 ::: zone pivot="sq1-command-line"
 
-[!INCLUDE [schema-compare-command-line](../includes/schema-compare-command-line.md)]
+[!INCLUDE [schema-compare-where-found](../includes/schema-compare-where-found.md)]
 
 ::: zone-end
 

docs/tools/sql-database-projects/concepts/sql-code-analysis/sql-code-analysis.md

@@ -1,10 +1,10 @@
 ---
-title: "SQL Code Analysis"
-description: "Analyzing Database Code to Improve Code Quality"
-author: dzsquared
-ms.author: drskwier
-ms.reviewer: maghan, randolphwest
-ms.date: 03/11/2025
+title: SQL Code Analysis
+description: Analyze database code to improve code quality.
+author: rwestMSFT
+ms.author: randolphwest
+ms.reviewer: drskwier
+ms.date: 03/11/2026
 ms.service: sql
 ms.subservice: sql-database-projects
 ms.topic: concept-article
@@ -82,7 +82,7 @@ A file `StaticCodeAnalysis.SuppressMessages.xml` can be added to the project to
 
 ## Provided rules
 
-### T-SQL Design Issues
+### T-SQL design issues
 
 When you analyze the T-SQL code in your database project, one or more warnings might be categorized as design issues. You should address design issues to avoid the following situations:
 
@@ -118,7 +118,7 @@ The provided rules identify the following design issues:
 - [SR0012: Avoid using reserved words for type names](./t-sql-naming-issues.md#sr0012-avoid-using-reserved-words-for-type-names)
 - [SR0016: Avoid using sp_ as a prefix for stored procedures](./t-sql-naming-issues.md#sr0016-avoid-using-sp_-as-a-prefix-for-stored-procedures)
 
-### T-SQL Performance Issues
+### T-SQL performance issues
 
 When you analyze the T-SQL code in your database project, one or more warnings might be categorized as performance issues. You should address a performance issue to avoid the following situation:
 
@@ -160,6 +160,14 @@ From the text editor, add an element `<RunSqlCodeAnalysis>True</RunSqlCodeAnalys
 
 ::: zone-end
 
+:::zone pivot="sq1-sql-server-management-studio"
+
+To enable or disable SQL code analysis in SQL Server Management Studio (SSMS), right-click the project in **Solution Explorer** and select **Properties**. In the **Code Analysis** tab of the properties window, select the desired code analysis settings.
+
+To disable a specific rule or to change the severity of a rule, select the corresponding option from the dropdown list for that rule from the rule list.
+
+:::zone-end
+
 ::: zone pivot="sq1-command-line"
 
 To override the code analysis settings in the project file, you can use the `/p:RunSqlCodeAnalysis` and `/p:SqlCodeAnalysisRules` properties with the `dotnet build` command. For example, to build with code analysis disabled:

docs/tools/sql-database-projects/concepts/sqlcmd-variables.md

@@ -1,19 +1,19 @@
 ---
 title: SQLCMD Variables in SQL Projects
-description: "Dynamically set values in a SQL project at deployment."
-author: dzsquared
-ms.author: drskwier
-ms.reviewer: maghan, randolphwest
-ms.date: 08/30/2024
+description: Dynamically set values in a SQL project at deployment.
+author: rwestMSFT
+ms.author: randolphwest
+ms.reviewer: drskwier
+ms.date: 03/11/2026
 ms.service: sql
 ms.subservice: sql-database-projects
 ms.topic: concept-article
 ms.collection:
   - data-tools
-zone_pivot_groups: sq1-sql-projects-tools
 ms.custom:
   - ignite-2024
   - sfi-ropc-nochange
+zone_pivot_groups: sq1-sql-projects-tools
 ---
 
 # SQLCMD variables overview
@@ -92,6 +92,16 @@ When you publish the project from the SQL Database Projects extension, SQLCMD va
 
 ::: zone-end
 
+:::zone pivot="sq1-sql-server-management-studio"
+
+To add a SQLCMD variable to a SQL project in SQL Server Management Studio (SSMS), right-click the project in **Solution Explorer** and select **Properties**. In the **SQLCMD Variables** section of the properties window, specify the variable name and optionally a default value.
+
+Once the variable is defined, it can be used in SQL scripts by wrapping the variable name in `$(variableName)` syntax.
+
+When you publish the project from SSMS, SQLCMD variables are set in the publish dialog.
+
+:::zone-end
+
 ::: zone pivot="sq1-command-line"
 
 To add a SQLCMD variable to a SQL project, add an `<ItemGroup>` item to the `.sqlproj` file with a `<SqlCmdVariable>` item for each variable. The `<SqlCmdVariable>` item includes the variable name, a default value, and a value that can be set at deployment time.

docs/tools/sql-database-projects/concepts/target-platform.md

@@ -1,10 +1,10 @@
 ---
 title: SQL Projects Target Platform
-description: "Specify SQL version compatibility for SQL database projects."
-author: dzsquared
-ms.author: drskwier
-ms.reviewer: maghan, randolphwest
-ms.date: 03/11/2025
+description: Specify SQL version compatibility for SQL database projects.
+author: rwestMSFT
+ms.author: randolphwest
+ms.reviewer: drskwier
+ms.date: 03/11/2026
 ms.service: sql
 ms.subservice: sql-database-projects
 ms.topic: concept-article
@@ -73,6 +73,12 @@ Alternatively, you can edit the `.sqlproj` file directly to change the target pl
 
 ::: zone-end
 
+:::zone pivot="sq1-sql-server-management-studio"
+
+To change the target platform of a SQL project in SQL Server Management Studio (SSMS), right-click the project in **Solution Explorer** and select **Properties**. In the **Project Settings** tab of the properties window, select the desired target platform from the **Target platform** dropdown list.
+
+:::zone-end
+
 ::: zone pivot="sq1-command-line"
 
 To build a SQL project for a target platform different than the target platform specified in the `.sqlproj` file, use the `/p:DSP=` command line argument. For example, to build a SQL project for SQL Server 2019 compatibility:

docs/tools/sql-database-projects/get-started.md

@@ -1,10 +1,10 @@
 ---
 title: Get Started with SQL Database Projects
 description: A SQL database project is a local representation of SQL objects that comprise the schema for a single database, such as tables, stored procedures, or functions.
-author: dzsquared
-ms.author: drskwier
-ms.reviewer: maghan, randolphwest
-ms.date: 01/29/2026
+author: rwestMSFT
+ms.author: randolphwest
+ms.reviewer: drskwier
+ms.date: 03/11/2026
 ms.service: sql
 ms.subservice: sql-database-projects
 ms.topic: get-started
@@ -33,31 +33,39 @@ This article steps through creating a new SQL project, adding objects to the pro
 
 ::: zone pivot="sq1-visual-studio"
 
-- [.NET 8 SDK](https://dotnet.microsoft.com/download/dotnet/8.0)
+- [.NET SDK](https://dotnet.microsoft.com/download/dotnet/10.0)
 - [Visual Studio 2022 Community, Professional, or Enterprise](https://visualstudio.microsoft.com/downloads/)
 - [Install SQL Server Data Tools (SSDT) for Visual Studio](../../ssdt/download-sql-server-data-tools-ssdt.md)
 
 ::: zone-end
 
 ::: zone pivot="sq1-visual-studio-sdk"
 
-- [.NET 8 SDK](https://dotnet.microsoft.com/download/dotnet/8.0)
+- [.NET SDK](https://dotnet.microsoft.com/download/dotnet/10.0)
 - [Visual Studio 2022 Community, Professional, or Enterprise](https://visualstudio.microsoft.com/downloads/)
-- [SQL Server Data Tools, SDK-style (preview) installed in Visual Studio](../../ssdt/sql-server-data-tools-sdk-style.md)
+- [SQL Server Data Tools, SDK-style (preview)](../../ssdt/sql-server-data-tools-sdk-style.md)
 
 ::: zone-end
 
 ::: zone pivot="sq1-visual-studio-code"
 
-- [.NET 8 SDK](https://dotnet.microsoft.com/download/dotnet/8.0)
+- [.NET SDK](https://dotnet.microsoft.com/download/dotnet/10.0)
 - [VS Code](https://code.visualstudio.com/Download)
 - [SQL Database Projects extension](../visual-studio-code-extensions/sql-database-projects/sql-database-projects-extension.md)
 
 ::: zone-end
 
+:::zone pivot="sq1-sql-server-management-studio"
+
+- [.NET SDK](https://dotnet.microsoft.com/download/dotnet/10.0)
+- [SQL Server Management Studio (SSMS)](/ssms/install/install)
+- [Database DevOps workload installed in SSMS](/ssms/database-devops)
+
+:::zone-end
+
 ::: zone pivot="sq1-command-line"
 
-- [.NET 8 SDK](https://dotnet.microsoft.com/download/dotnet/8.0)
+- [.NET SDK](https://dotnet.microsoft.com/download/dotnet/10.0)
 - [SqlPackage CLI](../sqlpackage/sqlpackage-download.md)
 - [Microsoft.Build.Sql.Templates .NET templates](https://www.nuget.org/packages/Microsoft.Build.Sql.Templates/)
 
@@ -124,6 +132,20 @@ Once completed, the empty project is opened and visible in the **Database Projec
 
 ::: zone-end
 
+:::zone pivot="sq1-sql-server-management-studio"
+
+Select **File**, **New**, then **Project**.
+
+In the **New Project** dialog box, use the term **SQL Server** in the search box. The top result should be **SQL Server Database Project**.
+
+:::image type="content" source="media/getting-started/new-project-dialog-ssms.png" alt-text="Screenshot of New project dialog." lightbox="media/getting-started/new-project-dialog-ssms.png":::
+
+Select **Next** to proceed to the next step. Provide a project name, which doesn't need to match a database name. Verify and modify the project location as needed.
+
+Select **Create** to create the project. The empty project is opened and visible in the **Solution Explorer** for editing.
+
+:::zone-end
+
 ::: zone pivot="sq1-command-line"
 
 With the .NET templates for Microsoft.Build.Sql projects installed, you can create a new SQL database project from the command line. The `-n` option specifies the name of the project, and the `-tp` option specifies the project target platform.
@@ -169,6 +191,16 @@ More database objects can be added through the context menu on the project node,
 
 ::: zone-end
 
+::: zone pivot="sq1-sql-server-management-studio"
+
+In **Solution Explorer**, right-click the project node and select **Add**, then **New Item**. The **Add New Item** dialog appears, select **Show All Templates** and then **Table**. Specify the table name as the file name and select **Add** to create the table in the SQL project.
+
+The table is opened in the SSMS query editor with the template table definition, where you can add columns, indexes, and other table properties. Save the file when you're done making the initial edits.
+
+More database objects can be added through the **Add New Item** dialog, such as views, stored procedures, and functions. Access the dialog by right-clicking the project node in **Solution Explorer** and selecting **Add**, then the desired object type after **Show All Templates**. Files in the project can be organized into folders through the **New Folder** option under **Add**.
+
+::: zone-end
+
 ::: zone pivot="sq1-command-line"
 
 Files can be added to the project by creating them in the project directory or nested folders. The file extension should be `.sql` and organization by object type or schema and object type is recommended.
@@ -212,6 +244,14 @@ The output window automatically opens to display the build process. If there are
 
 ::: zone-end
 
+::: zone pivot="sq1-sql-server-management-studio"
+
+In **Solution Explorer**, right-click the project node and select **Build**.
+
+The output window automatically opens to display the build process. If there are errors or warnings, they're displayed in the output window. On a successful build, the build artifact (`.dacpac` file) is created its location is included in the build output (default is `bin\Debug\projectname.dacpac`).
+
+::: zone-end
+
 ::: zone pivot="sq1-command-line"
 
 SQL database projects can be built from the command line using the `dotnet build` command.
@@ -266,6 +306,16 @@ After the connection is configured, the deployment process will begin. You can c
 
 ::: zone-end
 
+::: zone pivot="sq1-sql-server-management-studio"
+
+In **Solution Explorer**, right-click the project node and select **Publish...**.
+
+The publish dialog opens, where you establish the **target database connection**. If you don't have an existing SQL instance for deployment, LocalDB (`(localdb)\MSSQLLocalDB`) is installed with Visual Studio and can be used for testing and development.
+
+Specify a database name and select **Publish** to deploy the project to the target database or **Generate Script** to generate a script to review before executing.
+
+::: zone-end
+
 ::: zone pivot="sq1-command-line"
 
 The SqlPackage CLI is used to deploy a `.dacpac` file to a target database with the [publish action](../sqlpackage/sqlpackage-publish.md).