Viewing 15 posts - 8,476 through 8,490 (of 59,091 total)
What I've read here and what I'm seeing in my system, it's definitely the weekly index defrag that is the culprit. I have been using the Hallengren reindex script...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2019 at 12:24 am
Its ALWAYS the dba's fault - we just get used to it 🙂
Heh... not me... and they know better than to try... especially if they want help with the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2019 at 12:08 am
I'm not too worried about having some data latency because this will be a bulk overnight job that only runs once at night. I just need to to be...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2019 at 11:25 pm
That stat has been gathered in survey's we've contracted out for from Redgate Software. Each year we hire professional surveyers to contact database people across a wide range of...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2019 at 11:17 pm
Someone should do a survey that asks if anyone has actually been successful in using this DMV to actually find and fix performance issues or if they use other methods...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2019 at 6:09 pm
Getting back to the original replies on this thread, which more than adequately expressed the right idea which I'll strongly second, this exercise is a total waste of time and...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2019 at 5:23 pm
To answer the first question... NO.
To answer the implied question of how to make this faster, we need some more data. We need to know ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2019 at 5:18 pm
To ask the direct question that MVDBA implied, how much data latency delay is allowed?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2019 at 5:04 pm
So, just out of curiosity, what did you end up doing here?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2019 at 4:46 pm
This is why we should comment our source code and version control checkins - so those who follow us can better understand why we did things the way...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2019 at 2:17 pm
P.S. I also strongly agree with Scott... there's no way that I'd rely on DateFirst settings never mind actually change them.
What is wrong with using DATEFIRST?
Why the strong...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2019 at 2:03 pm
Hi Thom, How to approach such people issues. This is been like a habbit for the dev team to send out email to dba team to tune as...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2019 at 1:04 pm
How often do you add documents/nodes to this hierarchy?
According to the OP there are approximately 25k rows in the table. If this represents 5 years of activity,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2019 at 10:14 pm
Jeff,
I am completely agreed with you but this is a OPENTEXT application software so table design we don't have any control.
Honestly, I don't know how frequently we are adding...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2019 at 10:08 pm
The problem is the code that is "overly" using TempDB; you can't make TempDB use less space. Those that wrote the query need to fix it; if it's using...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2019 at 10:07 pm
Viewing 15 posts - 8,476 through 8,490 (of 59,091 total)