Triggers are generally over-used in SQL Server. They are only rarely necessary, can cause performance issues, and are tricky to maintain If you use them, it is best to keep them simple, and have only one operation per trigger. Joe Celko describes a feature of SQL that 'gets complicated fast'.
Technology has made many advances in the world, but it has also eliminated many jobs. This Friday's poll asks how you feel about that as a technology worker.
Aaron Bertrand explains a few details about the memory limits in SQL Server 2016 Service Pack 1 that make this upgrade even more compelling.
How does a column store index compare to a (traditional)row store index with regards to performance
Manvendra Singh takes a look at a SQL Server function that you can use to read the transaction log to see what entries are made for database transactions.
SQL Server 2016 does not allow computed columns to co exist with columnstore indexes and clustered btree indexes on same table.
By Steve Jones
This month we have a new host, Meagan Longoria, who graciously agreed to help...
By Steve Jones
I’m at the UK Redgate office today, meeting with senior leaders in all areas...
Optimizing Azure SQL Database performance often begins with identifying the most resource-intensive queries. Understanding...
When the schema of an object is changed, SQL Server wipes out the previous...
Comments posted to this topic are about the item SSRS Is Dead. Here Are...
Comments posted to this topic are about the item The Distance Metric
In the new VECTOR_DISTANCE() function in SQL Server 2025, the first parameter is the distance_metric. What is this?
See possible answers