The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Stop new tables being sent to remotes
Posted: 18 Feb 10 8:58 AM
|
Hello,
we've created a couple of new tables to hold archived HISTORY records, and I don't want these to be sent to remotes.
I can see a "Sync this table out to remotes" option in the table properties, but it's all greyed out. Is it possible to unset this somewhere? |
|
|
|
Re: Stop new tables being sent to remotes
Posted: 18 Feb 10 9:30 AM
|
This is done best while adding the tables, not after the fact.
The definitions can be altered on the RESYNCTABLEDEFS table, however it may be best to drop the tables and readd them correctly.
|
|
|
| |
|
Re: Stop new tables being sent to remotes
Posted: 22 Feb 10 10:46 AM
|
Hmm, I've set the "OMNIDIRECTIONAL" field to "X" for the three tables in question (which seemed to be the only difference when I created a test-table with sync set to no) and yet it's still sending the records out to the remote. It looks like it's being completely ignored by the remote creation DTS.  |
|
|
| |
|
Re: Stop new tables being sent to remotes
Posted: 22 Feb 10 10:54 AM
|
That would be too big of a hack....
Whenever a Remote DB is built, the DTS creates the DB itself, but there are other items that are generated during the Creating (eg. Site Key and Key Code) and some are updated within Blobs on the database after the creation of the DB.
Best bet is to, as I stated, drop the tables and add them back with the correct configuration.
|
|
|
|
Re: Stop new tables being sent to remotes
Posted: 22 Feb 10 11:41 AM
|
Yeah, it's not ideal. I'd only clear out the actual INSERT tasks.
These tables contain a lot of data (hence the remote problem in the first place). I can't just drop them. Does this sound sensible:
1. Remove all remotes
2. Create a table TEMP_H1 with the same structure as the original H1 using SQL
3. Insert all the data from H1 into TEMP_H1
4. Use Administrator to delete H1
5. Use Administrator to create a new H1 with the original structure
6. Use SQL to insert all the data from TEMP_H1 into the new H1
7. Use SQL to delete TEMP_H1
8. Cut new remotes
|
|
|
|