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
One of the things a customer asked recently about Redgate Data Modeler was how...
By HeyMo0sh
Cloud environments don’t sit still. Pricing models change, services evolve, workloads grow, and suddenly...
Are you considering replatforming your SQL Server workload due to recent vendor changes, but...
Comments posted to this topic are about the item Removing TDE
Comments posted to this topic are about the item The day-to-day pressures of a...
How do I remove TDE encryption of data from database xxx?
See possible answers