troubleshooting Question
How to suspend replication to a table with MSA database replication
Hi,
I am working with Sybase Replication 12.6 using MSA. There are reports that run against about 60 tables in the replicated database.
The application team wants to suspend updates to those tables while the reports are running. The report takes approximately one hour.
There are about 100 other critical tables in this database and they prefer not to suspend the connection for the entire database.
It seems I can create a 2nd database and define a subscription but there are a few tables that are extremely large that are not part of the report.
If I define a subscription for a 2nd replicated database, I need to perform a dump/load- so this replicated database will need to be as large
as the source database and unfortunately with Sybase 12.6, I can't shrink the database - totally wasted space.
Basically, what I need in addition to my MSA replicated database is a snapshot of the database or a subset of the database.
Is there a way to suspend updates for only the tables in the report for my current replicated database?
I thought about creating a database at primary with only views for the tables in the report then trying to replicate that database.
Then I can suspend connections to that database. Any reason this will not work?
Any other ideas on how to accomplish this?
THANK YOU!!!
I am working with Sybase Replication 12.6 using MSA. There are reports that run against about 60 tables in the replicated database.
The application team wants to suspend updates to those tables while the reports are running. The report takes approximately one hour.
There are about 100 other critical tables in this database and they prefer not to suspend the connection for the entire database.
It seems I can create a 2nd database and define a subscription but there are a few tables that are extremely large that are not part of the report.
If I define a subscription for a 2nd replicated database, I need to perform a dump/load- so this replicated database will need to be as large
as the source database and unfortunately with Sybase 12.6, I can't shrink the database - totally wasted space.
Basically, what I need in addition to my MSA replicated database is a snapshot of the database or a subset of the database.
Is there a way to suspend updates for only the tables in the report for my current replicated database?
I thought about creating a database at primary with only views for the tables in the report then trying to replicate that database.
Then I can suspend connections to that database. Any reason this will not work?
Any other ideas on how to accomplish this?
THANK YOU!!!
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 9 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Most Valuable Expert award recognizes technology experts who passionately share their knowledge with the community, demonstrate the core values of this platform, and go the extra mile in all aspects of their contributions. This award is based off of nominations by EE users and experts. Multiple MVEs may be awarded each year.