Activity overview
Latest activity by ngarris
Yes, its now below 66 GB and continuing to decrease, which is nice.
Could the bloat have been caused by the data purging bug referred to in this post? viewtopic.php?f=197&t=79357&p=140960&hilit=purge#p140960
I upgraded SQL Monitor to version 5 on February 11. Up to that point the database was 61,000 MB. It had been growing, but much slower (was 50,000 MB on October 11, 2015). From February 11 to April 11 it grew from 61,000 MB to almost 75,000 MB.
Data size should remain stable, since the number of monitored servers hasn't changed, and data purge settings haven't changed. / comments
Yes, its now below 66 GB and continuing to decrease, which is nice.
Could the bloat have been caused by the data purging bug referred to in this post?viewtopic.php?f=197&t=79357&p=140960&hilit=purg...
Where are guidelines for data purging?
Hello, as usual I am a big fan of SQLMonitor, it is an enormous help to our small DBA shop. Brilliant software!
In the past, the Configuration > Data Purging screen provided some guidance for the d...
SQL Monitor database grew and now decreasing in size
Our SQL Monitor database grew significantly, 26 GB in the last 8 months, to a high of almost 75 GB on April 10. I have not changed the data purging settings in years, and number of servers monitore...
Could not maintain connection, files on wrong drive
Hi, I wanted to post this resolution to possibly help someone else with the same problem. We built a new SQL Server with database files defaulting to E drive and log files defaulting to F drive. Ho...
Here are the results of the suggested tests to diagnose SQL Monitor connection problems. I have passed them along to our server admins to see if they can resolve these issues.
1. Ping works.
2. Remote registry access does not work (PerfMon on SQL Monitor server, logged on as login used to access database server, will not access the database server).
3. WMI does not work when accessed from the SQL Monitor server.
4. Remote file access works.
5. The SQL connection fails for both Windows and SQL logins. / comments
Here are the results of the suggested tests to diagnose SQL Monitor connection problems. I have passed them along to our server admins to see if they can resolve these issues.
1. Ping works.
2. Rem...
No, SQL Monitor cannot reach the Windows host, it is unreachable. / comments
No, SQL Monitor cannot reach the Windows host, it is unreachable.
P.S. I can successfully ping the server I want to add from the server which is running SQL Monitor. / comments
P.S. I can successfully ping the server I want to add from the server which is running SQL Monitor.
Thanks. I tried editing the properties to connect using TCP/IP and the correct port number (all other settings left at default). I tried both the alias and the actual server name. Both come up unreachable. / comments
Thanks. I tried editing the properties to connect using TCP/IP and the correct port number (all other settings left at default). I tried both the alias and the actual server name. Both come up unre...
I should add that on the server running SQL Monitor (which also hosts SQL Server and the SQL Monitor database), I added an alias for the aliased server using SQL Server Configuration Manager. / comments
I should add that on the server running SQL Monitor (which also hosts SQL Server and the SQL Monitor database), I added an alias for the aliased server using SQL Server Configuration Manager.
Can't connect to aliased SQL Server 2012
For security, we've given a new SQL Server default instance an alias with a non-standard port. Using the alias (and also using the server name) we are not able to connect using SQL Monitor, it says...