It depends on what you want to do. Further there are some options on how
to do bypass recovery, globally with a traceflag (for all databases or
all except master), with changing the status in sysdatabases.
The reasons for having a bypass recovery could be full/corrupt/lost
transaction log, doing admin jobs or many more.
So answer your question it would be good to get some more details why
you want to do a bypass recovery.
thanks
my database is corrupted.i dont have backup of this db.can i use
bypass recovery to repair the database?
Depends on what error you got, best would be to contact Sybase Tech.
Support so they an help you. :)
You can give it a try to do a bypass recovery with setting status -32768
for the database and see if you can get this datbase fixed or repaired
with the common dbcc checks.
Hope this helps.
HTH..
Abhishek Joshi
Using this dbcc command is pointless when the database has been marked as
suspect.
HTH,
Rob V.
-----------------------------------------------------------------
Rob Verschoor
Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
and Replication Server 15.0.1/12.5 // TeamSybase
Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks & Recipes for Sybase ASE" (ASE 15 edition)
"The Complete Sybase ASE Quick Reference Guide"
"The Complete Sybase Replication Server Quick Reference Guide"
mailto:r...@YOUR.SPAM.sypron.nl.NOT.FOR.ME
http://www.sypron.nl
Sypron B.V., Amersfoort, The Netherlands
Chamber of Commerce 27138666
-----------------------------------------------------------------