Nope. SQL Server will never "Not log". The log is provided as ameans of
maintaining consitency in the database. I believe Oracle has the option to
abandon this.
Your best bets to keep the log low
1. Simple Recovery Mode (Understand the implications)
2. Limit the amount of indexes
3. Fetch and insert sizes (Last tab of datapump task. This along with #1
will let the log breathe)
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.allisonmitchell.com - Expert SQL Server Consultancy.
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Russ" <anonymous (AT) discussions (DOT) microsoft.com> wrote
Quote:
I have a dts that basically performs a transformation from Access tables
to SQL Tables. Daily there are mulitple Access tapbles with between 2k - 5k
|
records in each. What is happening is that the .log file is contstantly
growing. Is there a way to disable the logging of these transactions. Is
that the switch under the DTS properties/advanced/use transactions?