How to maintain consistency between tables in database dump

[r***@gmail.com]

In Sybase database dump, what can we do in order to maintain the Table
data is consistent IN A SINGLE POINT OF TIME ?

We would like (1) to keep the database up and running and (2) users are
still able to make minor database changes during database dump.

Appreciate if anyone would help on this.

[Mark A. Parsons]

What do you mean by 'minor database changes'?

If this would include changes to the table that you're trying to keep in a
'consistent' state ... then you have mutually exclusive requirements.

If you're talking about allowing users to make changes to *other* tables
then you could look at revoking all insert/update/delete permissions on the
desired table during the duration of the database dump.

Post by r***@gmail.com
In Sybase database dump, what can we do in order to maintain the Table
data is consistent IN A SINGLE POINT OF TIME ?
We would like (1) to keep the database up and running and (2) users are
still able to make minor database changes during database dump.
Appreciate if anyone would help on this.

[r***@gmail.com]

Post by Mark A. Parsons
What do you mean by 'minor database changes'?
If this would include changes to the table that you're trying to keep in a
'consistent' state ... then you have mutually exclusive requirements.
If you're talking about allowing users to make changes to *other* tables
then you could look at revoking all insert/update/delete permissions on the
desired table during the duration of the database dump.

Post by r***@gmail.com
In Sybase database dump, what can we do in order to maintain the Table
data is consistent IN A SINGLE POINT OF TIME ?
We would like (1) to keep the database up and running and (2) users are
still able to make minor database changes during database dump.
Appreciate if anyone would help on this.

[r***@gmail.com]

Let me elaborate further.

I would like to make a backup with an image that is consistent "at" the
point when the "dump database" command is issue.

All changes made after the command should not be backup in the dump
file. This is particular important for cross table consistency.

I know that Oracle uses the online Redo (Rollback) segment to achive
this. Any mechanism (or command) in Sybase which can do that.

[Eugene Korolkov]

Ray,

I think no way, but at least dump is consistent "at" the point when
"dump database"
was finished, cause all changes between start point (when dump was issued)
and end point (when it is actually finished) have been applied in the
3rd phase of dump.
when trlog changes were applied.

HTH,
Eugene

Post by r***@gmail.com
Let me elaborate further.
I would like to make a backup with an image that is consistent "at" the
point when the "dump database" command is issue.
All changes made after the command should not be backup in the dump
file. This is particular important for cross table consistency.
I know that Oracle uses the online Redo (Rollback) segment to achive
this. Any mechanism (or command) in Sybase which can do that.

[A.M.]

Post by r***@gmail.com
Let me elaborate further.
I would like to make a backup with an image that is consistent "at" the
point when the "dump database" command is issue.

You might want to read up on how Sybase ASE's dumps work.

Post by r***@gmail.com
All changes made after the command should not be backup in the dump
file. This is particular important for cross table consistency.

The way ASE dumps work is that it snapshots all committed
transactions up to the point when it finishes, not at the
start.

Post by r***@gmail.com
I know that Oracle uses the online Redo (Rollback) segment to achive
this. Any mechanism (or command) in Sybase which can do that.

What Oracle stupidly does is irrelevant to how ASE works.

If you want to be totally consistent, you could quiesce
the database and snapshot it yourself. This will involve
some unavailability in the database while its quiesced.

-am © MMVI

[Ray]

Much appreciated for sharing experience on this issue.