Many DBA Dash errors in Tool

[chaithanyagade]

I could see many Primary key violation errors form DBA Dash Errors (24 hours). Could you please share any SQL Script to remove the duplicate key errors.

[DavidWiseman]

Hi, you might get these errors if you have two instances of the service running. Have you installed it as a service but also have it running as a console application? Or maybe setup two services monitoring the same instances?

[chaithanyagade]

Hi David, Thanks for your email. I don't think I have two instances with same setup. How do we check that I installed twice or having two instances? [cid:0ea57e5f-65de-4672-ad6e-34d16f85ff43] Regards, Chaithanya Database Engineer +91-9866369038

…

________________________________ From: David Wiseman ***@***.***> Sent: Wednesday, November 27, 2024 8:24 AM To: trimble-oss/dba-dash ***@***.***> Cc: chaithanyagade ***@***.***>; Author ***@***.***> Subject: Re: [trimble-oss/dba-dash] Many DBA Dash errors in Tool (Issue #1147) Hi, you might get these errors if you have two instances of the service running. Have you installed it as a service but also have it running as a console application? Or maybe setup two services monitoring the same instances? — Reply to this email directly, view it on GitHub<#1147 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A4RBZJMLZNAO2ILQVTO7DJ32CXW2TAVCNFSM6AAAAABSSCGT3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBUGI4TIMZWGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[DavidWiseman]

First check on the machine where you installed DBA Dash service. Open Task Manager and go to the Details tab. Sort by Name and see how many copies of DBADashService.exe are running. If you add the "Command Line" column, you can see where they are running from. If you have two and they are both running from the same location, someone might be running it as a console application - check the user name column.

DBA Dash logs information about the service used to import data. You could try this query which will show the agents associated with active instances.

SELECT * 
FROM dbo.DBADashAgent A
WHERE EXISTS(SELECT 1 
		FROM dbo.Instances I
		WHERE I.ImportAgentID = A.DBADashAgentID
		AND I.IsActive=1
		)

It's last one wins so if there are two agents running it's possible only one of them might be visible when you run the above query and it might keep changing between them. If you remove the WHERE clause from the above query it will give you the full list of possibilities.

SELECT * 
FROM dbo.DBADashAgent A

The other possibility I can think of is that the instance is listed twice in the source connections. This might occur if you have slightly different connection strings that point to the same instance.

Hope this helps,

David

[chaithanyagade]

Thanks David. It seems like resolved after removing duplicate source connection from the monitoring list. I will confirm you after 48 hours. Really, Thanks for your quick response. Regards, Chaithanya Database Engineer +91-9866369038

…

________________________________ From: David Wiseman ***@***.***> Sent: Thursday, November 28, 2024 12:27 AM To: trimble-oss/dba-dash ***@***.***> Cc: chaithanyagade ***@***.***>; Author ***@***.***> Subject: Re: [trimble-oss/dba-dash] Many DBA Dash errors in Tool (Issue #1147) First check on the machine where you installed DBA Dash service. Open Task Manager and go to the Details tab. Sort by Name and see how many copies of DBADashService.exe are running. If you add the "Command Line column, you can see where they are running from. If you have two and they are both running from the same location, someone might be running it as a console application - check the user name column. DBA Dash logs information about the service used to import data. You could try this query which will show the agents associated with active instances. SELECT * FROM dbo.DBADashAgent A WHERE EXISTS(SELECT 1 FROM dbo.Instances I WHERE I.ImportAgentID = A.DBADashAgentID AND I.IsActive=1 ) It's a last one wins so if there are two agents running it's possible only one of them might be visible when you run the above query and it might keep changing between them. If you remove the WHERE clause from the above query it will give you the full list of possibilities. SELECT * FROM dbo.DBADashAgent A The other possibility I can think of is that the instance is listed twice in the source connections. This might occur if you have slightly different connection strings that point to the same instance. Hope this helps, David — Reply to this email directly, view it on GitHub<#1147 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A4RBZJORWVIWFG6IHUPBQRL2C3HYXAVCNFSM6AAAAABSSCGT3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBVGUZDGMRRGI>. You are receiving this because you authored the thread.Message ID: ***@***.***>