Activity overview
Latest activity by NCstyle
Error 518
Got the following error on last night's backup:
Backing up Search_Service_Application_AnalyticsReportingStoreDB_752bbc078c184de79ad36f296b621130 (full database) to:
E:Program FilesMicrosoft SQL Ser...
How to purge data for Removed Servers
I removed some servers from my SQL Monitor configuration. However, I realized I forgot to check the box to "Delete existing data for the server from the Repository." So none of the data from thes...
Crimdon has a good point. We use Maintenance Windows precisely for the case where a machine will be down and may possibly have multiple reboots and we don't want to receive email alerts on it. This change in 5.0.7 leaves us with no way to suppress machine down alerts during maintenance times. / comments
Crimdon has a good point. We use Maintenance Windows precisely for the case where a machine will be down and may possibly have multiple reboots and we don't want to receive email alerts on it. Th...
Backup/Restore failures in SQL 2014 failover cluster
This is an FYI for those using SQL Backup and implementing SQL 2014 Failover Clusters. If you use the new Cluster Shared Volumes feature in Windows 2012 R2 for your storage instead of the old-styl...
I can also verify the bug with DBs in Simple mode alerting for Log Backup Overdue. It's occurring on two of my servers which are both SQL 2012, but it doesn't occur on all of my SQL 2012 servers. So it doesn't appear to be tied to the SQL version. / comments
I can also verify the bug with DBs in Simple mode alerting for Log Backup Overdue. It's occurring on two of my servers which are both SQL 2012, but it doesn't occur on all of my SQL 2012 servers. ...
FYI: The upgrade to 5.0.3.1858 appears to have solved the performance issue introduced by 5.0.2.1644. CPU utilization is back to where it was when we were on 5.0.1.1302, and the response time of the UI is back to normal as well. Not sure that this will fix the earlier complaints about the UI from the beginning of this thread, but it did fix the issues introduced in version 5.0.2 for us. / comments
FYI: The upgrade to 5.0.3.1858 appears to have solved the performance issue introduced by 5.0.2.1644. CPU utilization is back to where it was when we were on 5.0.1.1302, and the response time of t...