2020-02-19 (first published: 2019-03-14)
471 reads
Editorial
Badly Encrypted Databases
Database encryption is hard, and somewhat controversial. Steve thinks we ought to do a better job of it.
2019-03-13
75 reads
Dealing with Technical Debt
Technical debt can cripple software development, much like financial debt hurts individuals and organizations. Steve wants to know if you measure your debt today.
2019-03-12
106 reads
Who should have Sysadmin rights?
The point of this article is that only service accounts and/or specific network sql admin accounts should have sysadmin rights.
2019-03-11
1,552 reads
Microservice Reality
Phil Factor argues that very few processes, even in well-established businesses, mimic the dreamy clarity and autonomy of a microservice.
2019-03-11
156 reads
Databasee Brainstorming
We sometimes need to think differently about different situations. Steve notes that we might approach the way we solve problems in new ways.
2019-03-08
181 reads
2019-03-07
100 reads
The Data Incident
Google and Microsoft have plans for dealing with data incidents. Steve thinks you should as well.
2019-03-06
74 reads
The Creepiness of AI
It seems that many companies are implementing AI into their systems. Steve notes that this isn't always a good idea.
2019-03-05
87 reads
2019-03-04
105 reads
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