Skip to content

Commit 3f4996c

Browse files
author
MightyPen
committed
docs/relational-databases/, 'http:' 's', 'en-us/ erased, CATS inspired.
1 parent e1af443 commit 3f4996c

875 files changed

Lines changed: 1517 additions & 1517 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/relational-databases/backup-restore/create-a-full-database-backup-sql-server.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -380,7 +380,7 @@ Backup-SqlDatabase -ServerInstance "MyServer" –Database $database -BackupFile
380380
- [Use the Maintenance Plan Wizard](../../relational-databases/maintenance-plans/use-the-maintenance-plan-wizard.md)
381381

382382
## See also
383-
**[Troubleshooting SQL Server backup and restore operations](https://support.microsoft.com/en-us/kb/224071)**
383+
**[Troubleshooting SQL Server backup and restore operations](https://support.microsoft.com/kb/224071)**
384384
[Backup Overview (SQL Server)](../../relational-databases/backup-restore/backup-overview-sql-server.md)
385385
[Transaction Log Backups (SQL Server)](../../relational-databases/backup-restore/transaction-log-backups-sql-server.md)
386386
[Media Sets, Media Families, and Backup Sets (SQL Server)](../../relational-databases/backup-restore/media-sets-media-families-and-backup-sets-sql-server.md)

‎docs/relational-databases/backup-restore/create-an-encrypted-backup.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ manager: craigg
7272
7373
**Prerequisites:**
7474
75-
- A windows storage account and a container. For more information, see. [Lesson 1: Create Windows Azure Storage Objects](http://msdn.microsoft.com/library/74edd1fd-ab00-46f7-9e29-7ba3f1a446c5).
75+
- A windows storage account and a container. For more information, see. [Lesson 1: Create Windows Azure Storage Objects](https://msdn.microsoft.com/library/74edd1fd-ab00-46f7-9e29-7ba3f1a446c5).
7676
7777
- A Database Master Key for the master database, and a certificate or asymmetric key on the instance of SQL Server. For encryption requirements and permissions, see [Backup Encryption](../../relational-databases/backup-restore/backup-encryption.md).
7878

‎docs/relational-databases/backup-restore/create-credential-authenticate-to-azure-storage.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ manager: craigg
2525

2626
## Windows Azure Credentials
2727
**Management Certificate**
28-
Use this option to specify a certificate from the local certificate store that matches the management certificate from Windows Azure. For more information on Windows Azure management certificate, see [Create and Upload a Management Certificate for Windows Azure](http://go.microsoft.com/fwlink/?LinkId=320781).
28+
Use this option to specify a certificate from the local certificate store that matches the management certificate from Windows Azure. For more information on Windows Azure management certificate, see [Create and Upload a Management Certificate for Windows Azure](https://go.microsoft.com/fwlink/?LinkId=320781).
2929

3030
**Subscription**
3131
Select, type, or paste your Windows Azure subscription ID that matches the management certificate from the local certificate store.
@@ -34,7 +34,7 @@ manager: craigg
3434
Use this option if you have a publishing profile downloaded to your computer. If you use this option, the subscription ID, and the certificate are auto populated.
3535

3636
> [!CAUTION]
37-
> SQL Server currently supports publishing profile version 2.0. To download the supported version of the publishing profile, see [Download Publishing Profile 2.0](http://go.microsoft.com/fwlink/?LinkId=396421).
37+
> SQL Server currently supports publishing profile version 2.0. To download the supported version of the publishing profile, see [Download Publishing Profile 2.0](https://go.microsoft.com/fwlink/?LinkId=396421).
3838
3939
## Storage Account
4040
Select the storage account you want to use to store the backup files on.

‎docs/relational-databases/backup-restore/deleting-backup-blob-files-with-active-leases.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ manager: craigg
1616
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
1717
When backing up to or restoring from Microsoft Azure storage, SQL Server acquires an infinite lease to lock exclusive access to the blob. When the backup or restore process is successfully completed, the lease is released. If a backup or restore fails, the backup process attempts to clean up any invalid blobs. However, if the backup fails due to prolonged or sustained network connectivity failure, the backup process may not be able gain access to the blob and the blob may remain orphaned. This means the blob cannot be written to or deleted until the lease is released. This topic describes how to release (break) the lease and delete the blob.
1818

19-
For more information on lease types, read this [article](http://go.microsoft.com/fwlink/?LinkId=275664).
19+
For more information on lease types, read this [article](https://go.microsoft.com/fwlink/?LinkId=275664).
2020

2121
If the backup operation fails, it can result in an invalid backup file. The backup blob file might also have an active lease, preventing it from being deleted or overwritten. To delete or overwrite such blobs, the lease should first be released (broken). If there are backup failures, we recommend that you clean up leases and delete blobs. You can also periodically clean up leases and delete blobs as part of your storage management tasks.
2222

@@ -27,7 +27,7 @@ manager: craigg
2727

2828
1. **Identify blobs with leases:** If you have a script or a process that runs the backup processes, you might be able to capture the failure within the script or process and use that to clean up the blobs. You can also use the LeaseStats and LeastState properties to identify blobs with leases on them. Once you have identified the blobs, review the list and verify the validity of the backup file before deleting the blob.
2929

30-
2. **Break the lease:** An authorized request can break the lease without supplying a lease ID. See [here](http://go.microsoft.com/fwlink/?LinkID=275664) for more information.
30+
2. **Break the lease:** An authorized request can break the lease without supplying a lease ID. See [here](https://go.microsoft.com/fwlink/?LinkID=275664) for more information.
3131

3232
> [!TIP]
3333
> SQL Server issues a lease ID to establish exclusive access during the restore operation. The restore lease ID is BAC2BAC2BAC2BAC2BAC2BAC2BAC2BAC2.

‎docs/relational-databases/backup-restore/enable-sql-server-managed-backup-to-microsoft-azure.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ manager: craigg
1616
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
1717
This topic describes how to enable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] with default settings at both the database and instance level. It also describes how to enable email notifications and how to monitor backup activity.
1818

19-
This tutorial uses Azure PowerShell. Before starting the tutorial, [download and install Azure PowerShell](http://azure.microsoft.com/documentation/articles/powershell-install-configure/).
19+
This tutorial uses Azure PowerShell. Before starting the tutorial, [download and install Azure PowerShell](https://azure.microsoft.com/documentation/articles/powershell-install-configure/).
2020

2121
> [!IMPORTANT]
2222
> If you also want to enable advanced options or use a custom schedule, configure those settings first before enabling [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)]. For more information, see [Configure Advanced Options for SQL Server Managed Backup to Microsoft Azure](../../relational-databases/backup-restore/configure-advanced-options-for-sql-server-managed-backup-to-microsoft-azure.md).
@@ -25,15 +25,15 @@ manager: craigg
2525

2626
#### Create the Azure Blob Container
2727

28-
1. **Sign up for Azure:** If you already have an Azure subscription, go to the next step. Otherwise, you can get started with a [free trial](http://azure.microsoft.com/pricing/free-trial/) or explore [purchase options](http://azure.microsoft.com/pricing/purchase-options/).
28+
1. **Sign up for Azure:** If you already have an Azure subscription, go to the next step. Otherwise, you can get started with a [free trial](https://azure.microsoft.com/pricing/free-trial/) or explore [purchase options](https://azure.microsoft.com/pricing/purchase-options/).
2929

3030
2. **Create an Azure storage account:** If you already have a storage account, go to the next step. Otherwise, you can use the [Azure Management Portal](https://manage.windowsazure.com/) or Azure PowerShell to create the storage account. The following `New-AzureStorageAccount` command creates a storage account named `managedbackupstorage` in the East US region.
3131

3232
```powershell
3333
New-AzureStorageAccount -StorageAccountName "managedbackupstorage" -Location "EAST US"
3434
```
3535
36-
For more information about storage accounts, see [About Azure Storage Accounts](http://azure.microsoft.com/documentation/articles/storage-create-storage-account/).
36+
For more information about storage accounts, see [About Azure Storage Accounts](https://azure.microsoft.com/documentation/articles/storage-create-storage-account/).
3737
3838
3. **Create a blob container for the backup files:** You can create a blob container in the Azure Management Portal or with Azure PowerShell. The following `New-AzureStorageContainer` command creates a blob container named `backupcontainer` in the `managedbackupstorage` storage account.
3939
@@ -62,7 +62,7 @@ manager: craigg
6262
|**Container URL:**|https://managedbackupstorage.blob.core.windows.net/backupcontainer|
6363
|**SAS token:**|sv=2014-02-14&sr=c&sig=xM2LXVo1Erqp7LxQ%9BxqK9QC6%5Qabcd%9LKjHGnnmQWEsDf%5Q%se=2015-05-14T14%3B93%4V20X&sp=rwdl|
6464
65-
Record the container URL and SAS for use in creating a SQL CREDENTIAL. For more information about SAS, see [Shared Access Signatures, Part 1: Understanding the SAS Model](http://azure.microsoft.com/documentation/articles/storage-dotnet-shared-access-signature-part-1/).
65+
Record the container URL and SAS for use in creating a SQL CREDENTIAL. For more information about SAS, see [Shared Access Signatures, Part 1: Understanding the SAS Model](https://azure.microsoft.com/documentation/articles/storage-dotnet-shared-access-signature-part-1/).
6666
6767
#### Enable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)]
6868

‎docs/relational-databases/backup-restore/file-restores-simple-recovery-model.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ manager: craigg
4040

4141
In an *online file restore*, if database is online at restore time, it remains online during the file restore. However, each filegroup in which a file is being restored is offline during the restore operation. After all the files in an offline filegroup are recovered, the filegroup is automatically brought online.
4242

43-
For information about support for online page and file restore, see [Database Engine Features and Tasks](http://msdn.microsoft.com/library/d9efe145-3306-4d61-bd77-e2af43e19c34). For more information about online restores, see [Online Restore (SQL Server)](../../relational-databases/backup-restore/online-restore-sql-server.md).
43+
For information about support for online page and file restore, see [Database Engine Features and Tasks](https://msdn.microsoft.com/library/d9efe145-3306-4d61-bd77-e2af43e19c34). For more information about online restores, see [Online Restore (SQL Server)](../../relational-databases/backup-restore/online-restore-sql-server.md).
4444

4545
> [!TIP]
4646
> If you want the database to be offline for a file restore, take the database offline before you start the restore sequence by executing the following [ALTER DATABASE](../../t-sql/statements/alter-database-transact-sql-set-options.md) statement: ALTER DATABASE *database_name* SET OFFLINE.
@@ -90,7 +90,7 @@ manager: craigg
9090

9191
- [Restore Files and Filegroups (SQL Server)](../../relational-databases/backup-restore/restore-files-and-filegroups-sql-server.md)
9292

93-
- [Restore.SqlRestore Method (Server) (SMO)](http://msdn.microsoft.com/library/microsoft.sqlserver.management.smo.restore.sqlrestore.aspx)
93+
- [Restore.SqlRestore Method (Server) (SMO)](https://msdn.microsoft.com/library/microsoft.sqlserver.management.smo.restore.sqlrestore.aspx)
9494

9595
## See Also
9696
[Backup and Restore: Interoperability and Coexistence (SQL Server)](../../relational-databases/backup-restore/backup-and-restore-interoperability-and-coexistence-sql-server.md)

‎docs/relational-databases/backup-restore/recovery-models-sql-server.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ manager: craigg
6161
[ALTER DATABASE SET Options (Transact-SQL)](../../t-sql/statements/alter-database-transact-sql-set-options.md)
6262
[Back Up and Restore of SQL Server Databases](../../relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md)
6363
[The Transaction Log (SQL Server)](../../relational-databases/logs/the-transaction-log-sql-server.md)
64-
[Automated Administration Tasks (SQL Server Agent)](http://msdn.microsoft.com/library/541ee5ac-2c9f-4b74-b4f0-13b7bd5920b0)
64+
[Automated Administration Tasks (SQL Server Agent)](https://msdn.microsoft.com/library/541ee5ac-2c9f-4b74-b4f0-13b7bd5920b0)
6565
[Restore and Recovery Overview (SQL Server)](../../relational-databases/backup-restore/restore-and-recovery-overview-sql-server.md)
6666

6767

‎docs/relational-databases/backup-restore/restore-and-recovery-overview-sql-server.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -146,9 +146,9 @@ manager: craigg
146146

147147
For more information, see about the Database Recovery Advisor, see the following [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Manageability blogs:
148148

149-
- [Recovery Advisor: An Introduction](http://blogs.msdn.com/b/managingsql/archive/2011/07/13/recovery-advisor-an-introduction.aspx)
149+
- [Recovery Advisor: An Introduction](https://blogs.msdn.com/b/managingsql/archive/2011/07/13/recovery-advisor-an-introduction.aspx)
150150

151-
- [Recovery Advisor: Using SSMS to create/restore split backups](http://blogs.msdn.com/b/managingsql/archive/2011/07/13/recovery-advisor-using-ssms-to-create-restore-split-backups.aspx)
151+
- [Recovery Advisor: Using SSMS to create/restore split backups](https://blogs.msdn.com/b/managingsql/archive/2011/07/13/recovery-advisor-using-ssms-to-create-restore-split-backups.aspx)
152152

153153
## <a name="RelatedContent"></a> Related Content
154154
None.

‎docs/relational-databases/backup-restore/restoring-from-backups-stored-in-microsoft-azure.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,9 @@ manager: craigg
3232
- The restore task is used to restore a database using the SQL Server Management Studio. The backup media page now includes the **URL** option to show backup files stored in the Windows Azure Blob storage service. You also must provide the SQL Credential that is used to authenticate to the storage account. The **Backup sets to restore** grid is then populated with the available backups in the Windows Azure Blob storage. For more information, see [Restoring from Windows Azure storage Using SQL Server Management Studio](../../relational-databases/backup-restore/sql-server-backup-to-url.md#RestoreSSMS).
3333

3434
### Optimizing Restores
35-
To reduce restore write time, Add **perform volume maintenance tasks** user right to the SQL Server user account. For more information, see [Database File Initialization](http://go.microsoft.com/fwlink/?LinkId=271622). If restore is still slow with instant file initialization turned on, look at the size of the log file on the instance where the database was backed up. If the log is very large in size (multiple GBs), it would be expected that restore would be slow. During restore the log file must be zeroed which takes a significant amount of time.
35+
To reduce restore write time, Add **perform volume maintenance tasks** user right to the SQL Server user account. For more information, see [Database File Initialization](https://go.microsoft.com/fwlink/?LinkId=271622). If restore is still slow with instant file initialization turned on, look at the size of the log file on the instance where the database was backed up. If the log is very large in size (multiple GBs), it would be expected that restore would be slow. During restore the log file must be zeroed which takes a significant amount of time.
3636

37-
To reduce restore times it is recommended that you use compressed backups. For backup sizes exceeding 25 GB, use [AzCopy utility](http://blogs.msdn.com/b/windowsazurestorage/archive/2012/12/03/azcopy-uploading-downloading-files-for-windows-azure-blobs.aspx) to download to the local drive and then perform the restore. For other backup best practices and recommendations, see [SQL Server Backup to URL Best Practices and Troubleshooting](../../relational-databases/backup-restore/sql-server-backup-to-url-best-practices-and-troubleshooting.md).
37+
To reduce restore times it is recommended that you use compressed backups. For backup sizes exceeding 25 GB, use [AzCopy utility](https://blogs.msdn.com/b/windowsazurestorage/archive/2012/12/03/azcopy-uploading-downloading-files-for-windows-azure-blobs.aspx) to download to the local drive and then perform the restore. For other backup best practices and recommendations, see [SQL Server Backup to URL Best Practices and Troubleshooting](../../relational-databases/backup-restore/sql-server-backup-to-url-best-practices-and-troubleshooting.md).
3838

3939
You can also turn on Trace Flag 3051 when doing the restore to generate a detailed log. This log file is placed in the log directory, and is named using the format: BackupToUrl-\<instancename>-\<dbname>-action-\<PID>.log. The log file includes information about each round trip to Windows Azure Storage including timing that can be helpful in diagnosing the issue.
4040

0 commit comments

Comments
 (0)