External Article

Finding a better candidate for your clustered indexes

When creating tables it is difficult to determine exactly how the data will be accessed. Therefore when clustered indexes are chosen they are often just the ID column that makes the row unique. This may be a good choice, but once the application has been used and data access statistics are available you may need to go back and make some adjustments to your tables to ensure your clustered indexes are providing a benefit and not a drain on your applications.

Blogs

How to Connect to SQL Server When Nothing Else Works – DAC

By

It's 2 AM. Your phone is going off. Users can't connect to the application,...

Get a Range of Sequence Values: #SQLNewBlogger

By

I discovered a procedure recently that I wasn’t aware of: sp_sequence_get_range. This post looks...

The Agent Era: When “How do I…?” Replaces “Where do I click?”

By

After a year away getting to grips with AI and its application across the...

Read the latest Blogs

Forums

Detecting Deadlocks

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Detecting Deadlocks

setting an ssis param dynamicaly when the sql agent job runs

By stan

hi i was hoping for a more elegant way of setting a pkg level...

Query compile/runtime issue

By as_1234

I have a plan which in sys.query_store_plan shows: Last_compile_start_time of 2026-04-23 00:13:00.7670000 +00:00 Last_execution_time...

Visit the forum

Question of the Day

Detecting Deadlocks

By default, how often is the SQL Server Database Engine checking for deadlocks?

See possible answers