How can we help you today? How can we help you today?
DonFerguson
Activity overview Badges (0) Posts (47) Comments (160)

Comments

Sort by recent activity
Thanks Pete.  Since the word force is somewhat ambiguous, can you describe the exact criteria where it won't show red in global overview vs. when it will show if the  option "Do not force" is chosen? / comments
  1. Community
  2. Redgate Monitor
  3. SRP-12429 Optionally highlight servers encountering an error on global dashboard
Thanks Pete.  Since the word force is somewhat ambiguous, can you describe the exact criteria where it won't show red in global overview vs. when it will show if the  option "Do not force" is chosen?
0 votes
With the licensing issue not being an issue as pointed out by Russell, if you still truly don't want to monitor the instance, the work around is to suspend monitoring for the specific instance under Monitored Servers in Configuration. / comments
  1. Community
  2. Redgate Monitor
  3. How to remove SQL server instance that i don't want to monitor
With the licensing issue not being an issue as pointed out by Russell, if you still truly don't want to monitor the instance, the work around is to suspend monitoring for the specific instance unde...
0 votes
I don't think 9.1.1 was fully pulled.  It's still in the new release announcements thread with no mention of this issue.  And the download link there still works. / comments
  1. Community
  2. Redgate Monitor
  3. SQL Monitor Error
I don't think 9.1.1 was fully pulled.  It's still in the new release announcements thread with no mention of this issue.  And the download link there still works.
0 votes
This is a nice new feature.  My one piece of feedback is that it would be nice if I could send this specific alert to a custom email address.  The default address doesn't really work for me without major reconfiguration of all the other alerts.  I guess it's time for me to learn how to use the new powershell API to make the major reconfiguration of email address for all alerts easier. [image] / comments
  1. Community
  2. Redgate Monitor
  3. SQL Monitor Alert for when SQL Monitor server goes down...?
This is a nice new feature.  My one piece of feedback is that it would be nice if I could send this specific alert to a custom email address.  The default address doesn't really work for me without...
0 votes
Perhaps a "monitor the monitor" feature could be leveraged in a multi-base configuration.  Just an idea, but if anyone is interested, I'm sure we need to add it as a new feature suggestion. / comments
  1. Community
  2. Redgate Monitor
  3. SQL Monitor Alert for when SQL Monitor server goes down...?
Perhaps a "monitor the monitor" feature could be leveraged in a multi-base configuration.  Just an idea, but if anyone is interested, I'm sure we need to add it as a new feature suggestion.
0 votes
Same here.  The base monitor installation finally succeeded on a 2012 repository with the 9.0.7 release.  I still have four more base monitors to update, but I am optimistically hopeful that it will succeed on them as well. / comments
  1. Community
  2. Redgate Monitor
  3. Unable to install the current Version of SQL Monitor
Same here.  The base monitor installation finally succeeded on a 2012 repository with the 9.0.7 release.  I still have four more base monitors to update, but I am optimistically hopeful that it wil...
0 votes
I just tried version 9.0.6.  Still no joy.  I am getting the same error. [Red Gate Monitor (9.0.6.20734), Running as:  (Service), Working Dir: C:\Program Files\Red Gate\SQL Monitor\BaseMonitor] [Running on: , OS Version: Microsoft Windows NT 6.1.7601 Service Pack 1, .NET Runtime Version: 4.0.30319.42000 (Microsoft)] [Start Date: 2019-03-20 17:51:48Z, Current Date: 2019-03-20 17:51:54Z, Elapsed Time: 00:00:05.8281250] 2019-03-20 17:51:56,014 [              7] WARN  RedGate.SqlMonitor.Default.Config.SchemaVersioning.Sql.SqlSchemaVersionManager - Requested schema version upgrade from SchemaVersion(Seq224) to SchemaVersion(Seq227) Upgrade path is: SchemaVersion(Seq224) SchemaVersion(Seq225) SchemaVersion(Seq226) SchemaVersion(Seq227) 2019-03-20 17:52:51,201 [              7] WARN  RedGate.SqlMonitor.Engine.Alerting.Base.Service.SchemaInitialization - Schema upgrade failed with schema upgrade exception RedGate.SqlMonitor.Default.Config.SchemaVersioning.Sql.SqlSchemaUpgradeException: Violation of PRIMARY KEY constraint 'PK_datawarehouse_AllRPOs'. Cannot insert duplicate key in object 'datawarehouse.AllRPOs'. The duplicate key value is (~snip~, , ~snip~, 636886845050000000). ---> System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK_datawarehouse_AllRPOs'. Cannot insert duplicate key in object 'datawarehouse.AllRPOs'. The duplicate key value is (~snip~, , ~snip~, 636886845050000000). / comments
  1. Community
  2. Redgate Monitor
  3. Unable to install the current Version of SQL Monitor
I just tried version 9.0.6.  Still no joy.  I am getting the same error. [Red Gate Monitor (9.0.6.20734), Running as:  (Service), Working Dir: C:\Program Files\Red Gate\SQL Monitor\BaseMonitor][Run...
0 votes
For me, I needed to first uninstall the newer base monitor and then reinstall 9.0.3. / comments
  1. Community
  2. Redgate Monitor
  3. Unable to install the current Version of SQL Monitor
For me, I needed to first uninstall the newer base monitor and then reinstall 9.0.3.
0 votes
As a test, I went ahead and restored a copy of the RedGateMonitor database onto a test SQL Server 2016 instance, installed the basemonitor service and pointed it to the 2016 instance, and it worked.  So I believe that it is due to unexpected behavior of SQL Server 2012.  I suspect that it may be caused by the use of the LAG function, but this would take far more dissecting of the query causing the issue to confirm.  Hopefully Red Gate can find a solution.  Upgrading the database engine, albeit a major undertaking, may be a potential work around. / comments
  1. Community
  2. Redgate Monitor
  3. Unable to install the current Version of SQL Monitor
As a test, I went ahead and restored a copy of the RedGateMonitor database onto a test SQL Server 2016 instance, installed the basemonitor service and pointed it to the 2016 instance, and it worked...
0 votes
I too, am having issues upgrading.  It failed on 5 of 7 of my Base Monitor installations.  I was able to do a little digging and found that the real issue is not permissions, but instead a failure in the database repository upgrade process. The install log shows the following error: RedGate.SqlMonitor.Default.Config.SchemaVersioning.Sql.SqlSchemaUpgradeException: Violation of PRIMARY KEY constraint 'PK_datawarehouse_AllRPOs'. Cannot insert duplicate key in object 'datawarehouse.AllRPOs'. The duplicate key value is (~HostnameSnip~, , ~DatabaseNameSnip~, 636879933070000000). ---> System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK_datawarehouse_AllRPOs'. Cannot insert duplicate key in object 'datawarehouse.AllRPOs'. The duplicate key value is (~HostnameSnip~, , ~DatabaseNameSnip~, 636879933070000000). Further digging shows that a new procedure is created called [datawarehouse].[PopulateAllRPOs] that contains the following: SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE PROCEDURE [datawarehouse].[PopulateAllRPOs] AS BEGIN TRANSACTION; DELETE FROM [datawarehouse].[AllRPOs]; WITH [AllDbs] AS (SELECT [data].[Cluster_SqlServer_Database_Keys].[Id] AS [DatabaseId],            [data].[Cluster_Keys].[_Name] AS [ClusterName],            [data].[Cluster_SqlServer_Keys].[_Name] AS [InstanceName],            [data].[Cluster_SqlServer_Database_Keys].[_Name] AS [DatabaseName]     FROM [data].[Cluster_SqlServer_Database_Keys]         INNER JOIN [data].[Cluster_SqlServer_Keys]             ON [data].[Cluster_SqlServer_Keys].[Id] = [data].[Cluster_SqlServer_Database_Keys].[ParentId]         INNER JOIN [data].[Cluster_Keys]             ON [data].[Cluster_Keys].[Id] = [data].[Cluster_SqlServer_Keys].[ParentId]),      [AllBackupDates] AS (SELECT DISTINCT            [BTK].[ParentId] AS [DatabaseId],            [BI].[_FinishDate] AS [FinishDate]     FROM [data].[Cluster_SqlServer_Database_BackupType_Backup_Instances] [BI]         INNER JOIN [data].[Cluster_SqlServer_Database_BackupType_Backup_Keys] [BK]             ON [BK].[Id] = [BI].[Id]         INNER JOIN [data].[Cluster_SqlServer_Database_BackupType_Keys] [BTK]             ON [BTK].[Id] = [BK].[ParentId]),      [RPOs] AS (SELECT [DatabaseId],            [RpoFrom],            [RpoTo],            CASE                WHEN [RpoFrom] IS NULL THEN                    NULL                ELSE                    [RpoTo] - [RpoFrom]            END [Duration]     FROM     (         SELECT [DatabaseId],                [FinishDate] AS [RpoTo],                LAG([FinishDate], 1) OVER (PARTITION BY [DatabaseId] ORDER BY [FinishDate]) AS [RpoFrom]         FROM [AllBackupDates]     ) [ConsecutiveBackups] ) INSERT INTO [datawarehouse].[AllRPOs] (     [ClusterName],     [InstanceName],     [DatabaseName],     [BackupFinishDate],     [DurationTicks] ) SELECT [adb].[ClusterName],        [adb].[InstanceName],        [adb].[DatabaseName],        [RPOs].[RpoTo] AS [To],        [RPOs].[Duration] FROM [RPOs]     INNER JOIN [AllDbs] [adb]         ON [RPOs].[DatabaseId] = [adb].[DatabaseId]; COMMIT TRANSACTION; GO This query is producing duplicates and violating the primary key constraint in [datawarehouse].[AllRPOs].  I'm not sure if this has anything to do with the issue, but the two repositories where it succeeded, were on SQL Server 2016, but the 5 that failed were hosted on SQL Server 2012. At any rate, I haven't been able to get the repositories on 2012 to upgrade.    / comments
  1. Community
  2. Redgate Monitor
  3. Unable to install the current Version of SQL Monitor
I too, am having issues upgrading.  It failed on 5 of 7 of my Base Monitor installations.  I was able to do a little digging and found that the real issue is not permissions, but instead a failure ...
0 votes
Total activity
280
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
73