Tony Davis

  • Interests: football, modern literature, real ale

SQLServerCentral Editorial

Clustered Indexes? Sedimentary, my dear Watson

There is much sound advice suggesting that every table should have a clustered index, and that narrow, integer, ever-increasing columns, such as afforded by an IDENTITY column are the best choice. But is the sedimentary approach really the natural order of the day?

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(3)

You rated this post out of 5. Change rating

2010-05-24

499 reads

SQLServerCentral Editorial

Double-Entry Bookkeeping for SQL Programmers

All defensive programmers should, in general, avoid unsupported techniques. However, there is a balance to be struck between adherence to 'best practice' approaches to SQL programming, and the need to get the job done. Perhaps certain critical code would benefit from use of the age-old practice of double entry bookkeeping?

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(3)

You rated this post out of 5. Change rating

2010-03-22

1,029 reads

Blogs

Wait… Could This Be the End of Index Maintenance?

By

While attending SQLCon and FabCon Europe in Barcelona, there were a lot of announcements...

Copilot on the Power BI Report Canvas vs. Modern Report Builder

By

(This is the second post in a three-part series on how AI is changing...

The #MS_DatabaseConnector## Role: #SQLNewBlogger

By

I had seen these roles in various instances, but never dug into the new...

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

Packing and Decoding Device Status Codes with LEFT_SHIFT() and RIGHT_SHIFT() in SQL Server

By john.martin

Comments posted to this topic are about the item Packing and Decoding Device Status...

SQL Server Audit Failures

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server Audit Failures

Visit the forum

Question of the Day

SQL Server Audit Failures

If I have a SQL Server Server Audit setup, what are my options for configuring the instance in the event it can't write to the audit log?

See possible answers