Hello michael,
You cannot completely remove logging. What you can do though is use SIMPLE
as your recovery model as you are doing. This will not stop the transaction
log expanding when doing something like an INSERT or an UPDATE if you choose
to do these operations as one batch. The lazy writer will simply not be
able to write what is in the log to disk for you. What you can do to help
it along though is to do the operations in smaller batches this way the lazy
writer can get in there and flush dirty pages to disk.
Allan
Quote:
when doing my wash of data I have no use of the transaction log. I
take a backup before start of washing and alway wash all data.
So what I would prefer was to disable the transaction logging. I
already chose Simple as option of the database but that doesn't
prevent the file from growing.
It makes it easier to shrink the physical file, though...
So my question is whether it is possible to change a setting more on
the database or use a t-sql command before initiating my queries that
will prevent the transaction log from growing. |