3 Solutions For Auditing Long SQL Server Extracts or Loads
In this post, Tim Smith looks at the different options you can use to audit your SQL Server extracts and loads during the ETL process.
A General Way to Maintain History Tables
You will see here a way to handle history tables. This way only takes into account Date-based data cleanup but is easily generalizable.
Backup Preparations
This week Steve asks you to make sure you practice your restore skills periodically.
A Database Design Test
Steve Jones saw a database design test for developers, but he's never been given one.
Export data from SQL Server to Excel
What native SQL Server options are available to export to Excel? Jeremy Kadlec explains.
Handling Data Corruption
This week Steve Jones wonders what you might do if you discovered data corruption.
Scoring Outliers in Non-Normal Data with R
Using R to detect outliers is relatively easy, but most methods assume your data is normally distributed. How do you handle skewed datasets?
Azure Automation Methods
Tim Radney of SQLskills walks through multiple automation methods you can use to manage and maintain your Azure SQL Databases.
Blogs
How to Find Expensive Queries in Amazon Redshift
Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...
The Notification Trap: How Input Fatigue Is Killing Deep Work in Tech
By gbargsley
If you've been here before, you know this blog is usually about SQL Server,...
Designing a Storage Load Test for SQL Server
I’ve been doing storage load tests for SQL Server for a long time, both...
Forums
Make your moments memorable with Fildena 200mg
Make your moments memorable with Fildena 200mg, a high-strength option designed to support men...
How Long is a Long I/O?
Comments posted to this topic are about the item How Long is a Long...
T-SQL Trigonometric Functions in SQL Server
Comments posted to this topic are about the item T-SQL Trigonometric Functions in SQL...
Question of the Day
How Long is a Long I/O?
In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?
See possible answers