<scotty@amnet.net.au> wrote in message
news:ff2ce15a-acd1-4fe4-a77a-ad44e106411e@q1g2000prf.googlegroups.com...
> Hi all
>
> If this is impossible, I will be gobsmacked.
>
> Can someone *please* tell me how to disable transaction logging in
> tempdb? We have absolutely zero interest in point in time recovery on
> this DB, and all the transaction log is doing is causing us
> performance and space issues.
>
> Please? Anybody?
>

You also has a followup reply with:

"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......"

I'm confused as to whether your issue is with logging in tempdb or your main
database or both. Apparently it is with both?

Your ASE version might be helpful to readers of this forum. In general, the
newer the version the more likely that a new feature may be helpful. Or
that we notice issues with the release that you are using (i.e., recommend a
downgrade or upgrade).

Does the application use "create #table ... and insert into #table ..."? Or
"select ... into #table"? I'm a little bit rusty with the various ASE
releases but the latter should be minimally logged whereas the former is
logged. It might be that a bunch of consecutive "select into"s and "drop
previous #table" may help although the code could become somewhat
convoluted. (Instead of "update #table1" do "select into #table2 ...
including computations".)

There have been various threads at ISUG about the benefits of seperating the
system/default/log segments for tempdb as well as having seperate caches for
system/default and log segements of tempdb. Although you may not care about
recoverability of your main database not seperating the log onto its own
devices can impede performance.