fix links related to removed files

markingmyname · markingmyname · commit bac91ba21633 · 2024-03-29T23:22:21.000-05:00
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -41480,6 +41480,11 @@
       "redirect_url": "/sql/ssdt/sql-server-data-tools.md",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/ssdt/connected-database-development.md",
+      "redirect_url": "/sql/ssdt/sql-server-data-tools.md",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/ssms/about-dialog-box.md",
       "redirect_url": "/sql/ssms/download-sql-server-management-studio-ssms",
diff --git a/docs/ssdt/extract-publish-and-register-dacpac-files.md b/docs/ssdt/extract-publish-and-register-dacpac-files.md
@@ -57,5 +57,5 @@ In the **Register Data-tier Application** dialog box, specify the properties of
 Unregistering allows you to remove the metadata for a registered data-tier application from the instance. Unregistering does not delete the registered database.  
   
 ## See Also  
-[Connected Database Development](../ssdt/connected-database-development.md)  
+[Manage Tables, Relationships, and Fix Errors](../ssdt/manage-tables-relationships-and-fix-errors.md) 
   
diff --git a/docs/ssdt/how-to-browse-objects-in-a-sql-server-database-project.md b/docs/ssdt/how-to-browse-objects-in-a-sql-server-database-project.md
@@ -22,5 +22,5 @@ The SQL Server Object Explorer in Visual Studio now contains a dedicated Project
 3.  In **SQL Server Object Explorer**, expand the **Projects** node to see all the current SQL Server database projects in your solution under the **Projects** node.  
   
 ## See Also  
-[Connected Database Development](../ssdt/connected-database-development.md)  
+[Manage Tables, Relationships, and Fix Errors](../ssdt/manage-tables-relationships-and-fix-errors.md) 
   
diff --git a/docs/ssdt/how-to-change-target-platform-and-publish-a-database-project.md b/docs/ssdt/how-to-change-target-platform-and-publish-a-database-project.md
@@ -18,9 +18,6 @@ You can change the target SQL Server version for your SQL Server Data Tools (SSD
   
 SSDT also makes this task simple by being aware of your target platform and automatically detecting any error in your code (for example., when you are using unsupported features for a project that is going to be published to SQL Azure).  
   
-> [!WARNING]  
-> The following procedures utilize entities created in previous procedures in the [Connected Database Development](../ssdt/connected-database-development.md) and [Project-Oriented Offline Database Development](../ssdt/project-oriented-offline-database-development.md) sections.  
-  
 ### To change a project's target platform  
   
 1.  Right-click your project in **Solution Explorer** and select **Properties**. Click the **Project Settings** tab on the left to access the **Project Settings** property page.  
diff --git a/docs/ssdt/how-to-clone-an-existing-database.md b/docs/ssdt/how-to-clone-an-existing-database.md
@@ -15,9 +15,6 @@ This task uses some of the steps you learned in previous procedures to create a
   
 By using these steps, you can easily create a development or test database from a production database with identical schema and data. You can then continue to develop the test database in a connected mode, or create a database project for offline development and testing, all without disrupting the operation of the production database.  
   
-> [!WARNING]  
-> The following procedures uses entities created in previous procedures in the [Connected Database Development](../ssdt/connected-database-development.md) section.  
-  
 ### To create a development database  
   
 1.  In **SQL Server Object Explorer**, under the **SQL Server** node, expand your connected server instance.  
diff --git a/docs/ssdt/how-to-create-a-new-database-project.md b/docs/ssdt/how-to-create-a-new-database-project.md
@@ -20,9 +20,6 @@ You can create a new database project and import database schema from an existin
   
 The following two procedures essentially achieve the same goal by creating a new database project and importing schema from an existing database. Each database object will be represented as a SQL script file (.sql) in **Solution Explorer**. For more information on importing database schema from a snapshot, see [How to: Create a Snapshot of a Project](../ssdt/how-to-create-a-snapshot-of-a-project.md).  
   
-> [!WARNING]  
-> The following procedures utilize entities created in previous procedures in the [Connected Database Development](../ssdt/connected-database-development.md) section.  
-  
 ### To create a new database project off a connected database  
   
 1.  Right-click the **TradeDev** node in **SQL Server Object Explorer** and select **Create New Project**.  
@@ -35,7 +32,7 @@ The following two procedures essentially achieve the same goal by creating a new
   
 5.  Examine the hierarchy in the **Solution Explorer**. Expand the **dbo** folder and you will find separate **Functions**, **Tables** and **Views** folders. Notice that the tables and function are grouped under their schema folders.  
   
-6.  Double-click **Products.sql** under **Tables**. The **Table Designer** opens, showing the visual interpretation of the table in the Columns Grid, and the script definition of the table in the Script Pane. This is identical to what we see in the [Connected Database Development](../ssdt/connected-database-development.md) section.  
+6.  Double-click **Products.sql** under **Tables**. The **Table Designer** opens, showing the visual interpretation of the table in the Columns Grid, and the script definition of the table in the Script Pane. This is identical to what we see in the [Manage Tables, Relationships, and Fix Errors](../ssdt/manage-tables-relationships-and-fix-errors.md)section.  
   
 7.  Uncheck the **Allow Nulls** box for the **CustomerId** column. Press CTRL + S to save the file.  
   
@@ -59,7 +56,7 @@ The following two procedures essentially achieve the same goal by creating a new
   
 6.  Examine the hierarchy in the **Solution Explorer**. Expand the **dbo** folder and you will find separate **Functions**, **Tables** and **Views** folders. Notice that the tables and function are grouped under their schema folders.  
   
-7.  Double-click **Products.sql** under **Tables**. The **Table Designer** opens, showing the visual interpretation of the table in the Columns Grid, and the script definition of the table in the Script Pane. This is identical to what we see in the [Connected Database Development](../ssdt/connected-database-development.md) section.  
+7.  Double-click **Products.sql** under **Tables**. The **Table Designer** opens, showing the visual interpretation of the table in the Columns Grid, and the script definition of the table in the Script Pane. This is identical to what we see in the [Manage Tables, Relationships, and Fix Errors](../ssdt/manage-tables-relationships-and-fix-errors.md)section.  
   
 8.  Uncheck the **Allow Nulls** box for the **CustomerId** column. Press CTRL + S to save the file.  
   
diff --git a/docs/ssdt/how-to-create-a-snapshot-of-a-project.md b/docs/ssdt/how-to-create-a-snapshot-of-a-project.md
@@ -18,44 +18,41 @@ A **Data-tier Application** file provides you with a read-only representation of
   
 In the event of a user error on a source database project, you can revert the source project to the state it was in when the snapshot was created. You can also establish snapshots at various stages of your development for baseline purpose.  
   
-> [!WARNING]  
-> The following procedures utilize entities created in previous procedures in the [Connected Database Development](../ssdt/connected-database-development.md) and [Project-Oriented Offline Database Development](../ssdt/project-oriented-offline-database-development.md) sections.  
+## To create a snapshot
   
-### To create a snapshot  
+1. Right-click the **TradeDev** project in **Solution Explorer**, and select **Data-tier Application (\*.dacpac)...**.  
   
-1.  Right-click the **TradeDev** project in **Solution Explorer**, and select **Data-tier Application (\*.dacpac)...**.  
+2. SSDT will attempt to build the project first. If there is no build error, a **Snapshot** folder is created in **Solution Explorer**. Inside this folder, SSDT creates a .dacpac file using the name format of "\<Project Name\>_YYYYMMDD_HH-MM-SS.dacpac".  
   
-2.  SSDT will attempt to build the project first. If there is no build error, a **Snapshot** folder is created in **Solution Explorer**. Inside this folder, SSDT creates a .dacpac file using the name format of "\<Project Name\>_YYYYMMDD_HH-MM-SS.dacpac".  
+3. Right-click the .dacpac file and select **Rename**. Change the default file name to "TradeDev1.dacpac".  
   
-3.  Right-click the .dacpac file and select **Rename**. Change the default file name to "TradeDev1.dacpac".  
+4. Right-click the **GetProductsBySupplier** function in **Solution Explorer** and select **Delete** to remove it from the project.  
   
-4.  Right-click the **GetProductsBySupplier** function in **Solution Explorer** and select **Delete** to remove it from the project.  
-  
-5.  Follow the previous steps to create a new snapshot called **TradeDev2.dacpac**.  
+5. Follow the previous steps to create a new snapshot called **TradeDev2.dacpac**.  
   
 ### To import a snapshot  
   
-1.  Right-click the **TradeDev** project in **Solution Explorer**, select **Import**, then **Data-tier Application (\*.dacpac)...** from the contextual menus.  
+1. Right-click the **TradeDev** project in **Solution Explorer**, select **Import**, then **Data-tier Application (\*.dacpac)...** from the contextual menus.  
   
-2.  In the **Import Data-tier Application** dialog box, click **Browse** to select **TradeDev1.dacpac** to be used as the source of the import.  
+2. In the **Import Data-tier Application** dialog box, click **Browse** to select **TradeDev1.dacpac** to be used as the source of the import.  
   
     Notice that the **Target project** section has been disabled, since the current project is the default target. Click **Start** to start the import.  
   
-3.  Click **Finish** in the **Summary** page. In **Solution Explorer**, notice that the deleted table has been restored to the project.  
+3. Click **Finish** in the **Summary** page. In **Solution Explorer**, notice that the deleted table has been restored to the project.  
   
     > [!WARNING]  
     > The import snapshot will import all database entities in the snapshot schema to the project. This might create duplicate entities as a result. For example, each of the tables and view now contains an additional copy of itself named <ObjectName_1>. Right-click each of these duplicate objects in **Solution Explorer** and select **Delete** to remove it from the project.  
   
 ### To compare snapshots  
   
-1.  Right-click **TradeDev1.dacpac** in Solution Explorer and select **Schema Compare**. The **Schema Compare** window opens.  
+1. Right-click **TradeDev1.dacpac** in Solution Explorer and select **Schema Compare**. The **Schema Compare** window opens.  
   
-2.  Use the **Data-tier Application File** options to set the source and target schemas. Make sure that the **Source Schema** is set to **TradeDev1.dacpac** in **Data-tier Application File**, and the **Target Schema** is set to **TradeDev2.dacpac**.  
+2. Use the **Data-tier Application File** options to set the source and target schemas. Make sure that the **Source Schema** is set to **TradeDev1.dacpac** in **Data-tier Application File**, and the **Target Schema** is set to **TradeDev2.dacpac**.  
   
-3.  Click **OK** to start the compare. Notice that the deleted function is being highlighted as a difference between the old and new snapshot.  
+3. Click **OK** to start the compare. Notice that the deleted function is being highlighted as a difference between the old and new snapshot.  
   
     You can easily find the delta of different snapshots by using Schema Compare. In this case, you can find out how your project evolves during the development process.  
   
-## See Also  
+## See Also
+
 [How to: Use Schema Compare to Compare Different Database Definitions](../ssdt/how-to-use-schema-compare-to-compare-different-database-definitions.md)  
-  
diff --git a/docs/ssdt/how-to-create-new-database-objects-using-queries.md b/docs/ssdt/how-to-create-new-database-objects-using-queries.md
@@ -15,9 +15,6 @@ If you prefer to use scripts to create or edit views, stored procedures, functio
   
 The Transact-SQL Editor is invoked when you use the **View Code** contextual menu to open a database entity in a connected database or a project. It is also automatically opened when you use the **New Query** contextual menu from the SQL Server Object Explorer, or add a new script object to a database project. If you are not connected to a database but want to execute a query against it, you can also use the **New Query Connection** dialog box by selecting **Transact-SQL Editor** menu from the **SQL** menu to connect to a database and launch the Transact-SQL Editor.  
   
-> [!WARNING]  
-> The following procedures use entities created in previous procedures in the [Connected Database Development](../ssdt/connected-database-development.md) section.  
-  
 ### To create a new table using a Transact-SQL query  
   
 1.  Right-click the **Trade** database node and select **New Query**.  
diff --git a/docs/ssdt/how-to-debug-stored-procedures.md b/docs/ssdt/how-to-debug-stored-procedures.md
@@ -17,9 +17,6 @@ The Transact-SQL debugger allows you to interactively debug stored procedures by
   
 This example shows how to create and debug a Transact-SQL stored procedure by stepping into it.  
   
-> [!WARNING]  
-> The following procedure uses entities created in procedures in the [Connected Database Development](../ssdt/connected-database-development.md) and [Project-Oriented Offline Database Development](../ssdt/project-oriented-offline-database-development.md) sections.  
-
 > [!NOTE]
 > Transact-SQL debugging isn't available for Azure SQL Database or Azure SQL Managed Instance.
   
diff --git a/docs/ssdt/how-to-delete-objects-and-resolve-dependencies.md b/docs/ssdt/how-to-delete-objects-and-resolve-dependencies.md
@@ -17,9 +17,6 @@ f1_keywords:
 
 When you rename or delete an object in **SQL Server Object Explorer**, SQL Server Data Tools automatically detects all its dependency objects, and will prepare an ALTER script to rename or drop the dependency as needed.  
   
-> [!WARNING]  
-> The following procedures uses entities created in previous procedures in the [Connected Database Development](../ssdt/connected-database-development.md) section.  
-  
 ### To delete a database  
   
 1.  Right-click a database in **SQL Server Object Explorer**, and select **Delete**.  
diff --git a/docs/ssdt/how-to-edit-an-existing-table-using-queries.md b/docs/ssdt/how-to-edit-an-existing-table-using-queries.md
@@ -13,10 +13,7 @@ ms.topic: conceptual
 
 You can edit the definition of a table or its data by writing a Transact-SQL query. To view or enter data in a table visually, use the Data Editor as described in [Connected Database Development](../ssdt/connected-database-development.md).  
   
-> [!WARNING]  
-> The following procedures use entities created in previous procedures in the [Connected Database Development](../ssdt/connected-database-development.md) section.  
-  
-### To edit the definition of an existing table  
+## To edit the definition of an existing table
   
 1.  Expand the **Tables** node of the **Trade** database in **SQL Server Object Explorer**, and right-click **dbo.Suppliers**.  
   
diff --git a/docs/ssdt/how-to-execute-a-partial-query.md b/docs/ssdt/how-to-execute-a-partial-query.md
@@ -13,9 +13,6 @@ ms.topic: conceptual
 
 The Transact-SQL Editor allows you to highlight a specific segment of the script and execute it as a single query. This makes it easy for you to debug sections of complex queries.  
   
-> [!WARNING]  
-> The following procedure uses entities created in previous procedures in the [Connected Database Development](../ssdt/connected-database-development.md) and [Project-Oriented Offline Database Development](../ssdt/project-oriented-offline-database-development.md) sections.  
-  
 ## To partially execute a query  
   
 1. In **SQL Server Object Explorer**, double-click **PerishableFruits** under **Views** to open it in Transact-SQL editor.  
diff --git a/docs/ssdt/how-to-fix-errors.md b/docs/ssdt/how-to-fix-errors.md
@@ -13,10 +13,7 @@ ms.topic: conceptual
 
 The Error List pane displays any deployment or build errors. Syntax and semantic errors caused by editing in either the Transact-SQL Editor or Table Designer also shows up in the list when you are editing database entities and its definitions. The Error List is dynamically updated as you edit scripts across different tabs. You can then follow the errors identified for further troubleshooting.  
   
-> [!WARNING]  
-> The following procedures use entities created in procedures in the [Connected Database Development](../ssdt/connected-database-development.md) and [Project-Oriented Offline Database Development](../ssdt/project-oriented-offline-database-development.md) sections.  
-  
-### To fix errors  
+## To fix errors
   
 1.  Right-click the **Product** table (Product.sql) in **Solution Explorer** and select **View Designer**.  
   
@@ -36,6 +33,7 @@ The Error List pane displays any deployment or build errors. Syntax and semantic
   
 7.  Notice that the warning and error disappear from the **Error List** immediately after you fix the problems.  
   
-## See Also  
+## See Also
+
 [Use Transact-SQL Editor to Edit and Execute Scripts](../ssdt/use-transact-sql-editor-to-edit-and-execute-scripts.md)  
   
diff --git a/docs/ssdt/how-to-navigate-between-scripts.md b/docs/ssdt/how-to-navigate-between-scripts.md
@@ -16,7 +16,7 @@ f1_keywords:
 The Transact-SQL Editor for offline development provides two useful navigation tools that are familiar to Visual Studio users: Go To Definition and Find All References. For example, you can right-click a table name and use "Find All References" to list all references to the table in the project. You can double-click a search result to go to the specific code file. In this file, you can right-click the table name again, and choose "Go to Definition" to go back to the table definition.  
   
 > [!WARNING]  
-> The following procedure uses entities created in previous procedures in the [Connected Database Development](../ssdt/connected-database-development.md) and [Project-Oriented Offline Database Development](../ssdt/project-oriented-offline-database-development.md) sections.  
+> The following procedure uses entities created in previous procedures in the [Project-Oriented Offline Database Development](../ssdt/project-oriented-offline-database-development.md) sections.  
   
 ### To navigate between scripts  
   
diff --git a/docs/ssdt/how-to-outline-and-add-snippets-to-transact-sql-script.md b/docs/ssdt/how-to-outline-and-add-snippets-to-transact-sql-script.md
@@ -18,7 +18,7 @@ When you need to browse for an appropriate snippet, you can use the snippet pick
 By default, all text is displayed in the Transact-SQL Editor, but you can choose to hide some code from view. The Transact-SQL Editor allows you to select a region of code and make it collapsible, so that it appears under a plus sign (+).You can then expand or hide the region by clicking the plus sign (+) next to the symbol. Outlined code is not deleted; it is just hidden from view.  
   
 > [!WARNING]  
-> The following procedures utilize entities created in previous procedures in the [Connected Database Development](../ssdt/connected-database-development.md) and [Project-Oriented Offline Database Development](../ssdt/project-oriented-offline-database-development.md) sections.  
+> The following procedure uses entities created in previous procedures in the [Project-Oriented Offline Database Development](../ssdt/project-oriented-offline-database-development.md) sections.
   
 ### To insert snippets  
   
diff --git a/docs/ssdt/how-to-update-a-connected-database-with-power-buffer.md b/docs/ssdt/how-to-update-a-connected-database-with-power-buffer.md
@@ -17,9 +17,9 @@ SQL Server Data Tools Power Buffer technology makes it easy for you to apply cha
   
 SSDT is also aware of any changes made to your database schema outside Visual Studio. For example, if you add a new table to an existing database in SQL Server Management Studio, such change will immediately show up in the SQL Server Object Explorer in Visual Studio without manually refreshing it. The drift detection feature ensures that you are always viewing the latest schema definition of a database in SQL Server Object Explorer. Notice that any database objects opened in Table Designer or Transact-SQL Editor for editing will not be refreshed to show changes outside Visual Studio.  
   
-The following procedures utilize entities created in previous procedures in the [Connected Database Development](../ssdt/connected-database-development.md) section.  
+The following procedures utilize entities created in previous procedures in the [Manage Tables, Relationships, and Fix Errors](../ssdt/manage-tables-relationships-and-fix-errors.md)section.  
   
-### To apply the changes made in the previous procedures  
+## To apply the changes made in the previous procedures
   
 1.  Click the green **Update** button on the toolbar ("Update Database" tooltip is displayed if you hover over the button). The toolbar is above the Columns Grid of the Table Designer.  
   
diff --git a/docs/ssdt/how-to-use-microsoft-sql-server-2012-objects-in-your-project.md b/docs/ssdt/how-to-use-microsoft-sql-server-2012-objects-in-your-project.md
diff --git a/docs/ssdt/how-to-use-rename-and-refactoring-to-make-changes-to-your-database-objects.md b/docs/ssdt/how-to-use-rename-and-refactoring-to-make-changes-to-your-database-objects.md
diff --git a/docs/ssdt/how-to-use-schema-compare-to-compare-different-database-definitions.md b/docs/ssdt/how-to-use-schema-compare-to-compare-different-database-definitions.md
diff --git a/docs/ssdt/how-to-use-the-table-designer-to-manage-tables-and-relationships.md b/docs/ssdt/how-to-use-the-table-designer-to-manage-tables-and-relationships.md
diff --git a/docs/ssdt/how-to-view-and-edit-data-in-a-table.md b/docs/ssdt/how-to-view-and-edit-data-in-a-table.md
diff --git a/docs/ssdt/how-to-work-with-clr-database-objects.md b/docs/ssdt/how-to-work-with-clr-database-objects.md
diff --git a/docs/ssdt/sql-server-data-tools.md b/docs/ssdt/sql-server-data-tools.md
