You can set the connection in each query window. Right-click, Connection, Change Connection.

And, in Registered Servers, you can set the connection parameters at the server level.

That way, you only need...

In general, we (a call centre) specify the hours as provided by the contact: "8-5 Eastern time" and let the caller do the math.

Our service accepts incoming calls 8-5 caller's...

In my experience, time zones + DST = no win. We gave up in despair years ago.

It might not be so bad if everyone switched between Standard and Daylight at...

This should get you started

DECLARE @RangeINTEGER = 1000000
DECLARE @RowsINTEGER = (2000000000 / @Range) + 1
--SELECT @nRows
;WITH Num AS-- This will work for ranges > 172. Add another...

Ran into a similar situation some years ago. After trying everything else, we stopped and re-started the SQL Server service and problem solved.

Exceptionally busy next few days coming, but I did rebuild this morning, set a trace, and did check once to find 0.04% fragmentation - not the usual leap to 66.-whatever%...

Confirmed: 0 for index level, In-Row-Data, and trigger generated the expected email for each of an actual Insert, Update and Delete.

FWIW: This is not a end of the world scenario...

So... since the trigger isn't catching it, is my next step Extended Events?

It's coming from Table - Indexes - Reorganize. The underlying source is sys.dm_db_index_physical_stats, I believe.

After load - create index, as well as after rebuild or reorg,  avg_fragmentation_in_percent = 0

So, the trigger has been in place, but has not fired. It's simple: On I/U/D, send me an email with the user_name().

I rebuilt the index on Friday morning, this morning,...

Couple of days later. Wish I had the query handy, but it's on my other workstation, the one with the fried HD from a power blip last Friday. Good thing...

Won't be around for long, methinks.

Also, still on 2008, and XE was not friendly in the slightest back ...er... now 🙂 That said, can't wait to start playing with it...

As mentioned, the index is created post-load.

Thanks for taking the time to respond. Trigger, here I come!

I'll let you know what I find.

Thanks again

P

Ah, I should have been clearer. It is dropped and re-created monthly, populated with 1.8m rows, and then create the index. Within 2 days, the dm tables are showing fragmentation.

Could...

If you have space on prod, restore it to  second DB on prod server, remove unneeded tables/content, then back that up and restore to dev.