Signalling table not working for SQLServer if snapshot comes from a replica

On environments where the impact of the snapshot is not affordable to be done in the primary the obvious option is create a secondary and perform the snapshot there without impact productions environments.

The current implementation of the signaling assumes that we are always running the connector against a SQLServer that is writable.

It would be interesting if this signaling table could be place in a different database that allow us to have read-write permissions for signalling and the main database pointed to a readOnly replica for perform the snapshot at the same time.