Viewing 8 posts - 1 through 9 (of 9 total)
So that seems to have worked (to be precise, adding SQL Server Agent's account to Local Admins on all cluster nodes is what worked - the post is slightly unlcear)....
February 23, 2016 at 9:20 am
In my environment, the issue that presented with this error message was caused by an AD account being deleted, then recreated with the same name.
For example:
Bob Blob has an AD...
August 17, 2015 at 1:28 pm
So Ola himself graciously gave me the solution to this issue that worked.
Instead of calling the stored procedure from a T-SQL job step, the stored procedure should be called from...
August 17, 2015 at 1:21 pm
Yes, I have indeed tested it and it works for me (but your mileage may vary). In my environment, backing up larger DBs to multiple files allows me to shave...
August 4, 2015 at 9:12 am
That's correct. Double and triple. That was my first hunch actually.
February 27, 2015 at 11:19 am
- DATA and LOG are separated, but only logically. They are on two drives allocated on the same large SSD volume attached via iSCSI.
- When REBUILD is run, I see...
November 7, 2014 at 8:40 pm
Database was set to compatibility level 100. Could you tell me what impact changing it to 110 would make?
Will post execution plans tomorrow. Thanks for the help so far.
October 16, 2014 at 4:48 pm
Same issue here. I don't really want to borrow the DLL from an older version. I wonder if SP1 will include a fix for this?
October 16, 2014 at 4:22 pm
Viewing 8 posts - 1 through 9 (of 9 total)