Viewing 15 posts - 166 through 180 (of 5,842 total)
I sure hope someone can do some benchmarking on these!! :Whistling:
August 30, 2017 at 6:00 pm
Numerous things can result in a huge bottleneck on a disk. They include:
Antivirus, backups, snapshot access, controller (or other shared IO component) congestion due to non-problematic-disk load, driver/firmware bug...
August 30, 2017 at 10:48 am
Odd, but not the oddest thing I have come across when linked servers were involved! :w00t:
There are a variety of ways you can make that query run on...
August 28, 2017 at 5:10 pm
A very fast but hard-coded way would be to use CASE, similar to this pseudo-code. It should work due to short-cutting in the CASE execution:
CASE WHEN...
August 28, 2017 at 9:15 am
A) So you are running SQL Server database on a single rotating disk? May I suggest you start there as the root cause of your problems? 🙂 And are all...
August 28, 2017 at 9:09 am
August 24, 2017 at 12:07 pm
Adding a witness server to database mirroring is FAR LESS risky, difficult, problematic, BUGGY, etc., etc. than a Failover Cluster Instance and Always On Availability Group.
Anyway, best of...
August 23, 2017 at 7:43 pm
August 23, 2017 at 2:12 pm
August 23, 2017 at 9:45 am
Ola.hallengren.com is my go-to solution for MX.
August 22, 2017 at 9:43 pm
OOPSIE!! Coffee clearly hasn't kicked in yet! 🙂
August 22, 2017 at 7:47 am
IMHO the SQL Server debugger is essentially useless. Which is a damn shame...
August 22, 2017 at 7:35 am
Also, did you do any analysis while the code was running for that 1 hour? What if someone had a lock on a table and you simply waited for THAT...
August 22, 2017 at 7:34 am
Viewing 15 posts - 166 through 180 (of 5,842 total)