Blocking occurs in SQL Server 2005 when one process has one or more records locked, while another process tries to acquire locks on the same set (or subset) of records. This can create a daisy-chain of processes waiting to complete their work.
A look at how you can implement error handling in your stored procedures.
Indexing a SQL Server database in some respects is considered both an art and a science. Since this is the case, what are some considerations when designing indexes for a new database or an existing one in production? Are these the same types of steps or not? Do any best practices really exist when it comes to indexing? Where does indexing fall in the priority list from an application or production support perspective?
What changes are coming in the editions for SQL Server 2008. Steve Jones finds a rather scary piece of literature.
Understanding the types of tables available in SQL Server can greatly enhance your database development experience.
An article that speaks about some of the issues faced by the Author, during his Data Integration Project using SSIS. Shared with you in this article are the issues he was faced with and the solutions applied.
I am excited to host T-SQL Tuesday for the first time. I want to...
By Steve Jones
Redgate had some Claude training recently, which I went through as my knowledge has...
By Steve Jones
gnossienne– n. the awareness that someone you’ve known for years still has a private...
Comments posted to this topic are about the item Measuring Productivity
Comments posted to this topic are about the item Importing Excel files into SQL...
Comments posted to this topic are about the item Tracking All the Queries
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers