Skip to content

Commit 67de488

Browse files
authored
Merge branch 'master' into sqlnew
2 parents 1590c71 + 3e2c567 commit 67de488

7 files changed

Lines changed: 261 additions & 296 deletions

File tree

docs/breadcrumb/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -567,7 +567,7 @@
567567
homepage: /sql/relational-databases/graphs/sql-graph-overview
568568
- name: Import and export
569569
href: /sql/relational-databases/import-export/
570-
homepage: /sql/relational-databases/import-export/bulk-import-and-export-of-data-sql-server
570+
homepage: /sql/relational-databases/import-export/overview-import-export
571571
- name: In-memory OLTP
572572
href: /sql/relational-databases/in-memory-oltp/
573573
homepage: /sql/relational-databases/in-memory-oltp/in-memory-oltp-in-memory-optimization

docs/integration-services/data-flow/cdc-flow-components.md

Lines changed: 23 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -37,41 +37,33 @@ manager: "jhubbard"
3737
## Installation
3838
This section describes the installation procedures for the CDC Components for Microsoft [!INCLUDE[ssISCurrent](../../includes/ssiscurrent-md.md)].
3939

40-
The CDC Components for SSIS are packaged with the Microsoft® Change Data Capture Designer and Service for Oracle by Attunity for Microsoft SQL Server® 2016. This download is part of the SQL Server 2016 Feature Pack. Download components of the Feature Pack from the [SQL Server 2016 Feature Pack web page](http://go.microsoft.com/fwlink/?LinkId=746297).
40+
The CDC Components for SSIS are packaged with the Microsoft® Change Data Capture Designer and Service for Oracle by Attunity for Microsoft SQL Server®. This download is part of the SQL Server Feature Pack. Download components of the Feature Pack from the [SQL Server 2016 Feature Pack web page](http://go.microsoft.com/fwlink/?LinkId=746297).
4141

42-
### Version Support
43-
The following Microsoft [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] products are supported by the CDC components for SSIS:
42+
### Version Support
43+
44+
#### SQL Server version support
45+
46+
The CDC components for SSIS are supported on all the supported versions of Microsoft SQL Server. Currently, the supported versions of SQL Server include SQL Server 2012 through SQL Server 2017.
47+
48+
#### Operating system version support
4449

45-
- Microsoft [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]
46-
47-
- Microsoft [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] for Visual Studio 2015
48-
49-
These versions are supported on the following operating systems and platforms:
50-
51-
- Windows Vista with Service Pack 2
52-
53-
- Windows 7
50+
The CDC components for SSIS are supported on the following operating systems and platforms:
5451

52+
- Windows 8 and 8.1
5553
- Windows 10
56-
57-
- Windows Server 2008 with Service Pack 2
58-
59-
- Windows Server 2008 R2
60-
61-
- Windows Server 2012
54+
- Windows Server 2012 and 2012 R2
55+
- Windows Server 2016
6256

6357
### Running the Installation Program
6458
Before you run the installation wizard, be sure that the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)][!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] is closed. Then follow the directions in the installation wizard.
6559

66-
### Restart SSIS
67-
After you install the CDC components, you must restart the SSIS service to be sure that that the components work correctly when developing packages in the SQL [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)].
60+
### Restart SSIS Service
61+
After you install the CDC components, you must restart the SSIS service to be sure that the components work correctly when developing packages in the SQL [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)].
6862

69-
A message is displayed after you install the components. Click **Yes** when prompted.
63+
A message is displayed after you install the components. Click **Yes** when prompted.
7064

7165
### Uninstalling the Microsoft CDC Components
72-
You uninstall the CDC source, CDC splitter, or CDC Control task, by using the uninstall wizard. Before you uninstall the components you must make sure of the following:
73-
74-
If you are using the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)][!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] for package development, make sure the [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] is closed before running the uninstall wizard.
66+
You uninstall the CDC source, CDC splitter, or CDC Control task, by using the uninstall wizard. If you are using the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)][!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] for package development, make sure the [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] is closed before running the uninstall wizard.
7567

7668
## Benefits
7769
The CDC Components for [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)][!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] components allow SSIS developers to easily build SSIS packages that process change data. These components enhance the ability of SSIS developers to deal with CDC and reduce the complexity of CDC packages.
@@ -81,7 +73,7 @@ manager: "jhubbard"
8173
The SSIS CDC components are designed to work with the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC feature with change tables that are in the same [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] database.
8274

8375
## Getting Started with the Change Data Capture Components
84-
A typical CDC package processes changes to a group of tables. The basic control flow part of this type of CDC package is shown in the figure below. This package is called a trickle-feed processing package.
76+
A typical CDC package processes changes to a group of tables. The basic control flow part of this type of CDC package is shown in the following figure. This package is called a trickle-feed processing package.
8577

8678
![Trickle Feed Processing Package Control Flow](../../integration-services/data-flow/media/tricklefeedprocessing.gif "Trickle Feed Processing Package Control Flow")
8779

@@ -95,9 +87,9 @@ manager: "jhubbard"
9587

9688
The steps illustrated in this figure are:
9789

98-
- **Changes for Table X** is a CDC source that reads changes made to table X that where made in the CDC processing range determined in the parent control flow.
90+
- **Changes for Table X** is a CDC source that reads changes made to table X that were made in the CDC processing range determined in the parent control flow.
9991

100-
- **CDC Splitter X** is used to split the changes into inserts, deletes and updates. In this scenario it is assumed that the CDC Source is configured to produce Net changes so that different change types can be processed in parallel.
92+
- **CDC Splitter X** is used to split the changes into inserts, deletes, and updates. In this scenario, it is assumed that the CDC Source is configured to produce Net changes so that different change types can be processed in parallel.
10193

10294
- The specific changes are then further processed downstream. In this illustration, the changes are inserted into tables using multiple ODBC Destinations but in actual cases the processing may be different.
10395

@@ -137,7 +129,7 @@ manager: "jhubbard"
137129

138130
Passing the state of the CDC processing from the initial load package to the trickle feed package and between different tasks within each package occurs by means of a special SSIS package string variable. The value of this variable is referred to as the CDC State, which reflects the current state of CDC processing for the groups of tables being handled by the initial load and trickle-feed packages.
139131

140-
The value of the CDC State variable needs to be maintained in a persistent storage, it should be read before starting CDC processing and should be saved with the current state after processing completed. The task of loading and storing of the CDC state can be handled by the SSIS developer but the CDC Control component can automate this task by maintaining the CDC State value in a database table.
132+
The value of the CDC State variable needs to be maintained in persistent storage. It should be read before starting CDC processing and should be saved with the current state after processing completed. The task of loading and storing of the CDC state can be handled by the SSIS developer but the CDC Control component can automate this task by maintaining the CDC State value in a database table.
141133

142134
## Security Considerations
143135
This section lists some security considerations related to the use of the CDC components in SSIS.
@@ -146,15 +138,15 @@ manager: "jhubbard"
146138
Trickle-feed update packages need access to [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC functions. Such access is granted, by default, to members of the **db_owner** fixed database role. Because the **db_owner** is a powerful role, when defining capture instances within [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] it is recommended to associate a gating security role to each capture instance that allows the SSIS CDC package to use a much more restricted user for processing the changes.
147139

148140
### Access to CDC Database Current LSN
149-
The CDC Control task operations for marking the start LSN for change processing must be able to find the CDC Database current LSN. This is done using the procedure **sp_replincrementlsn** from the master database. Execute permission on this procedure must be given to the login used for connecting to the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC database.
141+
The CDC Control task operations for marking the start LSN for change processing must be able to find the CDC Database current LSN. The components find the LSN by using the procedure **sp_replincrementlsn** from the master database. Execute permission on this procedure must be given to the login used for connecting to the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC database.
150142

151143
### Access to CDC States Table
152144
The CDC States table is used for automatically persisting CDC States that need to be updatable by the login used for connecting to the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC database. As this table is created by the SSIS developer, set the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] system administrator as a user who is authorized to create [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] databases and perform administrative and maintenance tasks. In addition, a [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] system administrator who works with CDC enabled databases must be knowledgeable about [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] CDC technology and implementation.
153145

154146
## Grouping Tables for CDC Processing
155147
Database projects range in size from several tables to many thousands of tables. When designing initial load and CDC packages, it is beneficial to group tables in much smaller groups for easier management and efficiency. This section lists various considerations that impact the sorting of tables into small groups, where the tables in each are initially loaded and then updated as a group.
156148

157-
The CDC patterns supported by the CDC components assume that this grouping is already determined. Each group defines a separate CDC context that is maintained separately from other groups. For each group, initial-load and a trickle-feed update packages are created. Trickle-feed updates are scheduled for periodic runs based on the rate of change processing constraints (for example, CPU and IO consumption, impact on other systems) and the desired latency.
149+
The CDC patterns supported by the CDC components assume that this grouping is already determined. Each group defines a separate CDC context that is maintained separately from other groups. For each group, initial-load and trickle-feed update packages are created. Trickle-feed updates are scheduled for periodic runs based on the rate of change processing constraints (for example, CPU and IO consumption, impact on other systems) and the desired latency.
158150

159151
Tables are grouped based on the following considerations:
160152

@@ -186,7 +178,7 @@ manager: "jhubbard"
186178
|6-TFREDO (Reprocessing-Trickle-Feed-Updates)|This is the state on a **GetProcessingRange** that occurs after TFSTART. This indicates that the previous run did not complete successfully.<br /><br /> If using the __$reprocessing column, it is set to 1 to indicate that the package may be reprocessing rows already at the target.|
187179
|7-ERROR|The CDC group is in an ERROR state.|
188180

189-
The following is the state diagram for the CDC components. An ERROR state is reached when a state is reached that is not expected. The expected states are illustrated in the diagram below, however the diagram does not show the ERROR state.
181+
Here is the state diagram for the CDC components. An ERROR state is reached when a state is reached that is not expected. The expected states are illustrated in the following diagram. However the diagram does not show the ERROR state.
190182

191183
For example, at the end of an initial load package, when trying to set the state to ILEND, if the state is TFSTART then the CDC group is in an error state and the Trickle-Feed Update package does not run (the Initial Load package does run).
192184

docs/relational-databases/TOC.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@
4545
# [Extended events](../relational-databases/extended-events/extended-events.md)
4646
# [Graphs](../relational-databases/graphs/sql-graph-overview.md)
4747
# [Hierarchical Data](hierarchical-data-sql-server.md)
48-
# [Import and export](../relational-databases/import-export/bulk-import-and-export-of-data-sql-server.md)
48+
# [Import and export](../relational-databases/import-export/overview-import-export.md)
4949
# [In-memory OLTP](../relational-databases/in-memory-oltp/in-memory-oltp-in-memory-optimization.md)
5050
# [Indexes](../relational-databases/indexes/indexes.md)
5151
# [JSON](../relational-databases/json/json-data-sql-server.md)

docs/sql-server/what-s-new-in-sql-server-2017.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,11 +111,12 @@ SQL Server developers now have access to the extensive Python ML and AI librarie
111111
- **Package management** - T-SQL now supports the CREATE EXTERNAL LIBRARY statement, to give DBAs greater management over R packages. Use roles to control prviate or shared package access, store R packages in the database and share them among users.
112112
- **Performance improvements** - The stored procedure `sp_execute_external_script` has been optimized to support batch mode execution for columnstore data.
113113

114+
114115
For more information, see [What's new in SQL Server Machine Learning Services](~/advanced-analytics/what-s-new-in-sql-server-machine-learning-services.md).
115116

116117
## Next steps
117118
- See the [SQL Server 2017 Release Notes](sql-server-2017-release-notes.md).
118119
- Find out [What's new for SQL Server 2017 on Linux](https://docs.microsoft.com/sql/linux/sql-server-linux-whats-new).
119120
- Find out [What's new in SQL Server 2016](what-s-new-in-sql-server-2016.md).
120121

121-
[!INCLUDE[get-help-options](../includes/paragraph-content/get-help-options.md)]
122+
[!INCLUDE[get-help-options](../includes/paragraph-content/get-help-options.md)]

docs/t-sql/data-types/data-types-transact-sql.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Data types (Transact-SQL) | Microsoft Docs"
33
ms.custom: ""
4-
ms.date: "07/23/2017"
4+
ms.date: "09/13/2017"
55
ms.prod: "sql-non-specified"
66
ms.reviewer: ""
77
ms.suite: ""
@@ -104,7 +104,8 @@ In [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], based on their sto
104104
|[cursor](../../t-sql/data-types/cursor-transact-sql.md)|[timestamp](../../t-sql/data-types/rowversion-transact-sql.md)|
105105
|[hierarchyid](../../t-sql/data-types/hierarchyid-data-type-method-reference.md)|[uniqueidentifier](../../t-sql/data-types/uniqueidentifier-transact-sql.md)|
106106
|[sql_variant](../../t-sql/data-types/sql-variant-transact-sql.md)|[xml](../../t-sql/xml/xml-transact-sql.md)|
107-
|[table](../../t-sql/data-types/table-transact-sql.md)|[Spatial Types](http://msdn.microsoft.com/library/d1715574-34b1-4ce5-a29f-25e35027a54c)|
107+
|[Spatial Geometry Types](../../t-sql/spatial-geometry/spatial-types-geometry-transact-sql.md) |[Spatial Geography Types](../../t-sql/spatial-geography/spatial-types-geography.md)|
108+
|[table](../../t-sql/data-types/table-transact-sql.md) | |
108109

109110
## See also
110111
[CREATE PROCEDURE &#40;Transact-SQL&#41;](../../t-sql/statements/create-procedure-transact-sql.md)

0 commit comments

Comments
 (0)