Erland Sommarskog asked me about this in May 2022.
It's a bug exposed when a predicate is pushed down into the internal streaming table-valued function. The return type is indeed datetime2(7) but the source is a Windows FILETIME.
The predicate is pushed down below the internal conversion, so the ...
I mean they gotta be aware of the bug if the documentation example has the workaround
See this edit for an example: a four years old question contains a link to the then-current documentation. The world has moved on since, and someone changes the old link to point to the new documentation instead. Is this appropriate? Would it be better to leave the old link alone (provided it's s...
I find some of the ways people use logic on this site quite odd. A person asks a question on the internet. Rando answers question. Person says they don't believe them because another Rando said something else. So they both believe and don't believe? I don't get it.
Everyone starts from some basis for evaluating truth, and the goal needs to be to make that stronger and stronger so people can critical synthesize new information properly. My worry is not the ChatGPT produces wrong answers just like people, but that people are not thinking about the costs of evaluating its output just like you would any work product coming in from a first-time employee or whatever.
So you can safely accept what's good and discard what isn't. (And also decide to stop using it if the cost of using its output is excessive because it causes liability or usability or cleanup effort or whatever).
@CadeRoux Well most of the people I work with ask the internet anyway and many of the kids just go on the web to ask it to do their homework... so really whomever controls that controls the "truth"
I wonder if you end up having to edit ChatGPT instead of your own first draft, do you really save time and effort over all? There is the need to read and process someone else's work and critically analyze it. That's still a significant cognitive load.
--Controls how sleeping SPIDs are handled, based on the idea of levels of interest
--0 does not pull any sleeping SPIDs
--1 pulls only those sleeping SPIDs that also have an open transaction
--2 pulls all sleeping SPIDs
Speaking of WIA, is the wait_info column still updated / valid for a process that's being rolled back or in that case is it something like the last wait before the process was rolled back?
SQL will freeze for about 5 to 15 seconds. There are a couple of errors I see but the following is the most frequent. Any suggestions?
SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: Accep...
I'd guess blocking off the top of my head. The vendor probably has never heard of optimistic concurrency, indexing, or load testing at Internet scale, lol.
So I've been looking for a good way to automatically correlate the User who made the change to the history in a Temporal Table's history table. I found adding a computed column to the source table using the SUSER_NAME() function does persist the correct User to the history table of whoever executed the DML statement.
Yes the schema of the history table needs to match, so I added it to both (not computed in the history table, just the name and proper data type). But my plan would be to add this computed column to the source table prior to enabling it as a Temporal Table, actually at the same time I add the ValidFrom and ValidTo columns, so the auto-generated history table already has the proper schema.