- SQL Anywhere uses a transaction log to record all of the changes that occur in a database.
- In many circumstances, disk space limitations make it impractical to let the transactionlogs grow indefinitely to record all historical data.
- How should the transaction log maintenance be handled to ensure that the database backups and restores are maintained?
- SAP SQL Anywhere (all versions, all platforms)
- SAP Business Intelligence (BI) 4.0 SP7 and higher
- SAP Crystal Server
.log file, Transaction log, sybase, business objects, bobj, dblog, truncate, truncation, SQL Any, SQLA, SQL, changes , KBA , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , BI-BIP-ADM , BI Servers, security & CrystalReports viewing in BI platform , BI-BIP , Business intelligence platform , BI-BIP-SRV , CMS / Auditing issues (excl. 3rd Party Authentication) , MOB-AFA , Afaria , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.