sp_RestoreScript 1.6 Release – @Credential Added For Backups In Azure BLOB Storage

Releases seem to be coming out thick and fast at the moment, here's the latest v1.6 revision to sp_restorescript For those of you backing up to Azure BLOB Storage, we've now added a @Credential parameter. You can grab the latest version from our GitHub repo, https://github.com/SQLUndercover/UndercoverToolbox/blob/master/sp_restorescript.sql or for full documentation, visit https://sqlundercover.com/2017/06/29/undercover-toolbox-sp_restorescript-a-painless-way-to-generate-sql-server-database-restore-scripts/

Undercover Catalogue 0.3.0-Auditing and Change Tracking Comes to the Catalogue

We're pleased to announce the release of the Undercover Catalogue 0.3.0. You can grab it from our GitHub page... https://github.com/SQLUndercover/UndercoverToolbox/tree/master/SQLUndercoverCatalogue Installing and Upgrading Full installation and upgrade instructions can be found on the main Catalogue page, https://sqlundercover.com/undercover-catalogue-0-2/ v0.3.0 Brings Auditing to the Catalogue The biggest change that we've introduced to the Catalogue is auditing. All... Continue Reading →

Intent Locks In SQL Server

Intent locks, one of those things in SQL Server that seem to be very often misunderstood. They're something that I've found myself explaining time and time again, I've even been on calls with customer DBAs who don't fully understand why they're there and what they're doing. So what exactly is an intent lock and why... Continue Reading →

sp_RestoreScript v1.4 – It’s Now Compatible with Case Sensitive Collations, Accepts Wild Cards in DB Names and Fixes A bug

sp_RestoreScript 1.4 is now out and ready for download from our GitHub, https://github.com/SQLUndercover/UndercoverToolbox/blob/master/sp_restorescript.sql Full documentation on sp_RestoreScript can be found at https://sqlundercover.com/2017/06/29/undercover-toolbox-sp_restorescript-a-painless-way-to-generate-sql-server-database-restore-scripts/ New Features Compatible with case sensitive collations Now accepts wild cards in the @DatabaseName string, ('Database1,Database2,SQL%') would now be a valid option with % treated as a wildcard. Bug Fixes An issue when... Continue Reading →

Create a website or blog at WordPress.com

Up ↑