2018-12-18
48 reads
2018-12-18
48 reads
Phil Factor explains the enduring attachment of database developers to wildcards, despite their current deficiencies.
2025-03-17 (first published: 2018-12-17)
470 reads
Table variables have been fixed in SQL 2019, so now I have to decide if I will use them again.
2024-07-26 (first published: 2018-12-11)
326 reads
A new law in Australia might be a source for the worst data breeches we could have.
2018-12-10
76 reads
2018-12-07
82 reads
2020-01-28 (first published: 2018-12-06)
623 reads
Data breaches do more than harm an organization. There's a human cost.
2018-12-05
90 reads
2018-12-04
71 reads
File systems and document databases are the wild lands of data privacy. Phil Factor explains the value of JSON Schema in adding provenance to your document data.
2018-12-03
368 reads
2018-12-03
52 reads
By Chris Yates
There was a time when the Chief Data Officer lived in the shadows of...
By Rayis Imayev
"But I don’t want to go among mad people," Alice remarked."Oh, you can’t help...
By Steve Jones
I saw some good reviews of the small gemma3 model in a few places...
Comments posted to this topic are about the item Create an HTML Report on...
Comments posted to this topic are about the item We Should Demand Better
Comments posted to this topic are about the item 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