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/database-mirroring/add-a-database-mirroring-witness-using-windows-authentication-transact-sql.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
@@ -46,7 +46,7 @@ manager: craigg
46
46
47
47
3. Connect to the principal server and issue the following statement:
48
48
49
-
ALTER DATABASE *<database_name>* SET WITNESS **=***<server_network_address>*
49
+
ALTER DATABASE *<database_name>* SET WITNESS **=**_<server_network_address>_
50
50
51
51
where *<database_name>* is the name of the database to be mirrored (this name is the same on both partners), and *<server_network_address>* is the server network address of the witness server instance.
|*database*|Is the database from which the transaction log, partial database, or complete database is backed up.|
157
-
|FILE **=***logical_file_name*|Specifies the logical name of a file to include in the file backup.|
158
-
|FILEGROUP **=***logical_filegroup_name*|Specifies the logical name of a filegroup to include in the file backup. Under the simple recovery model, a filegroup backup is allowed only for a read-only filegroup.|
157
+
|FILE **=**_logical_file_name_|Specifies the logical name of a file to include in the file backup.|
158
+
|FILEGROUP **=**_logical_filegroup_name_|Specifies the logical name of a filegroup to include in the file backup. Under the simple recovery model, a filegroup backup is allowed only for a read-only filegroup.|
159
159
|[**,**...*f*]|Is a placeholder that indicates that multiple files and filegroups may be specified. The number of files or filegroups is unlimited.|
160
-
|*backup_device*[**,**...*n*]|Specifies a list of from 1 to 64 backup devices to use for the backup operation. You can specify a physical backup device, or you can specify a corresponding logical backup device, if already defined. To specify a physical backup device, use the DISK or TAPE option:<br /><br /> { DISK | TAPE } **=***physical_backup_device_name*<br /><br /> For more information, see [Backup Devices (SQL Server)](backup-devices-sql-server.md).|
160
+
|*backup_device*[**,**...*n*]|Specifies a list of from 1 to 64 backup devices to use for the backup operation. You can specify a physical backup device, or you can specify a corresponding logical backup device, if already defined. To specify a physical backup device, use the DISK or TAPE option:<br /><br /> { DISK | TAPE } **=**_physical_backup_device_name_<br /><br /> For more information, see [Backup Devices (SQL Server)](backup-devices-sql-server.md).|
161
161
|WITH *with_options*[**,**...*o*]|Optionally, specifies one or more additional options, such as DIFFERENTIAL.<br /><br /> Note: A differential file backup requires a full file backup as a base. For more information, see [Create a Differential Database Backup (SQL Server)](create-a-differential-database-backup-sql-server.md).|
162
162
163
163
2. Under the full recovery model, you must also back up the transaction log. To use a complete set of full file backups to restore a database, you must also have enough log backups to span all the file backups, from the start of the first file backup. For more information, see [Back Up a Transaction Log (SQL Server)](back-up-a-transaction-log-sql-server.md).
Copy file name to clipboardExpand all lines: docs/2014/relational-databases/backup-restore/backup-devices-sql-server.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,7 @@ manager: craigg
80
80
81
81
BACKUP DATABASE *database_name*
82
82
83
-
TO DISK **=** { **'***physical_backup_device_name***'** | **@***physical_backup_device_name_var* }
83
+
TO DISK **=** { **'**_physical_backup_device_name_**'** | **@**_physical_backup_device_name_var_ }
84
84
85
85
For example:
86
86
@@ -94,7 +94,7 @@ GO
94
94
95
95
RESTORE { DATABASE | LOG } *database_name*
96
96
97
-
FROM DISK **=** { **'***physical_backup_device_name***'** | **@***physical_backup_device_name_var* }
97
+
FROM DISK **=** { **'**_physical_backup_device_name_**'** | **@**_physical_backup_device_name_var_ }
98
98
99
99
For example,
100
100
@@ -130,7 +130,7 @@ GO
130
130
> Backing up data over a network can be subject to network errors; therefore, we recommend that when you are using a remote disk you verify the backup operation after it finishes. For more information, see [RESTORE VERIFYONLY (Transact-SQL)](/sql/t-sql/statements/restore-statements-verifyonly-transact-sql).
131
131
132
132
#### Specifying a Universal Naming Convention (UNC) Name
133
-
To specify a network share in a backup or restore command, you should use the fully qualified universal naming convention (UNC) name of the file for the backup device. A UNC name has the form **\\\\***Systemname***\\***ShareName***\\***Path***\\***FileName*.
133
+
To specify a network share in a backup or restore command, you should use the fully qualified universal naming convention (UNC) name of the file for the backup device. A UNC name has the form **\\\\**_Systemname_**\\**_ShareName_**\\**_Path_**\\**_FileName_.
134
134
135
135
For example:
136
136
@@ -168,7 +168,7 @@ GO
168
168
169
169
BACKUP { DATABASE | LOG } *database_name*
170
170
171
-
TO TAPE **=** { **'***physical_backup_device_name***'** | **@***physical_backup_device_name_var* }
171
+
TO TAPE **=** { **'**_physical_backup_device_name_**'** | **@**_physical_backup_device_name_var_ }
172
172
173
173
For example:
174
174
@@ -182,7 +182,7 @@ GO
182
182
183
183
RESTORE { DATABASE | LOG } *database_name*
184
184
185
-
FROM TAPE **=** { **'***physical_backup_device_name***'** | **@***physical_backup_device_name_var* }
185
+
FROM TAPE **=** { **'**_physical_backup_device_name_**'** | **@**_physical_backup_device_name_var_ }
186
186
187
187
### <aname="TapeOptions"></a> Tape-Specific BACKUP and RESTORE Options (Transact-SQL)
188
188
To facilitate tape management, the BACKUP statement provides the following tape-specific options:
@@ -201,7 +201,7 @@ GO
201
201
### <aname="OpenTapes"></a> Managing Open Tapes
202
202
To view a list of open tape devices and the status of mount requests, query the [sys.dm_io_backup_tapes](/sql/relational-databases/system-dynamic-management-views/sys-dm-io-backup-tapes-transact-sql) dynamic management view. This view shows all the open tapes. These include in-use tapes that are temporarily idle while they wait for the next BACKUP or RESTORE operation.
203
203
204
-
If a tape has been accidentally left open, the fastest way to release the tape is by using the following command: RESTORE REWINDONLY FROM TAPE **=***backup_device_name*. For more information, see [RESTORE REWINDONLY (Transact-SQL)](/sql/t-sql/statements/restore-statements-rewindonly-transact-sql).
204
+
If a tape has been accidentally left open, the fastest way to release the tape is by using the following command: RESTORE REWINDONLY FROM TAPE **=**_backup_device_name_. For more information, see [RESTORE REWINDONLY (Transact-SQL)](/sql/t-sql/statements/restore-statements-rewindonly-transact-sql).
205
205
206
206
## Using the Windows Azure Blob Storage Service
207
207
SQL Server Backups can be written to the Windows Azure Blob Storage Service. For more information on how to use the Windows Azure Blob storage service for your backups, see [SQL Server Backup and Restore with Windows Azure Blob Storage Service](sql-server-backup-and-restore-with-microsoft-azure-blob-storage-service.md).
Copy file name to clipboardExpand all lines: docs/2014/relational-databases/native-client-odbc-extensions-bulk-copy-functions/bcp-bind.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
@@ -140,7 +140,7 @@ bcp_bind(hdbc, szName, 0,
140
140
## Remarks
141
141
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)].
142
142
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.
144
144
145
145
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.
Copy file name to clipboardExpand all lines: docs/2014/reporting-services/report-design/add-a-filter-report-builder-and-ssrs.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
@@ -28,7 +28,7 @@ manager: craigg
28
28
29
29
1. Open a report in **Design** view.
30
30
31
-
2. Select the data region on the design surface, and then right-click *\<data region>***Properties**. For a gauge, select **Gauge Panel Properties**. The *\<data region>***Properties** dialog box opens.
31
+
2. Select the data region on the design surface, and then right-click _\<data region>_**Properties**. For a gauge, select **Gauge Panel Properties**. The _\<data region>_**Properties** dialog box opens.
32
32
33
33
> [!NOTE]
34
34
> On a Tablix data region, right-click the corner cell or a row or column handle, and then click **Tablix Properties**.
Copy file name to clipboardExpand all lines: docs/2014/ssms/agent/assign-alerts-to-an-operator.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
@@ -62,7 +62,7 @@ manager: craigg
62
62
63
63
4. Right-click the operator to which you want to assign an alert and select **Properties**, and select the **Notifications** page.
64
64
65
-
5. In the *operator_name***Properties** dialog box, under **Select a page**, select **Notifications**.
65
+
5. In the _operator_name_**Properties** dialog box, under **Select a page**, select **Notifications**.
66
66
67
67
6. Under **View notifications sent to this user by**, select **Alerts** to view a list of alerts sent to this operator or select **Jobs** to view a list of jobs that send notifications to this operator. Select one or more of the following checkboxes to define the notification method for each notification as necessary: **E-mail**, **Pager**, or **Net send**.
0 commit comments