|
|
-
|
|
Any maintenance activity requires some amount of dedicated resources. SQL Server uses locks to reserve resources for a particular task and maintain isolation between transactions. Answer this simple question regarding locks and index maintenance in SQL Server databases to win up to two (2) Pluralsight training codes!...
|
|
-
|
|
Do you know which SQL Server database does not follow one of the ACID properties - Atomicity, Consistency, Isolation and Durability? Read this post to know why tempdb does not follow ACID properties....
|
|
-
|
|
Any database should follow a certain set of properties, collectively called ACID properties - Atomicity, Consistency, Isolation and Durability. Answer this simple question regarding ACID properties and SQL Server databases to win up to two (2) Pluralsight training codes!...
|
|
-
|
|
The ROWVERSION column is an auto-incrementing number. The MIN_ACTIVE_ROWVERSION() non-deterministic function can be used to fetch the lowest active ROWVERSION value in the current database....
|
|
-
|
|
It is a myth that the ROWVERSION column holds a unique value across a database. In this post, I demonstrate that a possibility exists for having duplicate values in a ROWVERSION column when using Bulk-Insert operations (SELECT…INTO)...
|
|
-
|
|
It’s a common misconception amongst the novice SQL Server community that ROWVERSION is just a different name for the erstwhile TIMESTAMP. This is not the case – ROWVERSION is an improvement over TIMESTAMP, and one of the key differences is in the way in which they are used when defining tables. Today, we look at this DDL difference between – TIMESTAMP and ROWVERSION....
|
|
-
|
|
Working with the Profiler helps one learn SQL Server internals in a much better way. This post is based on a question I received in the ASK module of BeyondRelational.com regarding why we don't generally see parameter values in the "SQL:StmtCompleted" events....
|
|
-
|
|
One of the most common mistakes that all developers make is to pass parameters to a procedure based on the expected (ordinal) position and not the expected parameter name. Can you change the parameter sequence within your stored procedure without breaking the calling code?...
|
|
-
|
|
Have you ever worked on troubleshooting an issue for hours (or maybe days) at an end only to find that somebody else from the team has either faced the issue before or could have helped you with just 10 minutes of their time? This post is based on a real-life incident and is a lesson to all teams that peer reviews do help in resolving problems quickly....
|
|
-
|
|
In a rare case when you need to control the execution sequence of database triggers, you can use the sp_settriggerorder statement to do so. However, the recommended best practice always remains that you should have business logic dependent upon execution sequence within stored procedures....
|
|