Azure SQL Server - Multi Partiton Mode

Hi!

I'm currently in the process of deploying a debezium connector (v 2.1.0) and came accross some unexpected behavior due to a technical limitation in Azure SQL Server. The problem is, that Azure SQL Server does not support three-part queries ([db].[schema].[table/stored-proc]. A connection to an Azure SQL Server is always bound to a single database and cannot be altered via USE statements. Any three-part-queries where the [db] part does not equal the db of the sqlconnection will result in an error. 

So if you're connected to [db-1], you can execute [db-1].[dbo].[exec_custom_sp], but not [db-2].[dbo].[exec_custom_sp]. This behavior has been correctly analyzed by sergeimorozov in this ticket DBZ-5496.

With the bugfix, it's possible to stream changes from a single database. When trying to stream changes from multiple database using a single connector we receive the following error:

{"error_code":400,"message":"Connector configuration is invalid and contains the following 1 
error(s):\nUnable to connect. Check this and other connection properties. Error: Reference to database and/or server 
name in '[our-database-name].sys.sp_cdc_help_change_data_capture' is not supported in this version of SQL Server.\nYou can 
also find the above list of errors at the endpoint `/connector-plugins/{connectorType}/config/validate`"}
 

It would be great if you could take a look at this and determine if this is a bug or a feature request. Multi-Partitioning is a vital feature in our setup, as we're dealing with sharded databases. Deploying single connector instances for each database would be possible, but incurs additional overhead we would like to avoid.