Viewing 15 posts - 121 through 135 (of 59,067 total)
Are you sure they said "junk" and not "jump"? There is good use for tables that only contain IDs from the Fact Tables and the Dimension tables. In relational databases,...
--Jeff Moden
Change is inevitable... Change for the better is not.
My inline responses are in Bold'n'Black print below....
Thank you Jeff, Please find my inline response below.
If those backup drives are on the same system as your SQL Server,...
--Jeff Moden
Change is inevitable... Change for the better is not.
From your command it looks like you are using SQL native backup. There are other backup products out there (eg SQL Litespeed) that have as part of their USP...
--Jeff Moden
Change is inevitable... Change for the better is not.
You can always tell when a new article is going to be popular when the SPAM hits the discussion on it two weeks prior to the date it's supposed to...
--Jeff Moden
Change is inevitable... Change for the better is not.
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.
@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.
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.
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.
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.
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.
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.
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.
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.
Viewing 15 posts - 121 through 135 (of 59,067 total)