%META:TOPICPARENT{name="VirtTipsAndTricksGuide"}%

---+ How can I perform SPARQL Updates without exceeding transactional log size?

SPARUL updates are generally not meant to be transactional. To prevent running out of rollback 
space, it is usually best to tell Virtuoso to commit each operation as it is done, with this SQL call:
<verbatim>
SQL> log_enable (2);
</verbatim>	    

Transaction logging can also be turned off for [[VirtBulkRDFLoader][bulk updates]]. In such case, 
one should do a manual checkpoint after the bulk insert operation, to ensure persistence across 
server restart, since there will be no roll forward log.



If you're only occasionally exceeding the configured transactional log size, you may prefer 
to set the "<b>TransactionAfterImageLimit</b>" parameter in the virtuoso.ini config file 
to a higher value than its 50MB default:
<verbatim>
#virtuoso.ini
...
[Parameters]
...
TransactionAfterImageLimit = 99999999   ; bytes default 50000000
...
</verbatim>



---++ Related
   
   * [[VirtTipsAndTricksGuide][Virtuoso Tips and Tricks Collection]]
   * [[http://docs.openlinksw.com/virtuoso/rdfperformancetuning.html#rdfperfsparul][Using SPARUL]]
   * [[http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#ini_Parameters][Virtuoso INI Parameters]]