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.
SQL Server 2016 brings native support to advanced analytics in the database itself, using R Services. In this article, Arshad Ali explains what R is, what the on-premise advanced analytics options from Microsoft are, and shows how to get started using R Services with SQL Server 2016.
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Comments posted to this topic are about the item Multiple Deployment Processes
Comments posted to this topic are about the item How to Use sqlpackage to...
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers