Replication/archiving of database content to archive db in..

Dear subscribers

I’m looking for a solution to archive the content of some tables in a
product that uses Sybase as the database engine. The problem is that
some of the table contain records in such large numbers that it
affects the performance of the application thus we like to move
content older than e.g. a year to an archive instance of the database
on a regular basis. This archive instance will basically have the same
table setup as the original version but will contain the old data.

We have looked at Sybase’s Replication Server but I like to see if
there are any other options available. My biggest worry is fault
tolerance i.e. if anything goes wrong we mustn’t loose any data, i.e.
that a row is deleted from the main database without being written
properly to the archive database. If Sybase supports cross-database
transactions maybe this task can be solved with a simple scheduled
script?

Any suggestions are most welcome.

Regards, Ola Theander

ola.theander RemoveThis @otsystem.com wrote:
> Dear subscribers
>
> I?m looking for a solution to archive the content of some tables in a
> product that uses Sybase as the database engine. The problem is that
> some of the table contain records in such large numbers that it
> affects the performance of the application thus we like to move
> content older than e.g. a year to an archive instance of the database
> on a regular basis. This archive instance will basically have the same
> table setup as the original version but will contain the old data.
>
> We have looked at Sybase?s Replication Server but I like to see if
> there are any other options available. My biggest worry is fault
> tolerance i.e. if anything goes wrong we mustn?t loose any data, i.e.
> that a row is deleted from the main database without being written
> properly to the archive database. If Sybase supports cross-database
> transactions maybe this task can be solved with a simple scheduled
> script?

Replication servers seems to be overkill for what you want to
achieve.

- Copy the tuples you want to archive to the archive server,
- backup the archive database(s),
- then delete the tuples in the active server.

OK, the tuples are in both databases for a while, but if
that's a problem, then you can limit the number of rows you
copy in one run to shorten this period.

Luc.