Si vis pacem, para sql

Blog Post

Data compression

This post examines the compression of a database named Bankware (BW) at a client site. The database size was 300+ GB. The tests for BW were done on the sk-bankware server...

2015-03-04

6 reads

Blog Post

Database jokes

Sometimes when work is tough you simply need to take your eyes and mind away from your working console. Jokes are one matter that you can take a look on and smile...

2014-07-18

226 reads

Blog Post

Database jokes

Sometimes when work is tough you simply need to take your eyes and mind away from your working console. Jokes are one matter that you can take a look on and smile...

2014-07-18

3 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