Viewing 15 posts - 31 through 45 (of 59,063 total)
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
Let me understand this clearly... an "intern" had the privs to bring a production database down?
Seriously???
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2025 at 7:29 pm
I think opinions are great for the same reasons as you, Grant. Just not when it comes to things like code. I've seen way too many things that turned out...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 19, 2025 at 10:55 pm
Oz-860645 was happy to come here for a quick answer but then says "Nevermind, I figured it out." and disappeared.
When I created the synonym I did it without the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2025 at 6:49 pm
Sorry I'm lat on this thread and I may have missed it but no one is talking about the licensing costs of the SQL Server on the separate machine.
Also, did...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2025 at 5:38 pm
When you want it 100% correct, you should use ORIGINAL_LOGIN().
Especially when, IMHO, people use that nasty little word of "audit" like they did in this question.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2025 at 1:40 am
This can be done by creating database level triggers and can seriously be enhanced in capturing not only what changed when but by who from where.
I can't offer the code...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 17, 2025 at 5:30 am
i have a database with 400 stored porcedure , i need to optimise it , i found that tables are not having command index also.
like joins where ,group by...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2025 at 8:14 pm
Great question. Proof that extra features always come at a price. 😀
It also means more page splits than normal due to "ExpAnsive" UPDATEs because of the typical extra 4 bytes...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2025 at 6:19 pm
Btw, I disagree with those who suggest to always specify the windowing range. The default is ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW. Why repeat it? The best part...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2025 at 3:12 am
Viewing 15 posts - 31 through 45 (of 59,063 total)