Skip to content

Commit 17c6550

Browse files
v-shilsv-shils
authored
Merge pull request #8590 from Saisang/sai-fixMultipleAsterisk-1218-7
fix multiple asterisk 3rd batch part 7
2 parents e5cf2e6 + d19ecb1 commit 17c6550

53 files changed

Lines changed: 143 additions & 143 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/2014/analysis-services/instances/configure-service-accounts-analysis-services.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ manager: craigg
3333
## Logon account recommendations
3434
In a failover cluster, all instances of Analysis Services should be configured to use a Windows domain user account. Assign the same account to all instances. See [How to Cluster Analysis Services](https://msdn.microsoft.com/library/dn736073.aspx) for details.
3535

36-
Standalone instances should use the default virtual account, **NT Service\MSSQLServerOLAPService** for the default instance, or **NT Service\MSOLAP$***instance-name* for a named instance. This recommendation applies to Analysis Services instances in all server modes, assuming Windows Server 2008 R2 and later for the operating system, and SQL Server 2012 and later for Analysis Services.
36+
Standalone instances should use the default virtual account, **NT Service\MSSQLServerOLAPService** for the default instance, or **NT Service\MSOLAP$**_instance-name_ for a named instance. This recommendation applies to Analysis Services instances in all server modes, assuming Windows Server 2008 R2 and later for the operating system, and SQL Server 2012 and later for Analysis Services.
3737

3838
## Granting permissions to Analysis Services
3939
This section explains the permissions that Analysis Services requires for local, internal operations, such as starting the executable, reading the configuration file, and loading databases from the data directory. If instead you're looking for guidance on setting permissions for external data access and interoperability with other services and applications, see [Granting additional permissions for specific server operations](#bkmk_tasks) further on in this topic.

‎docs/2014/database-engine/configure-windows/configure-a-server-to-listen-on-a-specific-tcp-port.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ manager: craigg
4545

4646
3. If the **TCP Dynamic Ports** dialog box contains **0**, indicating the [!INCLUDE[ssDE](../../includes/ssde-md.md)] is listening on dynamic ports, delete the 0.
4747

48-
4. In the **IP***n* **Properties** area box, in the **TCP Port** box, type the port number you want this IP address to listen on, and then click **OK**.
48+
4. In the **IP**_n_ **Properties** area box, in the **TCP Port** box, type the port number you want this IP address to listen on, and then click **OK**.
4949

5050
5. In the console pane, click **SQL Server Services**.
5151

‎docs/2014/database-engine/configure-windows/configure-the-database-engine-to-listen-on-multiple-tcp-ports.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -68,9 +68,9 @@ manager: craigg
6868
6969
#### To configure the SQL Server Database Engine to listen on an additional TCP port
7070
71-
1. In SQL Server Configuration Manager, expand **SQL Server Network Configuration**, and then click **Protocols for***<instance_name>*.
71+
1. In SQL Server Configuration Manager, expand **SQL Server Network Configuration**, and then click **Protocols for**_<instance_name>_.
7272
73-
2. Expand **Protocols for***<instance_name>*, and then click **TCP/IP**.
73+
2. Expand **Protocols for**_<instance_name>_, and then click **TCP/IP**.
7474
7575
3. In the right pane, right-click each disabled IP address that you want to enable, and then click **Enable**.
7676
@@ -83,7 +83,7 @@ manager: craigg
8383
8484
6. In the left pane, click **SQL Server Services**.
8585
86-
7. In the right pane, right-click **SQL Server***<instance_name>*, and then click **Restart**.
86+
7. In the right pane, right-click **SQL Server**_<instance_name>_, and then click **Restart**.
8787
8888
When the [!INCLUDE[ssDE](../../includes/ssde-md.md)] restarts, the Error log will list the ports on which [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is listening.
8989

‎docs/2014/relational-databases/database-mail/configure-database-mail.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -388,7 +388,7 @@ manager: craigg
388388

389389

390390
### <a name="TestEmail"></a> Send Test E-Mail Page
391-
Use the **Send Test E-Mail from***<instance_name>* page to send an e-mail message using the specified Database Mail profile. Only members of the **sysadmin** fixed server role can send test e-mail using this page.
391+
Use the **Send Test E-Mail from**_<instance_name>_ page to send an e-mail message using the specified Database Mail profile. Only members of the **sysadmin** fixed server role can send test e-mail using this page.
392392

393393
**Database Mail Profile**
394394
Select a Database Mail profile from the list. This is a required field. If no profiles are shown, there are no profiles or you do not have permission to a profile. Use the **Database Mail Configuration Wizard** to create and configure profiles. If no profiles are listed, use the Database Mail Configuration Wizard to create a profile for your use.

‎docs/2014/relational-databases/logs/change-the-target-recovery-time-of-a-database-sql-server.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ manager: craigg
5151

5252
2. Use the following [ALTER DATABASE](/sql/t-sql/statements/alter-database-transact-sql-set-options)statement, as follows:
5353

54-
TARGET_RECOVERY_TIME **=***target_recovery_time* { SECONDS | MINUTES }
54+
TARGET_RECOVERY_TIME **=**_target_recovery_time_ { SECONDS | MINUTES }
5555

5656
*target_recovery_time*
5757
When greater than 0 (the default), specifies the upper-bound on the recovery time for the specified database in the event of a crash.

‎docs/2014/relational-databases/native-client-odbc-bulk-copy-operations/bulk-copying-from-program-variables.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -22,25 +22,25 @@ manager: craigg
2222
# Bulk Copying from Program Variables
2323
You can bulk copy directly from program variables. After allocating variables to hold the data for a row and calling [bcp_init](../native-client-odbc-extensions-bulk-copy-functions/bcp-init.md) to start the bulk copy, call [bcp_bind](../native-client-odbc-extensions-bulk-copy-functions/bcp-bind.md) for each column to specify the location and format of the program variable to be associated with the column. Fill each variable with data, then call [bcp_sendrow](../native-client-odbc-extensions-bulk-copy-functions/bcp-sendrow.md) to send one row of data to the server. Repeat the process of filling the variables and calling **bcp_sendrow** until all the rows have been sent to the server, then call [bcp_done](../native-client-odbc-extensions-bulk-copy-functions/bcp-done.md) to specify that the operation is complete.
2424

25-
The **bcp_bind***pData* parameter contains the address of the variable being bound to the column. The data for each column can be stored in one of two ways:
25+
The **bcp_bind**_pData_ parameter contains the address of the variable being bound to the column. The data for each column can be stored in one of two ways:
2626

2727
- Allocate one variable to hold the data.
2828

2929
- Allocate an indicator variable followed immediately by the data variable.
3030

31-
The indicator variable indicates the length of the data for variable-length columns, and also indicates NULL values if the column allows NULLs. If only a data variable is used, then the address of this variable is stored in the **bcp_bind***pData* parameter. If an indicator variable is used, the address of the indicator variable is stored in the **bcp_bind***pData* parameter. The bulk copy functions calculate the location of the data variable by adding the **bcp_bind***cbIndicator* and *pData* parameters.
31+
The indicator variable indicates the length of the data for variable-length columns, and also indicates NULL values if the column allows NULLs. If only a data variable is used, then the address of this variable is stored in the **bcp_bind**_pData_ parameter. If an indicator variable is used, the address of the indicator variable is stored in the **bcp_bind**_pData_ parameter. The bulk copy functions calculate the location of the data variable by adding the **bcp_bind**_cbIndicator_ and *pData* parameters.
3232

3333
**bcp_bind** supports three methods for dealing with variable-length data:
3434

3535
- Use *cbData* with only a data variable. Place the length of the data in *cbData*. Each time the length of the data to be bulk copied changes, call [bcp_collen](../native-client-odbc-extensions-bulk-copy-functions/bcp-collen.md)to reset *cbData*. If one of the other two methods is being used, specify SQL_VARLEN_DATA for *cbData*. If all the data values being supplied for a column are NULL, specify SQL_NULL_DATA for *cbData*.
3636

3737
- Use indicator variables. As each new data value is moved into the data variable, store the length of the value in the indicator variable. If one of the other two methods is being used, specify 0 for *cbIndicator*.
3838

39-
- Use terminator pointers. Load the **bcp_bind***pTerm* parameter with the address of the bit pattern that terminates the data. If one of the other two methods is being used, specify NULL for *pTerm*.
39+
- Use terminator pointers. Load the **bcp_bind**_pTerm_ parameter with the address of the bit pattern that terminates the data. If one of the other two methods is being used, specify NULL for *pTerm*.
4040

4141
All three of these methods can be used on the same **bcp_bind** call, in which case the specification that results in the smallest amount of data being copied is used.
4242

43-
The **bcp_bind***type* parameter uses DB-Library data type identifiers, not ODBC data type identifiers. DB-Library data type identifiers are defined in sqlncli.h for use with the ODBC **bcp_bind** function.
43+
The **bcp_bind**_type_ parameter uses DB-Library data type identifiers, not ODBC data type identifiers. DB-Library data type identifiers are defined in sqlncli.h for use with the ODBC **bcp_bind** function.
4444

4545
Bulk copy functions do not support all ODBC C data types. For example, the bulk copy functions do not support the ODBC SQL_C_TYPE_TIMESTAMP structure, so use [SQLBindCol](../native-client-odbc-api/sqlbindcol.md) or [SQLGetData](../native-client-odbc-api/sqlgetdata.md) to convert ODBC SQL_TYPE_TIMESTAMP data to a SQL_C_CHAR variable. If you then use **bcp_bind** with a *type* parameter of SQLCHARACTER to bind the variable to a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] **datetime** column, the bulk copy functions convert the timestamp escape clause in the character variable to the proper datetime format.
4646

@@ -100,7 +100,7 @@ GO
100100

101101
The bulk copy functions can be used to quickly load data into [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] that has been read from an ODBC data source. Use [SQLBindCol](../native-client-odbc-api/sqlbindcol.md) to bind the columns of a result set to program variables, then use **bcp_bind** to bind the same program variables to a bulk copy operation. Calling [SQLFetchScroll](../native-client-odbc-api/sqlfetchscroll.md) or **SQLFetch** then fetches a row of data from the ODBC data source into the program variables, and calling [bcp_sendrow](../native-client-odbc-extensions-bulk-copy-functions/bcp-sendrow.md) bulk copies the data from the program variables to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] .
102102

103-
An application can use the [bcp_colptr](../native-client-odbc-extensions-bulk-copy-functions/bcp-colptr.md) function anytime it needs to change the address of the data variable originally specified in the **bcp_bind** *pData* parameter. An application can use the [bcp_collen](../native-client-odbc-extensions-bulk-copy-functions/bcp-collen.md) function anytime it needs to change the data length originally specified in the **bcp_bind***cbData* parameter.
103+
An application can use the [bcp_colptr](../native-client-odbc-extensions-bulk-copy-functions/bcp-colptr.md) function anytime it needs to change the address of the data variable originally specified in the **bcp_bind** _pData_ parameter. An application can use the [bcp_collen](../native-client-odbc-extensions-bulk-copy-functions/bcp-collen.md) function anytime it needs to change the data length originally specified in the **bcp_bind**_cbData_ parameter.
104104

105105
You cannot read data from [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] into program variables using bulk copy; there is nothing like a "bcp_readrow" function. You can only send data from the application to the server.
106106

‎docs/2014/relational-databases/native-client-odbc-extensions-bulk-copy-functions/bcp-bind.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ bcp_bind(hdbc, szName, 0,
140140
## Remarks
141141
Use **bcp_bind** for a fast, efficient way to copy data from a program variable into a table in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
142142

143-
Call [bcp_init](bcp-init.md) before calling this or any other bulk-copy function. Calling **bcp_init** sets the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] target table for bulk copy. When calling **bcp_init** for use with **bcp_bind** and [bcp_sendrow](bcp-sendrow.md), the **bcp_init** *szDataFile* parameter, indicating the data file, is set to NULL; the **bcp_init**_eDirection_ parameter is set to DB_IN.
143+
Call [bcp_init](bcp-init.md) before calling this or any other bulk-copy function. Calling **bcp_init** sets the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] target table for bulk copy. When calling **bcp_init** for use with **bcp_bind** and [bcp_sendrow](bcp-sendrow.md), the **bcp_init** _szDataFile_ parameter, indicating the data file, is set to NULL; the **bcp_init**_eDirection_ parameter is set to DB_IN.
144144

145145
Make a separate **bcp_bind** call for every column in the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] table into which you want to copy. After the necessary **bcp_bind** calls have been made, then call **bcp_sendrow** to send a row of data from your program variables to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Rebinding a column is not supported.
146146

‎docs/2014/relational-databases/native-client-odbc-extensions-bulk-copy-functions/bcp-init.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ eDirection
5454

5555
If *eDirection* is DB_OUT, *szTable* can also be the name of a database view.
5656

57-
If *eDirection* is DB_OUT and a SELECT statement is specified using [bcp_control](bcp-control.md) before [bcp_exec](bcp-exec.md) is called, **bcp_init***szTable* must be set to NULL.
57+
If *eDirection* is DB_OUT and a SELECT statement is specified using [bcp_control](bcp-control.md) before [bcp_exec](bcp-exec.md) is called, **bcp_init**_szTable_ must be set to NULL.
5858

5959
*szDataFile*
6060
Is the name of the user file to be copied into or out of. If data is being copied directly from variables by using [bcp_sendrow](bcp-sendrow.md), set *szDataFile* to NULL.

‎docs/2014/relational-databases/native-client-odbc-stored-procedures/calling-a-stored-procedure.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,19 +27,19 @@ manager: craigg
2727
2828
The ODBC CALL escape sequence for calling a procedure is:
2929

30-
{[**?=**]**call***procedure_name*[([*parameter*][**,**[*parameter*]]...)]}
30+
{[**?=**]**call**_procedure_name_[([*parameter*][**,**[*parameter*]]...)]}
3131

3232
where *procedure_name* specifies the name of a procedure and *parameter* specifies a procedure parameter. Named parameters are only supported in statements using the ODBC CALL escape sequence.
3333

3434
A procedure can have zero or more parameters. It can also return a value (as indicated by the optional parameter marker ?= at the start of the syntax). If a parameter is an input or an input/output parameter, it can be a literal or a parameter marker. If the parameter is an output parameter, it must be a parameter marker because the output is unknown. Parameter markers must be bound with [SQLBindParameter](../../relational-databases/native-client-odbc-api/sqlbindparameter.md) before the procedure call statement is executed.
3535

3636
Input and input/output parameters can be omitted from procedure calls. If a procedure is called with parentheses but without any parameters, the driver instructs the data source to use the default value for the first parameter. For example:
3737

38-
{**call** *procedure_name***( )**}
38+
{**call** _procedure_name_**( )**}
3939

4040
If the procedure does not have any parameters, the procedure can fail. If a procedure is called without parentheses, the driver does not send any parameter values. For example:
4141

42-
{**call** *procedure_name*}
42+
{**call** _procedure_name_}
4343

4444
Literals can be specified for input and input/output parameters in procedure calls. For example, the procedure InsertOrder has five input parameters. The following call to InsertOrder omits the first parameter, provides a literal for the second parameter, and uses a parameter marker for the third, fourth, and fifth parameters. (Parameters are numbered sequentially, beginning with a value of 1.)
4545

‎docs/2014/relational-databases/native-client/ole-db/stored-procedures-calling.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ manager: craigg
8585

8686
The general syntax for calling a procedure by using the ODBC CALL escape sequence is:
8787

88-
{[**?=**]**call***procedure_name*[**(**[*parameter*][**,**[*parameter*]]...**)**]}
88+
{[**?=**]**call**_procedure_name_[**(**[*parameter*][**,**[*parameter*]]...**)**]}
8989

9090
For example:
9191

0 commit comments

Comments
 (0)