Bill Dog's Journal: would've never guessed that

Ran into something today. Found the answer:

4. INSERT queries that use SELECT with ORDER BY to populate rows guarantees how identity values are computed but not the order in which the rows are inserted

Mentally masticate on that one for a minute. You carefully craft an ordered query for output to a web page view. But you need to return other resultsets based on it, so you INSERT that SELECT into a table variable, use it to produce your other resultsets, and then finally SELECT from the table var as the last resultset to return.

But then you find your ordered query is ordered, just not your order! Would've never seen that even coming. So I slapped an IDENTITY column on the table var and sorted on it for the final resultset. Whatevs.

Scalability?

[smittyoneeach]

If the task is going to be run in parallel across arbitrary cores, I can foresee where you'd tell teach core to crank out a specific thousand rows, so that the IDs are kosher, but not want to be on the hook for the any storage thereof.

Re: Scalability?

[Bill Dog]

+1 Insightful