Problem: tblConfig_AgentGroupMembers : ForeignKeyConstraint tblConfig_AgentGroup_tblConfig_AgentGroupMembers_fk_constraint requires the child key values (d5dac6e3-f237-40bc-806b-2d9d4713c066) to exist in the parent table.
select * from tblConfig_AgentGroupMembers where FKAgentGroup like ‘d5dac6e3-f237-40bc-806b-2d9d4713c066’
Problem: Error: 2018-Jun-13 16:29:29.376 Synchronization failed – System.Data.ConstraintException: tblConfig_QueueAgentGroupMembers : ForeignKeyConstraint tblConfig_Queue_tblConfig_QueueAgentGroupMembers_fk_constraint requires the child key values (c3ca877f-85ca-41be-b3bc-bef09140752b) to exist in the parent table.
statement to find it: select * from tblConfig_QueueAgentGroupMembers where FKQueue like ‘c3ca877f-85ca-41be-b3bc-bef09140752b’
To remove change remove select * and replace with del
There is a known issue in version 18.104.22.168 where one table starts growing very large
You can check if yo have this problem by checking the disk usage in sql
If you see the Pie chart showing the database file as all purple then check the disk usage by table
What i then did was read the contents of this table with this SQL command
You can leave off the “Datekey” command. This will show you everything in the table. What i saw is that one day millions of entries while other days had a few thousand. I deleted that day and the SQL DB usage dropped by half
Then re-summarize the data into the SQL DB month by month check the size as you go. If it does go large again repeat the commands and find the offending day/time.
If SQL Express is used in the CCM/IQ environment, it imposes a 4gb capacity (or 10gb for SQLExpress 2008 R2) to each database. After a certain period of time, the database will fill up to its maximum. The amount of time until the maximum capacity is reach depends on the amount of the site traffic / amount of data collected or the amount of historical data present in the database.