Hey Rod. First guess, have you poked a hole in the firewall so your account can get to the Azure database? That's the most common issue. You should be able...

I'm with Ken. Temporal tables is probably the better solution. However, you also can look at setting up an UPDATE trigger as shown at the link. Be cautious and...

The...

Also, a Common Table Expression, CTE, is not a TABLE, but an EXPRESSION. That label causes so many problems for so many people. You're not defining a temporary storage space....

I'm with everyone else. To help you, we need to see code & structures. However, a couple of points.

If you're seeing 3000% usage, I know two things. First, you're using...

When a backup starts, a marker is placed in the transaction log. Any transactions that are completed when the backup is done, are then backed up. Any transactions that are...

No plans to update the execution plans book at...

Nah, just the 3rd edition. It's updated & cleaned up. The others are out of date, wrong, or unclear.

'

Yeah. Fixed it.

You could also define the SELECT statement of the view so that it masks the data actively as the query runs. Just and idea.

That's not a temporary table (I mean, it's temporary and it's a table, but it's not what SQL Server defines as a temporary table). That is a table variable. Table...

Sounds like you're looking at how GROUP BY works. Combine that with MAX() and COUNT() and you should be good to go. I'm guessing the column you...

These counters, by themselves, won't necessarily show a bottleneck. You need to capture the metrics over time so you have comparison points (x% yesterday, y% today, look, it's getting worse)....

While SQL Server itself doesn't capture metrics about timeouts, the windows OS does. Extended Events can actually capture this with a debug event (these are subject to change without notice,...

Jeff is so very right.

Columnstore is magic... until it isn't. It really comes down to what kind of queries you're running most of.