View Issue Details

IDProjectCategoryView StatusLast Update
0004439SymmetricDSBugpublic2022-08-01 19:26
Reporterj.mackay@backinmotion.com.au Assigned Toelong  
Priorityhigh 
Status closedResolutionno change required 
Product Version3.12.0 
Summary0004439: MSSQL: Cannot change sym_ tables destination schema
DescriptionIt seems there is no option to change the sync tables destination schema.

We have around 100 databases syncing to a single "warehouse" database and we're using an identifier for each database as the destination schema for the tables.

Example
DB1: dbo.clients go to destination db1.clients
DB2: dbo.clients go to destination db2.clients

The problem is that the source dbo.sym_ tables aren't configurable to set the destination schema to db1.sym_ .
Tagsdialect: sql-server, documentation

Activities

elong

2020-07-17 16:44

developer   ~0001733

The SYM objects go in the database you configure with db.url property in the engine properties file. If you have tables in another catalog (database) or schema that you want to capture changes on, then you specify he source_catalog_name and source_schema_name in the sym_trigger table.

elong

2020-07-17 16:48

developer   ~0001734

Thinking about this some more, on SQL-Server you can specify the default schema where objects will be created for the user. For example, if you want the "symmetricds" user to put its sym tables and other objects into the "sym" schema, you would run:

alter user symmetricds with default_schema = sym

Issue History

Date Modified Username Field Change
2020-06-23 03:38 j.mackay@backinmotion.com.au New Issue
2020-07-17 16:44 elong Assigned To => elong
2020-07-17 16:44 elong Status new => feedback
2020-07-17 16:44 elong Note Added: 0001733
2020-07-17 16:48 elong Note Added: 0001734
2020-07-22 16:41 elong Tag Attached: dialect: sql-server
2020-07-22 17:30 elong Tag Attached: documentation
2022-08-01 19:26 elong Status feedback => closed
2022-08-01 19:26 elong Resolution open => no change required