"Bump" to make the 2nd page of the discussion show up.

The greatest technical debt I have ever experienced is when we migrated from SQL Server 2016 to 2022.  That means that I'm still experiencing that "joy".  Overall, "It just runs...

Jeff - I'm going with Scotts recommendation which sticks with CAST and not FORMAT.  That said, just out of curiosity do you know how much data/rows need to be...

Heh.. "next time".  You're saying that because someone already did it but... they did...

You're not going to use this data as points in time, but as intervals, so model it that way

Create table events (event_number integer not null primary key, event_start_timestamp dateime2(0)...

{sarcasm on}

WHAT??? AI LIED??? Surely, you jest!  It's going to take over all our jobs, right?  RIGHT? 😉

{sarcasm off (for the moment)}

If you use FORMAT anyplace where there are a lot of rows, I can only wish you luck for performance because you're going to need it.

No, this is...

No.  Absolutely not.  It...

I don't know if it would be possible to write reports using Jupyter Notebooks, that would be canned reports accepting only parameters, such as start and end dates....

I'm confused.... the log file name of your latest graphic doesn't appear to match or relate to any database names in your first graphic.  You've also not said anything about...

Please see the article at the first link in my signature line below.  Most of us like to test our answers before we publish them.  For that, we need "Readily...

Only 17 responses on Steve Rezhener's thread.  I'm not sure that I'd consider that to be a viable source of information considering the previous and expected attendance for these types...

I don't believe such an alert exists.  My recommendation would be to make an SQL Server Agent Job that checks for such things and schedule it to run on a...

To be honest, I've found that most such contention is because of what is appropriately referred to as "crap code". 😉

I recommend that you figure out what's beating on TempDB...