In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

2.7

What is the connector configuration?

N/A

What is the captured database version and mode of depoyment?

(E.g. on-premises, with a specific cloud provider, etc.)

SQL  Server Database  running on Microsoft Azure Cloud

What behaviour do you expect?

 make Debezium configurable to persist/read schema history in the underlying database.

What behaviour do you see?

Schema history is persisted in Kafka that requires indefinite retention.

Do you see the same behaviour using the latest relesead Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

Yes

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

N/A

How to reproduce the issue using our tutorial deployment?

N/A

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

Reliance on Kafka to store schema history is not ideal.

Implementation ideas (optional)

 make Debezium configurable to persist/read schema history in the underlying database.