Yeah, I realized if I join this with the ens_message.header table I get the "source" and "target" configs and they differ which makes more sense.

Thanks for confirming what I'm seeing though.

Wait, I think I understand now.  In the second query, >8:01 is what I actually want since it was currently 9:01.  FirstDate is stored in UTC but my client is automatically adjusting, so it works when I compare it to UTC.  The local value for "OnlyAfterThisDate" isn't adjusted when displayed.

I'm not sure I'm verbalizing it correctly, but I think I do understand now.

Added a new top level comment since this thread is getting tight.  I'd love to see your thoughts.

This might better explain what I'm seeing or not understanding:

SELECT DATEADD(hh, -1, GETDATE()) as OnlyAfterThisDate, MIN(TimeCreated) as FirstDate, MAX(TimeCreated) as LastDate FROM ens.messageheader WHERE TimeCreated > DATEADD(hh, -1, GETDATE());

SELECT DATEADD(hh, -1, GETUTCDATE()) as OnlyAfterThisDate, MIN(TimeCreated) as FirstDate, MAX(TimeCreated) as LastDate FROM ens.messageheader WHERE TimeCreated > DATEADD(hh, -1, GETUTCDATE());

Changing my queries to GETUTCDATE() did seem to fix the issue but I still don't understand why.   ¯\_(ツ)_/¯

I don't see this option in DBVisualizer.

I'm not exactly sure what you're asking, but this is the definition in the ens.messageheaderbase class:

Property TimeCreated As Ens.DataType.UTC

I was referring to our local documentation.  I can't find the reference document.  Perhaps it's a version difference.

Is the "Newest" sorting issue the same cause?  Or are you at least aware of it too?

I'll try to restrain myself :)