Unanswered: Avoiding transaction logging - at least reducing it
I have an application that uses work tables within an SP to generate a recordset output to the caller as the result of a search operation. The SP does not update the main database, and the results, although sizeable, are not saved.
Clearly I do not need to log the updates to the work tables. They start out empty and the contents could be discarded.
Does SQL Server recognise this and not log the updates to work tables? Is there any way I can indicate that a table is not significant and need not be logged at all?
Would it help to put the work tables in a separate database?