Hi Abdelhak,
As I mentioned in your other thread, it is not recommended to run your SQL Anywhere database without a transaction log for performance reasons. It is also used to help in times of database recovery.
Tip: Always use a transaction log
Using a transactionlog can provide data protection, and can dramatically improve the performance of SQL Anywhere.
When operating without a transactionlog, SQL Anywhere performs a checkpoint at the end of every transaction which consumes considerable resources.
When operating with a transactionlog, SQL Anywhere only writes notes detailing the changes as they occur. It can choose to write the new database pages all at once, at the most efficient time. Checkpoints make sure information enters the database file, and that it is consistent and up to date.
You can further improve performance if you store the transaction log on a different physical device than the one containing the primary database file. The extra drive head does not generally have to seek to get to the end of the transaction log.
The linked article is incorrect in that turning off the transaction log will not have any impact and that turning it off is a wise strategy. On the contrary, creating a backup strategy and restoring it is your best mechanism to maintain your BI database and not lose any data in times of crisis.
---
In your specific case, I would also highly recommend taking a look at the health of your disk (i.e. chkdsk). The error:
A read failed with error code: (1392)
means that the Windows OS returned code 1392:
C:\>net helpmsg 1392
The file or directory is corrupted and unreadable.
Regards,
Jeff Albion
SAP Active Global Support