@ErikDarling Yeah, weird. I could have sworn that SSMS has yelled at me about that before, but maybe I'm just thinking of SELECT statements.
@ErikDarling Haha right. I guess I don't know what it means for the connection to not be available. I got this right before that error, so the connection was, indeed, busted. The messaging is just weird.
> A transport-level error has occurred when receiving results from the server. (provider: Session Provider, error: 19 - Physical connection is not usable)
It's certainly not ideal, but as I say, complicated
Things fight sometimes, and it depends what happens in what order
For example, scalar computations are pushed down to enable computed column and index matching. Filters are also pushed down. They can't both be at the bottom.
Of course, it could do both and cost the choice, but these things happen v early, before CBO (which may not happen at all for simple queries)
i didn't notice until i was testing repeatable read and serializable and getting deadlocks, and thought the late filter may have been involved (it wasn't, of course)
> Currency or monetary data does not need to be enclosed in single quotation marks ( ' ). It is important to remember that while you can specify monetary values preceded by a currency symbol, SQL Server does not store any currency information associated with the symbol, it only stores the numeric value.
The currency sign ¤ is a character used to denote an unspecified currency. It can be described as a circle the size of a lowercase character with four short radiating arms at 45° (NE), 135° (SE), 225° (SW) and 315° (NW). It is raised slightly above the baseline. The character is sometimes called scarab.: 5
== History ==
The symbol was first encoded for computers in 1972, as a placeholder for national currency symbols such as the dollar sign, in national variants (ISO 646) of ASCII and the International Reference Variant. It was proposed by Italy as an alternative (to the dollar sign) at 0x24...
Someone attempted to standardise
Imagine I pasted the normal xkcd
There is also a little comedy value in taking people seriously when they weren't
There was one that came in recently that we got called into and they basically DOS'd themselves with connections. Their logic was if it didn't immediately work, create a new connection and do the same thing.
but yes TempDB not having in memory options is the cost of running in the cloud
> Unfortunately, common ways of shutting down SQL Server 2012 do not currently automatically checkpoint databases (this contradicts the documentation, so it should be fixed at some point in the future).