Question, the vendor of our software decided to change the names of some tables that have been participating in transactional replication for Qlik Attunity CDC for a long time, these tables are quite large and I really would not like to throw them out of the publication due to renaming and re-perform the transfer of all data to Attunity CDC storage.
Perhaps there is some way to avoid this?
Before making any changes in a production environment, test to run the task from a timestamp or do metadata refresh run in a test instance to ensure that the approach works as expected.
You misunderstood me, I need change the name of the table in the SQL Server, and this table is already involved in transactional replication for Attunity CDC. After I change the name of table the Attunity task I get an error
What exactly are you trying to accomplish? If the old table name no longer exists, you'll have to add the new table to the task. If just the table name changed and the same data still exists with a new name on both the source and target, then you will need to do the advanced reload as suggested by @Dana_Baldwin to avoid reloading the entire table. For the CDC table, you can select the option to keep the existing data as well.
Request you to check the Help Document seems for MS SQL server its a limitation.
sp_renameis not supported (e.g.
sp_rename 'Sales.SalesRegion', 'SalesReg;)