Future Proofing an IT Career
Steve discusses the ways that you can ensure your IT career continues to move forward.
How much database normalization is enough?
Normalization is important for relational databases, but sometimes too much of a good thing can be bad.
Upgrade From SQL 2012 to SQL 2016 - Problem with Certificates
You may need to drop and recreate your certificates after migrating from SQL 2012 to SQL 2016+
How to be Accountable for Handling Personal Data
The GDPR is in full effect but meeting the requirements may still be confusing for many companies. In this article, William Brewer discusses what is needed to ensure compliance, including when a Data Protection Impact Assessment is required. He also explains the Data Protection Officer role.
How to change an Azure SQL Database Collation
In this tip we look at the steps you can follow to change the collation for an Azure SQL Database.
SQL Server Migration
Some SQL migrations require keeping the server name, instance name, IP, and port number. Geoff Ruble shares some notes on his recent experience with a SQL Server migration.
The Challenge of Failure and of Being Unwired
About to embark on a vacation, Steve talks about the difficulty in letting go.
Segment Data into Deciles
This short article shows a simple example of how to segment data into deciles
Blogs
Programmatically Retrieving MLV Lineage and Refresh Times
Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...
Upgrading SQL Server Containers on the Laptop
By Steve Jones
I don’t have SQL Server installed on my laptop. In an effort to keep...
Forums
Increase Deadlock Detection
Comments posted to this topic are about the item Increase Deadlock Detection
A Tool is Better than a Script
Comments posted to this topic are about the item A Tool is Better than...
Understanding Deadlock Victim Selection in SQL Server
Comments posted to this topic are about the item Understanding Deadlock Victim Selection in...
Question of the Day
Increase Deadlock Detection
How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?
See possible answers