Viewing 15 posts - 166 through 180 (of 59,101 total)
Reviving 10 year old zombie threads should probably be a no-no.
If it provides a good answer, especially a more effective good answer, I don't mind. It'll help others when...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2025 at 9:53 pm
@jeff - a lot of this rings true with me and this situation. My real challenge is how do I move forward. Should I update the stats for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2025 at 10:19 pm
We rebuilt a bunch of indexes that had avg_fragmentation_in_percent>30.
This will sound odd but you probably won't get much useful data from the deadlock data other than you're now suffering...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2025 at 5:18 pm
Yes well noted and conveyed the same to business and application owners. They are well are of the repercussions and will take a call on this. Thank you all...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2025 at 3:47 pm
Thank you, have you managed to get past the performance issues as a result of the version upgrade? Do you possibly have any links you can share on why...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2025 at 3:39 pm
The error is telling you what is wrong. Also, if you go to the KB article, it will also tell you what is wrong. It's saying that the instances where...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2025 at 1:56 am
I just want them to fix the serious performance problems that started in 2019 and they've done (apparently) nothing to fix even up 'til today for SQL Server 2022. 🙁
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2025 at 2:01 am
Yes... but it won't help... Stand up your 2022 server and do some restores and then do test runs against your old server and the new one. The tests should...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2025 at 6:49 pm
Heh... and people wonder why such a thing won't stand up in court. Ant-Green is spot on!
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2025 at 11:42 pm
I appreciate your honest replies and your professionalism in wanting to help others as you learn. That's pretty much the spirit for most of the long term denizens of this...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2025 at 11:39 pm
I am curious how it (GENERATE_SERIES function)performs compared to the tally table.
It's nasty fast. It's not as flexible as you'll find in other flavors of SQL because it "only"...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2025 at 8:50 pm
That trigger was placed there for a reason.
In financing terms once something is on a journal / ledger, it should ALWAYS remain on that journal / ledger.
If there was...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2025 at 5:27 pm
Largely speaking, I've thus far not used any of the various and sundry "AI" implementations out there (either for SQL or anything else,) mostly because, well, I don't see...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2025 at 5:22 pm
Decades of change and experimentation just to find out that SQLServerCentral remains one of the best online forums.
The system won't let me give that comment the million or so...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2025 at 2:27 am
Hi, John. Gosh... it's been a long time since we've seen each other in person.
Nice article and thank you for the honorable mention.
Just to add a bit of a clarification,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 26, 2025 at 2:20 am
Viewing 15 posts - 166 through 180 (of 59,101 total)