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?

4.67 (3)

You rated this post out of 5. Change rating

2010-05-24

450 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.67 (3)

You rated this post out of 5. Change rating

2010-03-22

974 reads

Blogs

From Data Custodian to Innovation Catalyst: The Evolving Role of the CDO

By

There was a time when the Chief Data Officer lived in the shadows of...

Down the Rabbit Hole: Dealing with Ad-Hoc Data Requests

By

"But I don’t want to go among mad people," Alice remarked."Oh, you can’t help...

Adding a Local Model to Ollama through the GUI

By

I saw some good reviews of the small gemma3 model in a few places...

Read the latest Blogs

Forums

Create an HTML Report on the Status of SQL Server Agent Jobs

By Nisarg Upadhyay

Comments posted to this topic are about the item Create an HTML Report on...

We Should Demand Better

By Steve Jones - SSC Editor

Comments posted to this topic are about the item We Should Demand Better

Estimated Rows

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Estimated Rows

Visit the forum

Question of the Day

Estimated Rows

I have two calls to the GENERATE_SERIES TVF in this code:

SELECT   TOP 10 gs.value
FROM     GENERATE_SERIES(1, 10) AS gs
ORDER BY NEWID ()
OPTION (RECOMPILE);
go
DECLARE @a int = 10;
SELECT   TOP (@a) gs.value
FROM     GENERATE_SERIES(1, @a) AS gs
ORDER BY NEWID ()
OPTION (RECOMPILE);
In the actual query plans, what is the estimated number of rows for each batch?

See possible answers