Viewing 15 posts - 2,986 through 3,000 (of 59,098 total)
Ed, what's your take on using Column Store for column-oriented (they record the entity and the column that changed as well as the "OldValue" and the "NewValue {big mistake on...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 10:49 pm
Bruin wrote:Is there a script that will report savings for Page Compression?
Thanks.
yes - its called "read the manual"
Sometimes, that's difficult because a lot of technical manuals aren't...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 7:21 pm
Now, I don't want to hijack this thread into EF tuning... but there are code smells in LINQ just like there are in T-SQL. My pet peeve is join...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 7:16 pm
So.. just to be sure from your example data...
101 has never been changed.
102 was replaced by 103 which was replaced by 104.
Is that correct?
If so, a hierarchical recursive CTE (rCTE)...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 7:07 pm
For me and just IMHO...
If it's a brand new database, I like to deploy using a restore.
If it's updates to a previously deployed database, then I like scripts because you...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 6:59 pm
The best way is to not read the same area of the table that he's writing to. It's also important that his "loading" should be fast. Some will suggest the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 6:39 pm
p.s. If the table isn't too wide, consider the use of a "System Versioned Temporal Table" which is all of that done auto-magically for you.
https://docs.microsoft.com/en-us/sql/relational-databases/tables/temporal-tables
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 6:33 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 6:30 pm
Thank you Kaj, that was a great and easy trick.
Thank you so much!
The method Kaj wrote about is call a "CROSS TAB". You can read more about how it...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 6:22 pm
The table structures are identical across the estate, so I had wondered if they could - or should - be consolidated somehow.
Possibly a Partitioned View. If it's across servers,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 6:16 pm
So that means that the application could be modified to look in a different database for a different table, then... correct?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 6:08 pm
Is there a script that will report savings for Page Compression?
Thanks.
Better than that, there's a system stored procedure that will estimate the savings as bytes before'n'after. You can find...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 6:04 pm
Bruin wrote:Is there a script that will report savings for Page Compression?
Thanks.
yes - its called "read the manual"
Sometimes, that's difficult because a lot of technical manuals aren't written for...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 6:01 pm
Thanks...
The monthly tables are queried often..
Ok... how are people doing that when there's one table per month? Are you already using partitioning and, if so, what kind?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 5:58 pm
That certainly a possibility. That's more of a "bridge" table. I don't know what else you're trying to track, though.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2022 at 3:12 am
Viewing 15 posts - 2,986 through 3,000 (of 59,098 total)