Before getting into the details, I need to make one thing clear. Nested transactions are a lie. They do not exist in SQL Server.
This is part 1 of a three-part series by Gail Shaw. Read the whole thing. Also read Paul Randal:
Nested transactions do not actually behave the way the syntax would have you believe. I have no idea why they were coded this way in SQL Server – all I can think of is someone from the dim and distant past is continually thumbing their nose at the SQL Server community and going “ha – fooled you!!”.
Nested transactions are somebody’s attempt at trolling. They succeeded.
Does this mean there will be no 32-bit version of SQL Server 2016? They may make some desktop version; I don’t know nor have I been following. But as a Server product? RIP, and good riddance.
So you can thank (or damn) me for this one. Me, I’m going to celebrate. Where’s my bottle of Coca Cola with real sugar?
Allan Hirt, I thank you. I have one 32-bit device left: it’s a cheap tablet. Let’s not wait until 2038 to get rid of x86.
Bad news. The error message is the same.
Working within Azure SQL Database, trace flags are not a part of your tool set.
Everything with Azure needs a timestamp. Come back in a year and this may be different.
Do indexes (clustered or non-clustered) define the physical storage order of the rows?
No, absolutely not.
What indexes do is provide a logical ordering, a collection of pointers, that allow the storage engine to retrieve data from an index ordered by the index key, but that’s logical ordering, it specified nothing regarding the physical ordering.
Read the whole thing.
Curated SQL is a simple premise: act as a clearinghouse for high-quality SQL Server material. Basically, we want to distill the tremendous number of articles and blog posts and make it easy for you to find the best of the web. This is a curated site, so all posts are lovingly hand-crafted, with nary a bot to be found.