Description
The following error might be observed on the Confluent Cloud UI for Microsoft SQL Server Sink Connectors:
The config table.format.name and topic names define a fully qualified name for the table which can take the form <database name>. <schema>. <table name> if delimiters are used. The connector attempted to write to a fully-qualified table name which had a non-existent database (eg- wrongdb.someschema.sometable or wrongdb.sometable). Make sure that <database name> in the fully-qualified table name correctly refers to a database that exists in the database instance. Additionally it is considered a best practice to ensure that the <database name> in the fully qualified name is equivalent to the connector configuration so make sure that they are the same.
Applies To
Confluent Cloud
Microsoft SQL Server Sink Connector
Cause
This error message indicates the sink connector attempts to write to a fully-qualified table name that has a non-existent database (for example, <database_name>.<schema_name>.<table_name> or <database_name>.<table_name>).
Resolution
The config "table.name.format" and topic names define a fully qualified name for the table which can take the form <database_name>.<schema_name>.<table_name> if delimiters are used.
If the value of the "table.name.format" config is not explicitly set, the connector uses the topic name as the table name. If you wish to change this, you can set the "table.name.format" config to be just the literal table name without using the ${topic} variable.
Ensure that <database_name> in the fully qualified table name correctly refers to a database in the instance. It is considered a best practice to ensure that the <database_name> in the fully qualified name is equivalent to the connector configuration.