Using isql to restore a Sybase database
The steps required to recover a Sybase database depend on the database that is involved and the problem that you have on your system.
These steps can include the following:
Using buildmaster, installmaster, and installmodel for system databases
Re-creating database devices
Re-creating databases
Loading database dumps
Applying transaction logs
For information on how to perform the preceding steps, see your Sybase documentation.
A load can take significantly longer than a dump. The time required to load a database depends on the overall number of pages in the database. The load database command loads all used pages from the dump into the target database and runs recovery of syslogs to ensure consistency. The load process initializes any unused pages.
You can load database and transaction dumps by manually submitting the Sybase LOAD command to SQL server (UNIX and Linux) or the isql utility on the client (Windows).
The LOAD command must include the appropriate dump file name. More information is available about how to edit the LOAD command with the correct dump file name.
Make sure to load the database dump and all of the transaction logs before bringing the database back online.
The following example shows you how to restore the database mydb to the level of a recent database dump plus two transaction log dumps:
Execute the LOAD commands directly from SQL server.
This loads the database dump and transaction log dumps.
Check database consistency.
When you have brought the database up-to-date, use DBCC commands to check the consistency of the database.
load database mydb from "sybackup::SYBASE.mydb.D.0.14693.12-12-1997.09:29:37 -SERV saturn" go