A far better method would be to write a trigger to do the copy to the history table.  Make sure you write it to handle more than one row at...

The method Kaj wrote about is call a "CROSS TAB".  You can read more about how it...

Possibly a Partitioned View.  If it's across servers,...

So that means that the application could be modified to look in a different database for a different table, then... correct?

Better than that, there's a system stored procedure that will estimate the savings as bytes before'n'after.  You can find...

Sometimes, that's difficult because a lot of technical manuals aren't written for...

Ok... how are people doing that when there's one table per month?  Are you already using partitioning and, if so, what kind?

That certainly a possibility.  That's more of a "bridge" table.  I don't know what else you're trying to track, though.

I have a 1.3 terabyte database and growing, in which 1 table a month collects all of the new data... The process is collecting machine data and creates a...

How do you intend to track "transactions"?  I seem to be that the operator gets a "batch" of fuel and then the operator give that fuel to a single machine. ...

Ok... I believe I've got it this time.  To summarize, the code solves the problem of NULLs being returned in the "Lag'n'Lead" columns if there is data outside of the...

My rub on the subject is concerning portable devices.  It's not like people religiously change the timezone on their machine and what does datetimeoffset in EF use as a reference...

p.s. I'm thinking that the LAST_VALUE and FIRST_VALUE functions may be a better choice here.  I'll give that a try.

EDIT:  I just tried them...  Prior to SQL Server 2022, LAST_VALUE...

Crud... just not having a good week here.  I just found a bug in my code and had to take it down. 🙁

My point is that deciding to use a DATETIME2 and only storing UTC dates/times only without also storing the time zone offset or time zone information is inherently a...