Caution about Restoring via SSMS v17
A default value has changed in the SSMS v7 restore wizard, and the consequences can be severe.
2018-11-06
1,923 reads
Warren Campbell
Automated Rapid Recovery during Database Code Releases using Snapshots
Leveraging snapshots across multiple databases simultaneously to allow for quick rollback in case of a problem deploying code
2015-12-08
2,169 reads
Automating Daily Checks with Powershell
Using Powershell to create color coded backup reports for all servers in your environment.
2011-12-19
14,194 reads
Automatically Scripting Out Permissions for Cross Environment Restores
This article from Warren Campbell shows a process to recreate permissions in development environments after restoring a database from a production instance.
2011-12-05
8,046 reads
Blogs
Keeping Redshift System Table History Past 7 Days with S3 Tables
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
Updating the Data API Builder
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
T-SQL Tuesday #202 Invitation: That One SQL Server Outage You’ll Never Forget
I am excited to host T-SQL Tuesday for the first time. I want to...
Forums
Practical Ways to Approach SQL Server Problems and Case Studies
Working with SQL Server can involve more than just writing queries. Understanding database design,...
Measuring Productivity
Comments posted to this topic are about the item Measuring Productivity
Importing Excel files into SQL Server using DuckDB and Python
Comments posted to this topic are about the item Importing Excel files into SQL...
Question of the Day
Tracking All the Queries
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers