You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/2014/database-engine/deprecated-database-engine-features-in-sql-server-2016.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ manager: craigg
34
34
|Database objects|Ability to return result sets from triggers|None|Returning results from trigger|12|
35
35
|Encryption|Encryption using RC4 or RC4_128 is deprecated and is scheduled to be removed in the next version. Decrypting RC4 and RC4_128 is not deprecated.|Use another encryption algorithm such as AES.|Deprecated encryption algorithm|253|
36
36
|Remote servers|sp_addremotelogin<br /><br /> sp_addserver<br /><br /> sp_dropremotelogin<br /><br /> sp_helpremotelogin<br /><br /> sp_remoteoption|Replace remote servers by using linked servers. sp_addserver can only be used with the local option.|sp_addremotelogin<br /><br /> sp_addserver<br /><br /> sp_dropremotelogin<br /><br /> sp_helpremotelogin<br /><br /> sp_remoteoption|70<br /><br /> 69<br /><br /> 71<br /><br /> 72<br /><br /> 73|
37
-
|Remote servers|@@remserver|Replace remote servers by using linked servers.|None|None|
37
+
|Remote servers|\@\@remserver|Replace remote servers by using linked servers.|None|None|
38
38
|Remote servers|SET REMOTE_PROC_TRANSACTIONS|Replace remote servers by using linked servers.|SET REMOTE_PROC_TRANSACTIONS|110|
39
39
|Set options|`SET ROWCOUNT` for `INSERT`, `UPDATE`, and `DELETE` statements|TOP keyword|SET ROWCOUNT|109|
40
40
|Table hints|HOLDLOCK table hint without parenthesis.|Use HOLDLOCK with parenthesis.|HOLDLOCK table hint without parenthesis|167|
@@ -137,7 +137,7 @@ manager: craigg
137
137
|[!INCLUDE[tsql](../includes/tsql-md.md)]|ROWGUIDCOL as a column name in DML statements.|Use $rowguid.|ROWGUIDCOL|182|
138
138
|[!INCLUDE[tsql](../includes/tsql-md.md)]|IDENTITYCOL as a column name in DML statements.|Use $identity.|IDENTITYCOL|183|
139
139
|[!INCLUDE[tsql](../includes/tsql-md.md)]|Use of #, ## as temporary table and temporary stored procedure names.|Use at least one additional character.|'#' and '##' as the name of temporary tables and stored procedures|185|
140
-
|[!INCLUDE[tsql](../includes/tsql-md.md)]|Use of @, @@, or @@ as [!INCLUDE[tsql](../includes/tsql-md.md)] identifiers.|Do not use @ or @@ or names that begin with @@ as identifiers.|'@' and names that start with '@@' as [!INCLUDE[tsql](../includes/tsql-md.md)] identifiers|186.|
140
+
|[!INCLUDE[tsql](../includes/tsql-md.md)]|Use of \@, \@\@, or \@\@ as [!INCLUDE[tsql](../includes/tsql-md.md)] identifiers.|Do not use \@ or \@\@ or names that begin with \@\@ as identifiers.|'\@' and names that start with '\@\@' as [!INCLUDE[tsql](../includes/tsql-md.md)] identifiers|186.|
141
141
|[!INCLUDE[tsql](../includes/tsql-md.md)]|Use of DEFAULT keyword as default value.|Do not use the word DEFAULT as a default value.|DEFAULT keyword as a default value|187|
142
142
|[!INCLUDE[tsql](../includes/tsql-md.md)]|Use of a space as a separator between table hints.|Use a comma to separate table hints.|Multiple table hints without comma|168|
143
143
|[!INCLUDE[tsql](../includes/tsql-md.md)]|The select list of an aggregate indexed view must contain COUNT_BIG (*) in 90 compatibility mode|Use COUNT_BIG (*).|Index view select list without COUNT_BIG(*)|2|
Copy file name to clipboardExpand all lines: docs/2014/integration-services/data-flow/ole-db-source.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ manager: craigg
75
75
76
76
`EXEC uspGetWhereUsedProductID ?, ?`
77
77
78
-
The stored procedure expects the variables, `@StartProductID` and `@CheckDate`, to provide parameter values. The order in which the parameters appear in the **Mappings** list is irrelevant. The only requirement is that the parameter names match the variable names in the stored procedure, including the @ sign.
78
+
The stored procedure expects the variables, `@StartProductID` and `@CheckDate`, to provide parameter values. The order in which the parameters appear in the **Mappings** list is irrelevant. The only requirement is that the parameter names match the variable names in the stored procedure, including the \@ sign.
79
79
80
80
### Mapping Parameters to Variables
81
81
The parameters are mapped to variables that provide the parameter values at run time. The variables are typically user-defined variables, although you can also use the system variables that [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] provides. If you use user-defined variables, make sure that you set the data type to a type that is compatible with the data type of the column that the mapped parameter references. For more information, see [Integration Services (SSIS) Variables](../integration-services-ssis-variables.md).
Copy file name to clipboardExpand all lines: docs/2014/integration-services/execute-sql-task-editor-parameter-mapping-page.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ manager: craigg
39
39
**Parameter Name**
40
40
Provide a parameter name.
41
41
42
-
Depending on the connection manager type that the task uses, you must use numbers or parameter names. Some connection manager types require that the first character of the parameter name is the @ sign , specific names like @Param1, or column names as parameter names.
42
+
Depending on the connection manager type that the task uses, you must use numbers or parameter names. Some connection manager types require that the first character of the parameter name is the \@ sign , specific names like \@Param1, or column names as parameter names.
43
43
44
44
**Related Topics:**[Parameters and Return Codes in the Execute SQL Task](../../2014/integration-services/parameters-and-return-codes-in-the-execute-sql-task.md)
Copy file name to clipboardExpand all lines: docs/2014/integration-services/expressions/identifiers-ssis.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ manager: craigg
35
35
36
36
- The first character of the name must be a letter as defined by the Unicode Standard 2.0, or an underscore (_).
37
37
38
-
- Subsequent characters can be letters or numbers as defined in the Unicode Standard 2.0, the underscore (_), @, $, and # characters.
38
+
- Subsequent characters can be letters or numbers as defined in the Unicode Standard 2.0, the underscore (_), \@, $, and # characters.
39
39
40
40
> [!IMPORTANT]
41
41
> Embedded spaces and special characters, other than the ones listed, are not valid in regular identifiers. In order to use spaces and special characters, you must use a qualified identifier instead of a regular identifier.
@@ -83,15 +83,15 @@ manager: craigg
83
83
> If both elements in dotted notation are enclosed in one pair of brackets, the expression evaluator interprets the pair as a single identifier, not a source-column combination.
84
84
85
85
## Variables in Expressions
86
-
Variables, when referenced in expressions, must include the @ prefix. For example, the **Counter** variable is referenced by using @Counter. The @ character is not part of the variable name; it only identifies the variable to the expression evaluator. If you build expressions by using the dialog boxes that [!INCLUDE[ssIS](../../includes/ssis-md.md)] Designer provides, the @ character is automatically added to the variable name. It is not valid to include spaces between the @ character and the variable name.
86
+
Variables, when referenced in expressions, must include the \@ prefix. For example, the **Counter** variable is referenced by using \@Counter. The \@ character is not part of the variable name; it only identifies the variable to the expression evaluator. If you build expressions by using the dialog boxes that [!INCLUDE[ssIS](../../includes/ssis-md.md)] Designer provides, the \@ character is automatically added to the variable name. It is not valid to include spaces between the \@ character and the variable name.
87
87
88
88
Variable names follow the same rules as those for other regular identifiers:
89
89
90
90
- The first character of the name must be a letter as defined by the Unicode Standard 2.0, or an underscore (_).
91
91
92
-
- Subsequent characters can be letters or numbers as defined in the Unicode Standard 2.0, the underscore (_), @, $, and # characters.
92
+
- Subsequent characters can be letters or numbers as defined in the Unicode Standard 2.0, the underscore (_), \@, $, and # characters.
93
93
94
-
If a variable name contains characters other than those listed, the variable must be enclosed in brackets. For example, variable names with spaces must be enclosed in brackets. The opening bracket follows the @ character. For example, the **My Name** variable is referenced as @[My Name]. It is not valid to include spaces between the variable name and the brackets.
94
+
If a variable name contains characters other than those listed, the variable must be enclosed in brackets. For example, variable names with spaces must be enclosed in brackets. The opening bracket follows the \@ character. For example, the **My Name** variable is referenced as \@[My Name]. It is not valid to include spaces between the variable name and the brackets.
95
95
96
96
> [!NOTE]
97
97
> The names of user-defined and system variables are case-sensitive.
Copy file name to clipboardExpand all lines: docs/2014/integration-services/expressions/integration-services-ssis-expressions.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,9 +41,9 @@ manager: craigg
41
41
42
42
- Variables use an expression to set their value. For example, GETDATE() sets the value of the variable to the current date.
43
43
44
-
- Precedence constraints can use expressions to specify the conditions that determine whether the constrained task or container in a package runs. Expressions used in a precedence constraint must evaluate to `true` or `false`. For example, the expression @A > @B compares two user-defined variables to determine whether the constrained task runs.
44
+
- Precedence constraints can use expressions to specify the conditions that determine whether the constrained task or container in a package runs. Expressions used in a precedence constraint must evaluate to `true` or `false`. For example, the expression \@A > \@B compares two user-defined variables to determine whether the constrained task runs.
45
45
46
-
- The For Loop container can use expressions to build the initialization, evaluation, and the incrementing statements that the looping structure uses. For example, the expression @Counter = 1 initializes the loop counter.
46
+
- The For Loop container can use expressions to build the initialization, evaluation, and the incrementing statements that the looping structure uses. For example, the expression \@Counter = 1 initializes the loop counter.
47
47
48
48
Expressions can also be used to update the values of properties of packages, containers such as the For Loop and Foreach Loop, tasks, package and project level connection managers, log providers, and Foreach enumerators. For example, using a property expression, the string "Localhost.AdventureWorks" can be assigned to the ConnectionName property of the Execute SQL task. For more information, see [Use Property Expressions in Packages](use-property-expressions-in-packages.md).
49
49
@@ -53,7 +53,7 @@ manager: craigg
53
53
## Expression Builder
54
54
The expression builder is a graphical tool for building expressions. It is available in the **Conditional Split Transformation Editor**, **Derived Column Transformation Editor** dialog boxes, and in the **Expression Builder** dialog box, is a graphical tool for building expressions.
55
55
56
-
The expression builder provides folders that contain package-specific elements, and folders that contain the functions, type casts, and operators that the expression language provides. The package-specific elements include system variables and user-defined variables. In the **Conditional Split Transformation Editor** and **Derived Column Transformation Editor** dialog boxes, you can also view data columns. To build expressions for the transformations, you can drag items from the folders to the **Condition** or **Expression** column or you can type the expression directly in the column. The expression builder automatically adds needed syntax elements such as the @ prefix on variable names.
56
+
The expression builder provides folders that contain package-specific elements, and folders that contain the functions, type casts, and operators that the expression language provides. The package-specific elements include system variables and user-defined variables. In the **Conditional Split Transformation Editor** and **Derived Column Transformation Editor** dialog boxes, you can also view data columns. To build expressions for the transformations, you can drag items from the folders to the **Condition** or **Expression** column or you can type the expression directly in the column. The expression builder automatically adds needed syntax elements such as the \@ prefix on variable names.
57
57
58
58
> [!NOTE]
59
59
> The names of user-defined and system variables are case-sensitive.
Copy file name to clipboardExpand all lines: docs/2014/integration-services/expressions/syntax-ssis.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ manager: craigg
33
33
## Identifiers
34
34
Expressions can include column and variable identifiers. The columns can originate in the data source or can be created by transformations in the data flow. Expressions can use lineage identifiers to refer to columns. Lineage identifiers are numbers that uniquely identify package elements. Lineage identifiers, referenced in an expression, must include the pound (#) prefix. For example, the lineage identifier 138 is referenced using #138.
35
35
36
-
Expressions can include the system variables that [!INCLUDE[ssIS](../../includes/ssis-md.md)] provides and custom variables. Variables, when referenced in an expression, must include the @ prefix. For example, the `Counter` variable is referenced using @Counter. The @ character is not part of the variable name; it only indicates to the expression evaluator that the identifier is a variable. For more information, see [Identifiers (SSIS)](identifiers-ssis.md).
36
+
Expressions can include the system variables that [!INCLUDE[ssIS](../../includes/ssis-md.md)] provides and custom variables. Variables, when referenced in an expression, must include the \@ prefix. For example, the `Counter` variable is referenced using \@Counter. The \@ character is not part of the variable name; it only indicates to the expression evaluator that the identifier is a variable. For more information, see [Identifiers (SSIS)](identifiers-ssis.md).
37
37
38
38
## Literals
39
39
Expressions can include numeric, string, and Boolean literals. String literals used in expressions must be enclosed in quotation marks. Numeric and Boolean literals do not take quotation marks. The expression language includes escape sequences for characters that are frequently escaped. For more information, see [Literals (SSIS)](numeric-string-and-boolean-literals.md).
0 commit comments