So after doing some more digging, it looks like new connections come in and are part of the internal workload group initially before they are assigned to a user defined...

I agree. We are testing in lower environments. Thanks for sharing the article.

Very odd that a technology will indefinitely grow a data file for a database that is 500MB normally...

I've got an extended event running now that will hopefully capture the next growth event(s) with more detail.

Just happened again. I have pulled the growth report. Autogrowth just starts going haywire and growing and growing until there is no more space on the drive... lol. There is...

As far as I know you would need to set up some sort of activity collection that logs to a table. But even then, you might miss some things if...

Do you have any logs? I would check secondary sql logs and primary. It might have just needed time.

You could create a separate AD group ADG2. Add ADG2 Group as a member of ADG1. Add ADG2 to SQL server, grant it dbo on the select database. That way,...

You lose any routing. IE, if you have the listener specified in connection strings, those connections don't happen. Where normally, it would route traffic to the primary or secondary depending...

Obviously you want to get to the root of the issue that is causing the sudden spike but I might recommend looking into buffer pool extension if you have a...

Do you have 2 jobs on the primary executing the same package at the same time?

I believe you can see the server that attempted to execute the package if you dig a little deeper in the report

As far as I know you need some level of access to view the agent history / job activity monitor on each node. 

Since they are all trying to...