Skip to content

Commit 32cf9c0

Browse files
committed
REst of ssdt files to shorten titles
1 parent 7021cb0 commit 32cf9c0

31 files changed

Lines changed: 144 additions & 119 deletions

File tree

docs/ssdt/connected-database-development.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.author: maghan
99
manager: jroth
1010
ms.reviewer: “”
1111
ms.custom: seo-lt-2019
12-
ms.date: "02/09/2017"
12+
ms.date: 02/09/2017
1313
---
1414

1515
# Connected Database Development

docs/ssdt/dac-framework-compatibility.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.author: maghan
99
manager: jroth
1010
ms.reviewer: “”
1111
ms.custom: seo-lt-2019
12-
ms.date: "02/09/2017"
12+
ms.date: 02/09/2017
1313
---
1414

1515
# DAC Framework Compatibility

docs/ssdt/interpreting-sql-server-unit-test-results.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,5 @@
11
---
2-
title: "Interpreting SQL Server Unit Test Results"
3-
ms.custom: seo-lt-2019
4-
5-
ms.date: "02/09/2017"
2+
title: Interpreting SQL Server Unit Test Results
63
ms.prod: sql
74
ms.technology: ssdt
85
ms.topic: conceptual
@@ -11,8 +8,12 @@ author: markingmyname
118
ms.author: maghan
129
manager: jroth
1310
ms.reviewer: “”
11+
ms.custom: seo-lt-2019
12+
ms.date: 02/09/2017
1413
---
14+
1515
# Interpreting SQL Server Unit Test Results
16+
1617
When you run a SQL Server unit test, test results are automatically produced, saved to disk, and summarized in the **Test Results** window. As soon as you start a test run, the **Test Results** window appears and displays the progress of the test run. This display includes tests that are running and tests that have completed.
1718

1819
To see detailed information about a test result, double-click it in the **Test Results** window to display the **Test Results Details** page. For more information about a test result, double-click it.

docs/ssdt/keyboard-shortcuts-for-sql-server-unit-test-designer.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,5 @@
11
---
2-
title: "Keyboard Shortcuts for SQL Server Unit Test Designer"
3-
ms.custom: seo-lt-2019
4-
5-
ms.date: "02/09/2017"
2+
title: Keyboard Shortcuts for SQL Server Unit Test Designer
63
ms.prod: sql
74
ms.technology: ssdt
85
ms.topic: conceptual
@@ -11,8 +8,12 @@ author: markingmyname
118
ms.author: maghan
129
manager: jroth
1310
ms.reviewer: “”
11+
ms.custom: seo-lt-2019
12+
ms.date: 02/09/2017
1413
---
14+
1515
# Keyboard Shortcuts for SQL Server Unit Test Designer
16+
1617
You can use the following keyboard shortcuts to navigate within the SQL Server Unit Test Designer.
1718

1819
|||
Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,5 @@
11
---
2-
title: "Manage Tables, Relationships, and Fix Errors"
3-
ms.custom: seo-lt-2019
4-
5-
ms.date: "02/09/2017"
2+
title: Manage Tables, Relationships, and Fix Errors
63
ms.prod: sql
74
ms.technology: ssdt
85
ms.topic: conceptual
@@ -11,14 +8,17 @@ author: markingmyname
118
ms.author: maghan
129
manager: jroth
1310
ms.reviewer: “”
11+
ms.custom: seo-lt-2019
12+
ms.date: 02/09/2017
1413
---
14+
1515
# Manage Tables, Relationships, and Fix Errors
16-
Topics in this section describe how to use the Table Designer to design tables and manage table relationships. Additional topics describe how to fix common syntax or semantic errors.
17-
18-
## In This Section
19-
16+
17+
Topics in this section describe how to use the Table Designer to design tables and manage table relationships. Additional topics describe how to fix common syntax or semantic errors.
18+
19+
## In This Section
20+
2021
|Topic|Description|
2122
|---------|---------------|
2223
Use the Table Designer to Manage Tables and Relationships](../ssdt/how-to-use-the-table-designer-to-manage-tables-and-relationships.md)|Use the new Table Designer to design tables and manage table relationships.|
23-
Fix Errors](../ssdt/how-to-fix-errors.md)|Follow any syntax or semantic errors that show up in the Error List pane to fix errors.|
24-
24+
Fix Errors](../ssdt/how-to-fix-errors.md)|Follow any syntax or semantic errors that show up in the Error List pane to fix errors.|

docs/ssdt/overview-of-connection-strings-and-permissions.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,5 @@
11
---
2-
title: "Overview of Connection Strings and Permissions"
3-
ms.custom: seo-lt-2019
4-
5-
ms.date: "02/09/2017"
2+
title: Connection Strings and Permissions
63
ms.prod: sql
74
ms.technology: ssdt
85
ms.topic: conceptual
@@ -11,8 +8,12 @@ author: markingmyname
118
ms.author: maghan
129
manager: jroth
1310
ms.reviewer: “”
11+
ms.custom: seo-lt-2019
12+
ms.date: 02/09/2017
1413
---
14+
1515
# Overview of Connection Strings and Permissions
16+
1617
To run SQL Server unit tests, you must connect to a database server by using one or two specific connection strings. Each connection string represents an account that has the specific permissions that you must have to perform the task or set of tasks in a particular script as part of the test. You can specify these strings in the **SQL Server Test Configuration** dialog box or by manually editing the app.config file for your test project.
1718

1819
## Connection Strings

docs/ssdt/overview-of-extensibility-for-database-code-analysis-rules.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,5 @@
11
---
2-
title: "Overview of Extensibility for Database Code Analysis Rules"
3-
ms.custom: seo-lt-2019
4-
5-
ms.date: "02/09/2017"
2+
title: Extensibility for Database Code Analysis Rules
63
ms.prod: sql
74
ms.technology: ssdt
85
ms.topic: conceptual
@@ -11,8 +8,12 @@ author: markingmyname
118
ms.author: maghan
129
manager: jroth
1310
ms.reviewer: “”
11+
ms.custom: seo-lt-2019
12+
ms.date: 02/09/2017
1413
---
14+
1515
# Overview of Extensibility for Database Code Analysis Rules
16+
1617
Visual Studio editions containing SQL Server Data Tools include code analysis rules to report on Transact\-SQL design, naming, and performance warnings in your database code. For more information, see [Analyzing Database Code to Improve Code Quality](https://msdn.microsoft.com/library/dd172133(v=vs.100).aspx).
1718

1819
If the built-in code analysis rules do not include coverage for a specific Transact\-SQL issue that you want included you can create custom database code analysis rules. For example, you might want to create a custom rule that avoids using the WAITFOR DELAY statement, as demonstrated in [Walkthrough Authoring a Custom Static Code Analysis Rule Assembly for SQL Server](../ssdt/walkthrough-author-custom-static-code-analysis-rule-assembly.md). To create custom database code analysis rules, you use the classes in the [CodeAnalysis](https://msdn.microsoft.com/library/microsoft.sqlserver.dac.codeanalysis.aspx) namespace.

docs/ssdt/previous-releases-of-sql-server-data-tools-ssdt-and-ssdt-bi.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
---
2-
title: "Previous releases of SQL Server Data Tools (SSDT and SSDT-BI)"
3-
ms.custom: seo-lt-2019""
4-
ms.date: "09/05/2018"
2+
title: Previous releases of SSDT
53
ms.prod: sql
64
ms.prod_service: "sql-tools"
75
ms.reviewer: ""
@@ -12,9 +10,13 @@ author: markingmyname
1210
ms.author: maghan
1311
manager: jroth
1412
ms.reviewer: “”
13+
ms.custom: seo-lt-2019
14+
ms.date: 09/05/2018
1515
monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||=azuresqldb-mi-current"
1616
---
17+
1718
# Previous releases of SQL Server Data Tools (SSDT and SSDT-BI)
19+
1820
[!INCLUDE[appliesto-ss-asdb-asdw-pdw-md](../includes/appliesto-ss-asdb-asdw-pdw-md.md)]
1921
SQL Server Data Tools (SSDT) provides project templates and design surfaces for building SQL Server content types - relational databases, Analysis Services models, Reporting Services reports, and Integration Services packages.
2022

docs/ssdt/project-oriented-database-development-using-command-line-tools.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,5 @@
11
---
2-
title: "Project-Oriented Database Development using Command-Line Tools"
3-
ms.custom: seo-lt-2019
4-
5-
ms.date: "04/26/2017"
2+
title: Project-Oriented Database Development using Command-Line Tools
63
ms.prod: sql
74
ms.technology: ssdt
85
ms.topic: conceptual
@@ -11,8 +8,12 @@ author: markingmyname
118
ms.author: maghan
129
manager: jroth
1310
ms.reviewer: “”
11+
ms.custom: seo-lt-2019
12+
ms.date: 04/26/2017
1413
---
14+
1515
# Project-Oriented Database Development using Command-Line Tools
16+
1617
SQL Server Data Tools proves command-line tools that enable a number of project-oriented database development scenarios.
1718

1819
## In This Section

docs/ssdt/project-oriented-offline-database-development.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,5 @@
11
---
2-
title: "Project-Oriented Offline Database Development"
3-
ms.custom: seo-lt-2019
4-
5-
ms.date: "02/09/2017"
2+
title: Project-Oriented Offline Database Development
63
ms.prod: sql
74
ms.technology: ssdt
85
ms.topic: conceptual
@@ -14,8 +11,12 @@ author: markingmyname
1411
ms.author: maghan
1512
manager: jroth
1613
ms.reviewer: “”
14+
ms.custom: seo-lt-2019
15+
ms.date: 02/09/2017
1716
---
17+
1818
# Project-Oriented Offline Database Development
19+
1920
This section describes features provided by SQL Server Data Tools (SSDT) for authoring, building, debugging and publishing a database project.
2021

2122
Using SSDT, you can create an offline database project and implement schema changes by adding, modifying or deleting the definitions of objects (represented by scripts) in the project, without a connection to a server instance. These can all be accomplished by using the table designer, or the Transact\-SQL Editor. You can also write and debug Transact\-SQL and CLR objects in the same project. You can use Schema Compare to ensure that your project stays in sync with the production database, and create snapshots for your project in each stage of the development cycle for comparison purposes. While you are working on your database projects in a team-based environment, you can employ version control for all the files. After your database project has been developed, tested and debugged, you can hand off your project to authorized personnel to be published to a production environment.

0 commit comments

Comments
 (0)