Lasse Gravgaard Lange

That whole blog post should probably be added to the SymmetricDS user guide though ;)

Hi Eric, Thank you for your reply. You were absolutely correct! I was not aware of this requirement. Switching to SymmetricDS Pro also helped a lot, as I could see when the transform became active in the GUI.

I put it everywhere. Sadly it did not work. I have created the tables manually at the target database instead. This worked :)

I want to synchronize a few tables from SQL Anywhere to Azure SQL. The tables may have a lot of foreign key references, but I don't care about referential integrity in the Azure SQL database. I tried defining create.table.without.foreign.keys=true in all engines, but the foreign key constraints are still created when I send a table reload request to the Azure database. I have tried completely cleaning both databases, but when the tables are synchronized, the constraints are created. Is there something...

I want to synchronise a few tables from SQL Anywhere to Azure SQL. The tables may have a lot of foreignkey references, but I don't care about referential integrity in the Azure SQL database. I tried defining create.table.without.foreign.keys=true in all engines, but the foreign key constraints are still created when I send a table reload request to the Azure database. I have tried completely cleaning both databases, but when the tables are synchronized, the constraints are created. Is there something...

Hi Evan, I have attempted to create a column transform, however I could not get it to generate a new column at the target node. The following is what I have tried: insert into "dbo"."sym_transform_table" ( transform_id, source_node_group_id, target_node_group_id, transform_point, source_schema_name, source_table_name, target_table_name, update_action, delete_action, transform_order, column_policy, update_first, last_update_by, last_update_time, create_time ) values ( 'Ledger', 'local', 'stage', 'EXTRACT',...

I had this issue as well. After trying a lot of different combinations for schema_name and catalog_name in sym_trigger, I was finally able to find something where SymmetricDS was able to find the table, both for trigger creation and deletion. In my case, I used a SQL Anywhere database, but I don't know which DBMS you are using.

Hello everyone, Almost finished with setting up SymmetricDS, but still one thing I cannot figure out. I need to add an extra column to the target database which tells what node the data comes from. I have 4 "cannot change" SQL Anywhere databases, from which I wish to sync a few tables to a central Azure SQL database. The connection is working fine, and when running with a single SQL Anywhere database, the table synchronizes to Azure without problems. What I wish to accomplish is adding an extra column...