Hi Daniel, The log_enable() function is a connection wide setting , thus is on connection you stop logging then all of statements executed will be with no logging which includes both transaction and replication logs.
If less statements are made then this should restrict the number of transactional activities that have to be logged and hence improve performance. Best Regards Hugh Williams Professional Services OpenLink Software, Inc. // http://www.openlinksw.com/ Weblog -- http://www.openlinksw.com/blogs/ LinkedIn -- http://www.linkedin.com/company/openlink-software/ Twitter -- http://twitter.com/OpenLink Google+ -- http://plus.google.com/100570109519069333827/ Facebook -- http://www.facebook.com/OpenLinkSoftware Universal Data Access, Integration, and Management Technology Providers > On 28 Oct 2015, at 14:08, Davis, Daniel (NIH/NLM) [C] <daniel.da...@nih.gov> > wrote: > > Thanks, it obviously had to be scoped, but it wasn’t clear to me how it was > scoped. If I call log_enable(2,1) manually before the stored procedure, > would the entire stored procedure turn off transaction logging? > > If I refactor my stored procedure to use fewer statements to do the same > changes to the graph, will that cause the transaction logging to be less of > an issue for performance (and failure as it exceeds its maximum size)? > > From: Hugh Williams [mailto:hwilli...@openlinksw.com] > Sent: Tuesday, October 27, 2015 11:20 PM > To: Davis, Daniel (NIH/NLM) [C] <daniel.da...@nih.gov> > Cc: virtuoso-users <virtuoso-users@lists.sourceforge.net> > Subject: Re: [Virtuoso-users] log_enable(2,1) - how long? > > Hi Daniel, > > log_enable (2,1) would turn off transaction logging for the next statement > executed which on completion the transaction logging would be turned back on. > > If it is called in a stored procedure then once again it would turn off > transaction logging for the next statement executed which on completion the > transaction logging would be turned back on. > > Best Regards > Hugh Williams > Professional Services > OpenLink Software, Inc. // http://www.openlinksw.com/ > <http://www.openlinksw.com/> > Weblog -- http://www.openlinksw.com/blogs/ > <http://www.openlinksw.com/blogs/> > LinkedIn -- http://www.linkedin.com/company/openlink-software/ > <http://www.linkedin.com/company/openlink-software/> > Twitter -- http://twitter.com/OpenLink <http://twitter.com/OpenLink> > Google+ -- http://plus.google.com/100570109519069333827/ > <http://plus.google.com/100570109519069333827/> > Facebook -- http://www.facebook.com/OpenLinkSoftware > <http://www.facebook.com/OpenLinkSoftware> > Universal Data Access, Integration, and Management Technology Providers > > On 27 Oct 2015, at 13:53, Davis, Daniel (NIH/NLM) [C] <daniel.da...@nih.gov > <mailto:daniel.da...@nih.gov>> wrote: > > When I execute log_enable(2,1) in a session, does it just affect statements > made by that statement, or the whole server? > When the session closes, does it revert to logging transactions? > > What if I move log_enable(2,1) to a stored procedure called by a session? > > Dan Davis, Systems/Applications Architect (Contractor), > Office of Computer and Communications Systems, > National Library of Medicine, NIH > > ------------------------------------------------------------------------------ > _______________________________________________ > Virtuoso-users mailing list > Virtuoso-users@lists.sourceforge.net > <mailto:Virtuoso-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/virtuoso-users > <https://lists.sourceforge.net/lists/listinfo/virtuoso-users> > > ------------------------------------------------------------------------------ > _______________________________________________ > Virtuoso-users mailing list > Virtuoso-users@lists.sourceforge.net > <mailto:Virtuoso-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/virtuoso-users > <https://lists.sourceforge.net/lists/listinfo/virtuoso-users>
------------------------------------------------------------------------------
_______________________________________________ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users