Duplicated databases under monitored server since installation of SQL Monitor 8.0.19.16748

JoergH

Hi,

we have the same problem that DanAppleyard described in his post "Databases Duplicated Under Monitored Server" in early january:

16 out of 38 databases of one of our monitored servers have doubled "ghost" entries in SQL Monitor.

As was stated in the above mentioned post, those ghost entries are related to database_name entries in msdb.dbo.backupset which differ from the name entries in sys.databases in having different case patterns (e.g. "Abcd" instead of "abcd" and so on).

This wasn't an issue until we installed SQL Monitor 8.0.19.16748 in the mid of October. We first thought of an issue due to switching several times between monitored servers after migration to SQL 2017. But the following query showed the exact date when the ghost entries appeared:

SELECT _name COLLATE SQL_Latin1_General_Cp1_CS_AS as _name_1<br>&nbsp;&nbsp;&nbsp; , utils.TicksToDateTime(CollectionDate) AS Collection_Datum<br>&nbsp;&nbsp;&nbsp; , * <br>FROM [data].[Cluster_SqlServer_Database_Keys] <br>WHERE Parentid = 15 -- belongs to that specific monitored server<br>ORDER BY _name_1

How can we fix this issue?

We are on version 9.0.2.19903.  I just saw that 9.0.3 is released but unfortunately we can't go up to that version since SQL Monitor ist actually still running on SQl Server 2008 R2!

Regards, Joerg

Russell D

Hi Joerg, can you send those query results into support@red-gate.com please?

JoergH

Hi Russell,

sure I'll send it in a few minutes.

Meanwhile, I opened a support case #131718, and this issue is already tracked as SRP-11790.

Joerg

Russell D

This has now been fixed, please update to 9.0.9 and let us know if you have any issues.