Building Databases: One Man’s Best Practice?
One man’s meat is often another man’s poison. In this editorial Tony Davis looks at why a migrations-based approach to database version control might not always be best practice.
2015-09-07
6,262 reads
Database version control
Blogs
Modifying a Trigger to Capture More Info: #SQLNewBlogger
By Steve Jones
I had someone ask me about using triggers to detect changes in their tables....
SQL Server Agent Jobs: Set It and Forget It?
By Kevin3NF
Useful tips to make your jobs more stable Too many IT teams treat SQL...
From SQL Server to PostgreSQL: A Story of 5 Key SQL Differences
After spending decades working in SQL Server, getting familiar with PostgreSQL felt like traveling...
Forums
One big server with multiple instances, or multiple smaller servers...
We're currently on SQL 2019 and will likely be looking to migrate to a...
Transitioning AlwaysOn Availability Group to Synchronous Commit Mode
Hello, I have a SQL Server with an AlwaysOn configuration consisting of three replicas...
CDC & Azure Managed Instances - Performance degredation
Anyone got any good advice for performance tuning CDC on a Managed Instance? We...
Question of the Day
The Trigger Updated Column(s)
In a trigger, I can use UPDATE() or UPDATED_COLUMNS() to determine which columns were changed. For these functions, which one accepts a column name as a parameter?
See possible answers