简体   繁体   中英

Is there a way to use SQL Server 2019 and CDC (Change Data Capture) at the same time?

I am working on a project where I have to use CDC, catalog collation SQL_Latin1_General_CP1_CI_AS and a CS collation for data. I get an collation conflict error from sp_cdc_create_populate_stored_procs when enabling cdc for any table. This is called from other procedure "sys.sp_cdc_enable_table_internal" and again this is call from my own sql-script "sys.sp_cdc_enable_table". To me this seems like a bug but would appreciate if there's any new ideas how to implement production level workaround on this matter.

This is a documented limitation of Contained Databases.

Limitations

Partially contained databases do not allow the following features.

-Partially contained databases cannot use replication, change data capture, or change tracking.

-Numbered procedures

-Schema-bound objects that depend on built-in functions with collation changes

-Binding change resulting from collation changes, including references to objects, columns, symbols, or types.

-Replication, change data capture, and change tracking.

Contained Databases - Limitations

If you need a case-insensitive catalog collation along with a case-sensitive collation for data, you can set the column collation directly on your text columns instead of using the database's default collation.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM