Viewing 15 posts - 5,011 through 5,025 (of 59,089 total)
While a Calendar table will certainly work, a little (and I do mean very little) math can be used to solve this problem. Case in point...
--===== Create...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2021 at 9:02 pm
For a stand-alone, nonclustered index with just that column in it, REBUILD that index setting the FREESPACE to 50[%]. That will delay any fragmentation for some amount of time,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2021 at 10:20 pm
I've experienced the random GUID-"problem" upclose in other tables. Index is 98-99% fragmented just a few hours after a defragjob has completed. There's frequent INSERT and DELETE in that...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2021 at 10:11 pm
YES!
"Nice to have: 2k years experience with DBCC TIMEWARP()."
And then sit back and see how many people actually respond. @=)
BWWWWWWAAAAA-HAAAAAA-HAAAAAA!!!!
That made my whole week! Thanks for the great laugh!!!
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2021 at 5:23 pm
Ah... sorry... you're asking for when it was stopped. Might be a different lookup so I withdrew my previous post.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2021 at 7:54 pm
Yes... Most have seen it happen many times before. There are a thousand different causes of a few reasons that can usually be explained by an actual execution plan. Any...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2021 at 7:41 pm
We manage SQL Server data in a growing environment where our One of the most popular archiving techniques with data that includes date and can be scaled early as...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2021 at 7:22 pm
Fragmentation associated with Random GUIDs is a complete MYTH based on improper testing, misinformation, and the use of supposed "Best Practices" for index maintenance that are actually "Worst Practices" and...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2021 at 7:13 pm
DELETE FROM dbo.Table WHERE ID IN (12); ... With the temporal table, deadlocks are guaranteed every time. Only one of the deletions will succeed; the rest will...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2021 at 5:46 pm
Is the table clustered on ID?
Have you got any other indexes on the table?
Have you looked at the execution plan?
Oh lordy... I posted before having enough coffee. This is...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2021 at 5:06 pm
Instead of having multiple connections trying to delete one or two rows at a time from all over hell's little half acre in the table, remember that it's a TEMPORAL...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2021 at 4:32 pm
Shifting gears to another aspect to employment, I'd say "and so it begins" except that it's been this way for a long time. It's just getting worse. If you have...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2021 at 4:17 am
Heh... ah... I know what you mean now. No comment. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2021 at 3:40 am
I "love" some of the ads I've seen... they start with needing only 2 years of experience but want a full stack developer that is also an expert...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2021 at 3:37 am
My pleasure and thank you for the feedback. xp_LoginInfo is one of those tools that I don't need to use often but it's a real life saver when I do...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2021 at 3:34 am
Viewing 15 posts - 5,011 through 5,025 (of 59,089 total)