the_chad
Thanks, Greg! Here is some detailed information:
- MajorDB1_Merge
1 Filtered table based on SUSER_SNAME()
8 joined tables, based on a simple join (e.g., FilterTbl.CustID = JoinTbl.CustID)
Includes 1 updateable table and 7 download only
- MajorDB1_Trans
Includes stored procedures, views, functions
- MinorDB1_Merge
4 Filtered tables based on SUSER_SNAME()
Filtered Table A:
1 simple joined table
Filtered Table B:
10 simple joined tables
Filtered Table C:
4 simple joined tables
Filtered Table D:
6 simple joined tables
- MinorDB1_Trans
stored procs, views, functions
- MajorDB2_Merge
2 Filtered tables based on SUSER_SNAME()
Filtered Table A:
7 simple joined tables, including 2 updateable tables
1 joined table (InvoiceHdr) with an additional date join statement
This table has 3 child tables
1 joined table with an additional date join statement
This table has 4 child tables, 1 of which has 1 child table
Filtered Table B:
1 joined table (InvoiceHdr) based on different criteria than above
- MajorDB2_Trans1
64 relatively small tables for codes and such
3 filtered tables, 1 based on a literal "in" list (e.g., ('a', 'b', 'c'), 2 based on an in list over a subquery
- MajorDB2_Trans2
stored procs, views, functions
- MajorDB3_Merge
4 Filtered tables based on SUSER_SNAME()
Filtered Table A:
1 simple joined table, download only
Filtered Table B (all updateable):
7 simple joined tables
3 joined tables with additional date join
1 simple joined table with a child table
Filtered Table C (all updateable):
3 simple joined tables
Filtered Table D (all updateable):
1 simple joined table with 8 child tables that also exist under Filtered Table B
- MajorDB3_Trans1
13 relatvely small tables for codes
- MajorDB3_Trans2
stored procs, views, functions
- MinorDB2_Merge
7 Filtered tables based on SUSER_SNAME(), 1 of which has a child table
6 updateable tables, 2 download only
- MinorDB2_Trans1
23 tables for codes
- MinorDB2_Trans2
stored procs, views, functions
This publication contains most of the stored procedures (200 or so) for the application
Error Summary
The error "The replication agent has not logged a progress message in
n minutes..." occurs most often in the transactional publications for stored
procedures. In some of these cases, there will be an action message "A total
of 2 transaction(s) with 2 command(s) were delivered" followed by "A DDL
change has been replicated", which seems to indicate a transaction success
message is received after the syncrhonization success message, thereby making
the distributor think the synchronization is still in progress. This error
also occurs when there seem to be no transactions available for
synchronization, and does occasionally occur for merge publications.
I also have lock problems and performance issues when updating the filtered
table(s) in the major databases. Could this be because there are too many
tables joined off of the filtered table If so, how might I split them up