Creating query without transaction log

Is there a way to avoid writing transaction log?
We are an OLAP shop and we do not necessarily need transaction log while querying a 33gb data
These type of queries capture an enormous amount of transaction log. If something happen, we can always restart the query, the log has minimal use for us. It is only filling up a huge amount of disk space. I truncate and shrink my databas
everytime I am close of running out of space to keep these log to the minimum
Any help is greatly appreciated
Thanks
TonyTony,
What is the recovery model?
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Tony - ICW Group" <tmangahas@.icwgroup.com> wrote in message
news:F343EA26-32F7-4456-A907-12EAF14E32DE@.microsoft.com...
> Is there a way to avoid writing transaction log?
> We are an OLAP shop and we do not necessarily need transaction log while
querying a 33gb data.
> These type of queries capture an enormous amount of transaction log. If
something happen, we can always restart the query, the log has minimal use
for us. It is only filling up a huge amount of disk space. I truncate and
shrink my database
> everytime I am close of running out of space to keep these log to the
minimum.
> Any help is greatly appreciated.
> Thanks,
> Tony|||Recovery model is Simple.|||I would try putting the database into Read-only mode.|||You need to find out what is causing the log to grow. SQL Server doesn't log SELECT statements, so it has to
be something else. Some operations can be done in minimal logging mode, but that is restrictive (bulk load
operations, SELECT INTO and index creations and rebuilds).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Tony - ICW Group" <tmangahas@.icwgroup.com> wrote in message
news:D5623FAA-EA57-4D43-BF91-8F8B866A90C8@.microsoft.com...
> Recovery model is Simple.