SQL Anywhere Feedback - Disable Events on startup

Author

Disable Events on startup

Kjetil Valøy

2005-10-27, 7:41 am

I would like to have a server option that disable Events from
automatically trigger. This will be usefull when I copy the backup of
the DB and LOG file to another connection and runs validate on that
DB. Then I will know that the backup event wont trigger and therefor
destroy the latest backup.

Kjetil Valøy

Breck Carter [TeamSybase]

2005-10-27, 7:41 am

Does the backup still run if you start the database as read-only? It
probably *shouldn't* since backup implies checkpoint, and checkpoint
contradicts read-only.

Breck

On 11 Oct 2005 05:53:01 -0700, __no_spam__kjetil.valoy@iticket.no
(Kjetil Valøy) wrote:

>I would like to have a server option that disable Events from
>automatically trigger. This will be usefull when I copy the backup of
>the DB and LOG file to another connection and runs validate on that
>DB. Then I will know that the backup event wont trigger and therefor
>destroy the latest backup.
>
>Kjetil Valøy

--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com

Kjetil Valøy

2005-10-27, 7:41 am

I actually don't know about that, I have to try that later. But if we
want to validate a backup that was taken on a database where
transactions are not commited yet. Then (if I have understood the
manual correct) you cannot start the database in read-only mode.

If I start that DB in "not readonly mode" the events starts fiering
and "bad things" can happend.

-- Kjetil --

On 11 Oct 2005 07:08:52 -0700, "Breck Carter [TeamSybase]"
< NOSPAM__bcarter@risi
ngroad.com> wrote:

>Does the backup still run if you start the database as read-only? It
>probably *shouldn't* since backup implies checkpoint, and checkpoint
>contradicts read-only.
>
>Breck
>
>On 11 Oct 2005 05:53:01 -0700, __no_spam__kjetil.valoy@iticket.no
>(Kjetil Valøy) wrote:
>
>
>--
>SQL Anywhere Studio 9 Developer's Guide
>Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
>bcarter@risingroad.com
>RisingRoad SQL Anywhere and MobiLink Professional Services
>www.risingroad.com

Rob Waywell

2005-10-27, 7:41 am

You can't start that database anyway without the uncommitted transactions
being rolled back, and a checkpoint being issued once the recovery is
complete, which would modify the log file regardless.

So your options are either:

1) Use a copy of the backup for this validation in which case you won't be
concerned about the events firing (which doesn't mean it isn't a reasonable
feature request)

2) Run the BACKUP DATABASE command with the WAIT BEFORE START clause to
create a backup that does not require any recovery and which can be started
as a read only database.

--
-----------------------------------------------
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
"Kjetil Valøy" <__no_spam__kjetil.valoy@iticket.no> wrote in message
news:434e39f0.701489268@forums.sybase.com...
>I actually don't know about that, I have to try that later. But if we
> want to validate a backup that was taken on a database where
> transactions are not commited yet. Then (if I have understood the
> manual correct) you cannot start the database in read-only mode.
>
> If I start that DB in "not readonly mode" the events starts fiering
> and "bad things" can happend.
>
> -- Kjetil --
>
> On 11 Oct 2005 07:08:52 -0700, "Breck Carter [TeamSybase]"
> < NOSPAM__bcarter@risi
ngroad.com> wrote:
>
>

Breck Carter [TeamSybase]

2005-10-27, 7:41 am

Yes, absolutely, I forgot about read-only-versus-recovery, oops :)

On 13 Oct 2005 06:39:01 -0700, "Rob Waywell"
<rwaywell@no_spam.ianywhere.com> wrote:

>You can't start that database anyway without the uncommitted transactions
>being rolled back, and a checkpoint being issued once the recovery is
>complete, which would modify the log file regardless.
>
>So your options are either:
>
>1) Use a copy of the backup for this validation

Using a copy may be the best of all worlds: It proves the backup db
and log files can be used to start/recover, it lets you run in read
only mode if desired, it lets you run dbvalid, AND it makes WAIT
BEFORE START unnecessary. In a busy shop, WAIT BEFORE START is
equivalent to NEVER START :)

Not to mention the fact that WAIT BEFORE START doesn't seem to be
accessible via dbbackup, and dbbackup is more desirable in some
environments; e.g., it can be scheduled by staff that don't have
database access, it's easier to keep a log of actions performed by
batch files, etc.

> in which case you won't be
>concerned about the events firing (which doesn't mean it isn't a reasonable
>feature request)

I agree about it being a reasonable request. Events are very new in
the grand scheme of things, there have been unpredicted uses AND
unpredicted, um, issues :)

>
>2) Run the BACKUP DATABASE command with the WAIT BEFORE START clause to
>create a backup that does not require any recovery and which can be started
>as a read only database.

--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com

Kjetil Valøy

2005-10-27, 7:41 am

I do copy the .db and .log file to a new location to do verification.
Also, now and then I need to take a copy of the database to run some
tests. If I start the database on the same computer as the "live"
database the events starts triggering and it canl destry my backup
from last night.

This was my motivation for this request.

By the way. It was no problem running backup in read only mode.

-- Kjetil --

On 13 Oct 2005 06:42:16 -0700, "Rob Waywell"
<rwaywell@no_spam.ianywhere.com> wrote:

>You can't start that database anyway without the uncommitted transactions
>being rolled back, and a checkpoint being issued once the recovery is
>complete, which would modify the log file regardless.
>
>So your options are either:
>
>1) Use a copy of the backup for this validation in which case you won't be
>concerned about the events firing (which doesn't mean it isn't a reasonable
>feature request)
>
>2) Run the BACKUP DATABASE command with the WAIT BEFORE START clause to
>create a backup that does not require any recovery and which can be started
>as a read only database.
>
>--
>-----------------------------------------------
>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
>"Kjetil Valøy" <__no_spam__kjetil.valoy@iticket.no> wrote in message
>news:434e39f0.701489268@forums.sybase.com...
>
>

Sponsored Links