Activity overview
Latest activity by tomdpe
Let's see if I can make clear how particularly bad this issue is. In a nutshell at no time without actually being in and looking at SQL Monitor do I know with any certainty that my Sql servers and db's are being monitored unless I have another solution monitoring the SQL Server that houses my SQL Monitor DB and actually monitoring that individual db since it is when the DB goes offline that SQL Monitor stops monitoring without any indication that there is a problem. This actually means my entire environment could be having issues and SQL Monitor could be in a compromised state and no one would be the wiser. In essence until there is some alert coming back from SQL Monitor that its database is offline It cannot be trusted. Do any of your customers know this. Is it pointed out anywhere that if you are going to use SQL Monitor to monitor your SQL Server environment you need to have a different SQL Server monitoring system in place to make sure its db is up and that it is able to monitor. I run servers with databases backing millions of customers and call centers with thousands of users and I am now finding out that SQL Monitor cannot be trusted to alert me when its own database goes offline and that Red-Gate is passing it off as since it cannot be logged to a db we can't alert on it. SQL Monitor SHOULD BE SCREAMING WHEN THIS HAPPENS. And Red-Gate should issuing a notice with an intent to correct not an excuse and a non response.
/ comments
Let's see if I can make clear how particularly bad this issue is. In a nutshell at no time without actually being in and looking at SQL Monitor do I know with any certainty that my Sql servers and...
I am dealing with the same issue and would suggest that when there is an issue with the SQL Monitor database being unavailable, that it could be indicated by logging an alert to a local data file similar to one used by the SSMS Tab History and sending out that alert indicating the main SQL Monitor database is unavailable prior to suspending all other alerting would be a great help. Once the DB is back online that entry could then be synced up as the first step of bringing everything online. This would cover the need to logging all alerts and give us better assurance that we are covered. Remember that your product is only as strong as your weakest link and this has caused issues for us on a couple of occasion. / comments
I am dealing with the same issue and would suggest that when there is an issue with the SQL Monitor database being unavailable, that it could be indicated by logging an alert to a local data file s...
Have you been able find a solution for this? / comments
Have you been able find a solution for this?
Log files sent. / comments
Log files sent.
After updating the SQL Monitor server with the same CU it made no difference as far as the issue. This issue is consistent across 6 different servers (2 different windows clusters). This issue started with each server as soon as it was patched with this CU. / comments
After updating the SQL Monitor server with the same CU it made no difference as far as the issue. This issue is consistent across 6 different servers (2 different windows clusters). This issue st...
Intermittent Missing data for Machine and SQL Sql Server metrics for servers w/ 2018-10 CU KB4462917
After updating the Windows 2016 with 2018-10 CU (KB4462917) for the machine with our SQL Servers the Machine and SQL Server Metrics are missing 2-4 minutes of data every ~20 minutes. Each server'...
Does removing and re-adding a Cluster server Lose the history
I recently moved a SQL Fci to our production cluster. To do this I had setup a new FCI instance on our production cluster with a different name, move all of the databases sync everything up. Rena...
While installing SQL Monitor 8 The create database step hangs. It appears to create the database but gets stuck while running this step. "DECLARE @command NVARCHAR(MAX)SET @command = 'ALTER DATABASE ' + QUOTENAME(DB_NAME()) + ' SET ALLOW_SNAPSHOT_ISOLATION ON' EXEC (@command)" This is not actually doing anything. This same statement comes up when trying to use that created db after closing the window and finishing the instal using the created database, when first launching the web site. I am using a windows server 2016 standard server and using a separate existing SQL Server 2016 FCI. The trace on this process just shows it connected with no activity and the activity monitor shows it as suspended with repeated ~1000ms ENABLE_VERSIONING Waits. I would appreciate a solution as I finally have licenses to install this and would like to get using it. / comments
While installing SQL Monitor 8 The create database step hangs. It appears to create the database but gets stuck while running this step. "DECLARE @command NVARCHAR(MAX)SET @command = 'ALTER DATAB...