|
|
@@ -8,8 +8,14 @@
|
|
|
"language_info": {
|
|
|
"name": "sql",
|
|
|
"version": ""
|
|
|
+ },
|
|
|
+ "azdata_notebook_guid": "968A824C-277C-4FA8-9519-16D8840BECD1",
|
|
|
+ "extensions": {
|
|
|
+ "azuredatastudio": {
|
|
|
+ "version": 1,
|
|
|
+ "views": []
|
|
|
+ }
|
|
|
}
|
|
|
- "azdata_notebook_guid": "968A824C-277C-4FA8-9519-16D8840BECD1"
|
|
|
},
|
|
|
"nbformat_minor": 2,
|
|
|
"nbformat": 4,
|
|
|
@@ -59,7 +65,12 @@
|
|
|
"The following set of T-SQL commands will help you identify if a database transaction log is not truncated and the reason for it. The following script will also recommend steps to resolve the issue:"
|
|
|
],
|
|
|
"metadata": {
|
|
|
- "azdata_cell_guid": "d25a34e0-7c52-4112-bf09-8feafe21a142"
|
|
|
+ "azdata_cell_guid": "d25a34e0-7c52-4112-bf09-8feafe21a142",
|
|
|
+ "extensions": {
|
|
|
+ "azuredatastudio": {
|
|
|
+ "views": []
|
|
|
+ }
|
|
|
+ }
|
|
|
}
|
|
|
},
|
|
|
{
|
|
|
@@ -68,7 +79,10 @@
|
|
|
"SET NOCOUNT ON\r\n",
|
|
|
"DECLARE @SQL VARCHAR (8000), @log_reuse_wait tinyint, @log_reuse_wait_desc nvarchar(120), @dbname sysname, @database_id int, @recovery_model_desc varchar (24)\r\n",
|
|
|
"\r\n",
|
|
|
- "DROP TABLE IF EXISTS #CannotTruncateLog_Db\r\n",
|
|
|
+ "if ( OBJECT_id (N'tempdb..#CannotTruncateLog_Db') is not null)\r\n",
|
|
|
+ "BEGIN\r\n",
|
|
|
+ " DROP TABLE #CannotTruncateLog_Db\r\n",
|
|
|
+ "END\r\n",
|
|
|
"\r\n",
|
|
|
"SELECT \r\n",
|
|
|
" sdb.name as DbName, \r\n",
|
|
|
@@ -126,7 +140,7 @@
|
|
|
" BEGIN\r\n",
|
|
|
" select 'Is '+ @recovery_model_desc +' recovery model the intended choice for your database? Review recovery models and determine if you need to change it. https://docs.microsoft.com/sql/relational-databases/backup-restore/recovery-models-sql-server'\r\n",
|
|
|
" select 'To truncate the log consider performing a transaction log backup on database ''' + @dbname+ ''' which is in ' + @recovery_model_desc +' recovery model. Be mindful of any existing log backup chains that could be broken' as Recommendation\r\n",
|
|
|
- " select 'BACKUP LOG [' + @dbname + '] TO DISK = ''some_volume:\\some_folder\' + @dbname + '_LOG.trn''' as BackupLogCommand\r\n",
|
|
|
+ " select 'BACKUP LOG [' + @dbname + '] TO DISK = ''some_volume:\\some_folder\\' + @dbname + '_LOG.trn ''' as BackupLogCommand\r\n",
|
|
|
" END\r\n",
|
|
|
" else if (@log_reuse_wait = 3)\r\n",
|
|
|
" BEGIN\r\n",
|
|
|
@@ -189,7 +203,12 @@
|
|
|
""
|
|
|
],
|
|
|
"metadata": {
|
|
|
- "azdata_cell_guid": "9056554c-ad23-446e-9225-daa19154731a"
|
|
|
+ "azdata_cell_guid": "9056554c-ad23-446e-9225-daa19154731a",
|
|
|
+ "extensions": {
|
|
|
+ "azuredatastudio": {
|
|
|
+ "views": []
|
|
|
+ }
|
|
|
+ }
|
|
|
},
|
|
|
"outputs": [],
|
|
|
"execution_count": null
|
|
|
@@ -212,7 +231,12 @@
|
|
|
"To review the complete backup history of a database, use the following sample script:"
|
|
|
],
|
|
|
"metadata": {
|
|
|
- "azdata_cell_guid": "c9efd682-4795-49c2-96aa-86f064b9ee47"
|
|
|
+ "azdata_cell_guid": "c9efd682-4795-49c2-96aa-86f064b9ee47",
|
|
|
+ "extensions": {
|
|
|
+ "azuredatastudio": {
|
|
|
+ "views": []
|
|
|
+ }
|
|
|
+ }
|
|
|
}
|
|
|
},
|
|
|
{
|
|
|
@@ -244,7 +268,12 @@
|
|
|
"ORDER BY bs.database_name asc, bs.Backup_Start_Date desc;"
|
|
|
],
|
|
|
"metadata": {
|
|
|
- "azdata_cell_guid": "f351810c-19e0-4b39-aa1b-01fced961829"
|
|
|
+ "azdata_cell_guid": "f351810c-19e0-4b39-aa1b-01fced961829",
|
|
|
+ "extensions": {
|
|
|
+ "azuredatastudio": {
|
|
|
+ "views": []
|
|
|
+ }
|
|
|
+ }
|
|
|
},
|
|
|
"outputs": [],
|
|
|
"execution_count": null
|
|
|
@@ -311,7 +340,12 @@
|
|
|
""
|
|
|
],
|
|
|
"metadata": {
|
|
|
- "azdata_cell_guid": "7fdd7c75-6904-4ec1-89c8-459aef29b1bb"
|
|
|
+ "azdata_cell_guid": "7fdd7c75-6904-4ec1-89c8-459aef29b1bb",
|
|
|
+ "extensions": {
|
|
|
+ "azuredatastudio": {
|
|
|
+ "views": []
|
|
|
+ }
|
|
|
+ }
|
|
|
}
|
|
|
},
|
|
|
{
|
|
|
@@ -379,7 +413,12 @@
|
|
|
"END"
|
|
|
],
|
|
|
"metadata": {
|
|
|
- "azdata_cell_guid": "1c9389f3-6389-4bfa-8a96-b57a5fd3a834"
|
|
|
+ "azdata_cell_guid": "1c9389f3-6389-4bfa-8a96-b57a5fd3a834",
|
|
|
+ "extensions": {
|
|
|
+ "azuredatastudio": {
|
|
|
+ "views": []
|
|
|
+ }
|
|
|
+ }
|
|
|
},
|
|
|
"outputs": [],
|
|
|
"execution_count": null
|
|
|
@@ -392,7 +431,12 @@
|
|
|
"Error 9002 can be generated if the transaction log size has been set to an upper limit and autogrow is not allowed. In this case, enabling autogrow or increasing the log size manually can help resolve the issue. Use this T-SQL command to find such log files and follow the recommendations provided:"
|
|
|
],
|
|
|
"metadata": {
|
|
|
- "azdata_cell_guid": "fc76db02-a5b3-406c-8a4c-63aba78b5053"
|
|
|
+ "azdata_cell_guid": "fc76db02-a5b3-406c-8a4c-63aba78b5053",
|
|
|
+ "extensions": {
|
|
|
+ "azuredatastudio": {
|
|
|
+ "views": []
|
|
|
+ }
|
|
|
+ }
|
|
|
}
|
|
|
},
|
|
|
{
|
|
|
@@ -447,7 +491,12 @@
|
|
|
" SELECT 'Found no files that have reached max log file size' as Findings"
|
|
|
],
|
|
|
"metadata": {
|
|
|
- "azdata_cell_guid": "2b57ea05-f10d-46a0-9c4e-ef93e48b5222"
|
|
|
+ "azdata_cell_guid": "2b57ea05-f10d-46a0-9c4e-ef93e48b5222",
|
|
|
+ "extensions": {
|
|
|
+ "azuredatastudio": {
|
|
|
+ "views": []
|
|
|
+ }
|
|
|
+ }
|
|
|
},
|
|
|
"outputs": [],
|
|
|
"execution_count": null
|
|
|
@@ -469,7 +518,12 @@
|
|
|
"In either case, if the current size limit has been reached, increase the MAXSIZE value.</mark>"
|
|
|
],
|
|
|
"metadata": {
|
|
|
- "azdata_cell_guid": "46cf127c-ff3b-48e4-ba77-5fd04cb7a146"
|
|
|
+ "azdata_cell_guid": "46cf127c-ff3b-48e4-ba77-5fd04cb7a146",
|
|
|
+ "extensions": {
|
|
|
+ "azuredatastudio": {
|
|
|
+ "views": []
|
|
|
+ }
|
|
|
+ }
|
|
|
}
|
|
|
}
|
|
|
]
|
