I contacted support for this issue and we were unable to rectify the issue. I don't believe the underlying issue was caused by Redgate software. I will be reviewing the cause for the memory 'explosion'.
We have scheduled an emergency server reboot this evening.
I did learn that 1 process =SQBCoreService.exe is expected per SQL instance on the box. We only have a single instance, so 4 was abnormal, but no investigation was possible.
Support also shared this ...unfortunately for my scenario it requires that SQL Backup Agent service be operational.
We have scheduled an emergency server reboot this evening.
I did learn that 1 process =SQBCoreService.exe is expected per SQL instance on the box. We only have a single instance, so 4 was abnormal, but no investigation was possible.
Support also shared this ...unfortunately for my scenario it requires that SQL Backup Agent service be operational.
| Code: |
| Thanks for your call - to try and get the crash-log, do the following: USE master GO EXECUTE master..sqbutility 9997 GO |