SQL Anywhere database replication - Log File Considerations with SQLRemote

Author

Log File Considerations with SQLRemote

Jack T.

2005-08-23, 1:23 pm

I have a question about the docs. The docs say:

>Transaction log-based replication SQL Remote replication is based on the
>transaction log. This enables it to replicate only changes to data, rather
>than all data, in each update. Also, log-based replication has performance
>advantages over other replication systems.
The transaction log is the repository of all changes made to a database. SQL
Remote replicates changes made to databases as recorded in the transaction
log. Periodically, all committed transactions in the consolidated database
transaction log belonging to any publication are sent to remote databases.
At remote sites, all committed transactions in the transaction log are
periodically submitted to the consolidated database.<

If SQLRemote uses the log file for replication, then I take it that the
normal backup scheme where you backup the the database and truncate the log
file will mess up SQLRemote or does it handle it have its own copy of log
file entries where all housekeeping issues are managed by SQLRemote?

Thanks,
Jack T.

Rob Waywell

2005-08-24, 1:23 pm

take at look at the dbbackup -r switch

Yes dbremote requires old log files as a normal part of replication.

--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional

Sybase's iAnywhere Solutions

Please respond ONLY to newsgroup

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer
"Jack T." <Jack. Toering_NO_SPAM_HERE
_@LeadingEdgeITA.com> wrote in message
news:430b54b7$1@foru
ms-2-dub...
>I have a question about the docs. The docs say:
>
> The transaction log is the repository of all changes made to a database.
> SQL Remote replicates changes made to databases as recorded in the
> transaction log. Periodically, all committed transactions in the
> consolidated database transaction log belonging to any publication are
> sent to remote databases. At remote sites, all committed transactions in
> the transaction log are periodically submitted to the consolidated
> database.<
>
> If SQLRemote uses the log file for replication, then I take it that the
> normal backup scheme where you backup the the database and truncate the
> log file will mess up SQLRemote or does it handle it have its own copy of
> log file entries where all housekeeping issues are managed by SQLRemote?
>
> Thanks,
> Jack T.
>

Jack T.

2005-08-24, 1:23 pm

>Yes dbremote requires old log files as a normal part of replication.<

That's very good to know.

Thanks,
Jack T.

"Rob Waywell" <rwaywell@no_spam.ianywhere.com> wrote in message
news:430ca090$1@foru
ms-1-dub...
> take at look at the dbbackup -r switch
>
> Yes dbremote requires old log files as a normal part of replication.
>
> --
> -----------------------------------------------
> Robert Waywell
> Sybase Adaptive Server Anywhere Developer - Version 8
> Sybase Certified Professional
>
> Sybase's iAnywhere Solutions
>
> Please respond ONLY to newsgroup
>
> EBF's and Patches: http://downloads.sybase.com
> choose SQL Anywhere Studio >> change 'time frame' to all
>
> To Submit Bug Reports:
> http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
>
> SQL Anywhere Studio Supported Platforms and Support Status
> http://my.sybase.com/detail?id=1002288
>
> Whitepapers, TechDocs, and bug fixes are all available through the
> iAnywhere
> Developer Community at www.ianywhere.com/developer
> "Jack T." <Jack. Toering_NO_SPAM_HERE
_@LeadingEdgeITA.com> wrote in message
> news:430b54b7$1@foru
ms-2-dub...
>
>

Sponsored Links