. "2017-06-13T05:47:39Z" . "2017-06-13T05:47:39.515722"^^ . . . "2017-06-13T05:47:39.515722"^^ . . "VirtTipsAndTricksGuideTransactionLogControl" . . "b3651ef6c3e22336a416cd261318e5b1" . "VirtTipsAndTricksGuideTransactionLogControl" . . "VirtTipsAndTricksGuideTransactionLogControl" . . "2017-06-13T05:47:39Z" . . . . . . . . "%META:TOPICPARENT{name=\"VirtTipsAndTricksGuide\"}%\n\n---+ How can I perform SPARQL Updates without exceeding transactional log size?\n\nSPARUL updates are generally not meant to be transactional. To prevent running out of rollback \nspace, it is usually best to tell Virtuoso to commit each operation as it is done, with this SQL call:\n\nSQL> log_enable (2);\n\t \n\nTransaction logging can also be turned off for [[VirtBulkRDFLoader][bulk updates]]. In such case, \none should do a manual checkpoint after the bulk insert operation, to ensure persistence across \nserver restart, since there will be no roll forward log.\n\n\n\nIf you're only occasionally exceeding the configured transactional log size, you may prefer \nto set the \"TransactionAfterImageLimit\" parameter in the virtuoso.ini config file \nto a higher value than its 50MB default:\n\n#virtuoso.ini\n...\n[Parameters]\n...\nTransactionAfterImageLimit = 99999999 ; bytes default 50000000\n...\n\n\n\n\n---++ Related\n \n * [[VirtTipsAndTricksGuide][Virtuoso Tips and Tricks Collection]]\n * [[http://docs.openlinksw.com/virtuoso/rdfperformancetuning.html#rdfperfsparul][Using SPARUL]]\n * [[http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#ini_Parameters][Virtuoso INI Parameters]]\n" . . . . .