Hello,
Environment:
Lab with 2 x View Connection Broker v7.4 on Win2016. An external SQL Database server running SQL2014 Enterprise.
Problem:
After upgrading from 7.3 to 7.4, the Event DB, running on the external SQL Server, grows super fast to enormous proportions. It will fill the disk the DB is on, or if the DB has a file-size-limit, grow to that size. After that, it turns "red" inside the Horizon Admin GUI (because it cannot write new records, obviously).
As this is just a lab, I un-configured the event DB and deleted the humongous DB (it was about 80 GB in size...) from the SQL Server.
While the event DB is not configured (shows up as corresponding yellow in the Admin GUI), both Connection Servers went from "almost no CPU usage" to "80% or more CPU Usage all the time".
Then:
On the SQL server I created a new fresh database and limited the file-size to 1 GB.
I configured a Event DB again, the CPU's of both connection servers came to rest (almost no usage, this is a lab and just sits idle)
Within 30 minutes, the DB file grew to 1 GB.
This problem is 100% repeatable.
In the logs on the connection servers (C:\ProgramData\VMware\VDM\logs), I see nothing that grabs my attention relating to this issue.
All i see in the regular log file are these errors:
"[EventDBConnection] Could not reconnect to Events database: Unable to create events tables: Could not allocate space for object 'sys.sysobjvalues'.'clst' in database 'HorizonViewEventDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup"
Which is completely logical as the 1 GB DB-file is full. If I change the size to 2 GB, within 30 minutes, that will be full too. etc. etc. etc.
In the Debug logfile, I don't see anything dodgy either.
My question is: i'm not a SQL person. How do I go about troubleshooting this? I need to find out "with what is the DB getting filled at such an insane rate". Is there a SQL query that I can run to see the last X hundred messages that came in before the DB reached it's size limit?