Security Shaming
This week Steve Jones looks at a new idea, rating the security of products publicly to try and shame vendors into more secure coding.
This week Steve Jones looks at a new idea, rating the security of products publicly to try and shame vendors into more secure coding.
Too many failovers can cause problems, as can those that happen to often. Steve Jones says you need to consider whether you always need to failover in a sitaution.
This article compares SELECT INTO and INSERT INTO under different scenarios, and the best approach preferred.
So often, the unexpected delays in delivering database code are more likely to happen after the developers initiate the release process. The necessary checks and tests can turn up surprises: The handover process can expose deficiencies. With good teamwork, planning and forethought, though, the process can be made almost painless.
As database developers, we may need to rethink the way we store and handle personal names
In this latest T-SQL Tuesday, Rob Farley takes a look at a couple of unexpected aspects of query plans you might observe when using Temporal Tables in SQL Server 2016.
Daniel Calbimonte walks through the steps to creating a SQL Server Reporting Services (SSRS) Report from an Analysis Services Tabular Database.
A how-to guide for configuring replication agents after a password change
Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...
By Steve Jones
I don’t have SQL Server installed on my laptop. In an effort to keep...
Comments posted to this topic are about the item Increase Deadlock Detection
Comments posted to this topic are about the item A Tool is Better than...
Comments posted to this topic are about the item Understanding Deadlock Victim Selection in...
How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?
See possible answers