Viewing 15 posts - 31 through 45 (of 59,067 total)
I can't see any of the comments that were posted according to the discussion pages near the bottom of the article,
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2026 at 6:18 pm
the reason why the code was removed (post deleted really) is because since sometime ago any post that contains 2 URL's gets that treatment. there is no error, just...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2026 at 3:45 am
I hope I'm not too late... simple conversions of DATETIMEOFFSET(7) to DATETIME will cause rounding up to the next unit of time once out of every 600 times... and that...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2026 at 3:27 am
The timing is less than ideal but that 21 years means I'm going to get quite a significant payout. By my calculations, after tax it's a year's money so...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2026 at 2:29 am
Hard lessons in the past (especially for but not limited to SQL Server 2012) have "helped" me understand not to trust Microsoft for at least a year (and sometimes more)...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2025 at 2:54 pm
Like Granny used to say, "The faster they move, the behinder they get".
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2025 at 5:00 pm
I did that for the SQL Saturday in Kalamazoo, MI in 2013. I did a take on "Strolling through the park" to introduce my session on how to safely use...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2025 at 6:36 pm
Too funny that people have given something like this a name. The problem has been brought to us by all the people the preach things like DONE > Perfection but...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2025 at 8:36 pm
If only...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2025 at 11:49 pm
My biggest concern is people using it to do the things they don't know anything about.
A couple of recent examples that I've come up with are to ask AI 1)...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2025 at 5:31 am
As for the old table, you were going to delete all but a million rows. When you're sure the copy worked correctly, just drop the old table.
Also, decide the maximum...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2025 at 7:52 pm
I also read about using 'SWITCH' to map the data to the backup table, then insert the records back into the original table. Once the data dump is done,...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2025 at 7:45 pm
If you're going to remove 25% or more of the data from a HEAP or a Table (Clustered Index Present), the best thing to do all the way around is...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2025 at 6:32 pm
Good article. Thanks for taking the time to write it up.
What I'd like to see is...
You have a database that has a partitioned table. The partitioned table has 1 filegroup...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2025 at 6:06 pm
This is a classic problem with where to start counting. It's compounded by the fact that when people generate the code for modification, it frequently adds a blank line above...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2025 at 11:12 pm
Viewing 15 posts - 31 through 45 (of 59,067 total)