On Apr 8, 8:54 pm, sco...@amnet.net.au wrote:
> On Apr 9, 10:41 am, Manish Negandhi <negandhi.man...@gmail.com> wrote:
>
> > in time recovery, to reduce tempdb log size you can execute dump
> > transaction process with no_log in loop which will truncate log as
> > often as *possible* .
>
> Thanks for the response!
>
> Will no_log dump the transaction log of current sessions?
>
> The main issue we have is we have several processes that do an
> extremely large amount of work in tempdb, but we do not wish to retain
> the ability to rollback the main database (not tempdb). So our
> transaction log issues are from single processes......
>
> We could increase the size of the log again, but it all seems so
> fruitless when you care zero about the log.

dump tran can only truncate the log up to the beginning of the oldest
open transaction.

You really cannot turn off logging in tempdb. really.

15.0.2 has a new feature that reduces the amount of logging i/o that
has to be done in tempdb, which will help with the performance side of
things. I believe we are also looking at ways to make tempdb(s)
purely memory-resident with no need for disks at all - but the feature
isn't here yet.

-bret