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?