At first, I think you are right. Setting the 'select into/bulkcopy' option 
will allow nonlogged bulkcopy, whild turning it off will prevent you from 
running 'select into' and 'bulk insert' operations ( ver 7.0 or less, not 
true in 2000). 

Your co-workers are somehow right too.  Having this option set, you won't 
be able to do the log backup anymore, which may lead to problems in 
recovery.  I don't know any bug about 'select into/bulkcopy' option.  
Please share it if anyone has related knowledge or experience. 

The solution is simple.  This option, and trunc. log option, is and should 
always be enabled for tempdb.   So in your application, you can 
always 'select into' or insert a temp table without logging.


> Hi All,
> 
> There is a debate going on here at work about the Select Into/Bulk Copy
> option on a database and I would appreciate the input of all of you 
experts
> out there, since I am just learning about SQL.
> 
> A Co-worker and I are under the impression (From reading books) that the
> Select Into/Bulk Copy option on a database will allow you to do Select
> Into's to create tables without creating entries in to the Transaction
> log while still allowing other transactions the ability to log.  We are
> trying to prevent the Transaction log from filling up with unnecessary
> entries.
> 
> There are other people here at work that state (from what they have heard
> and not from actual experience) that the Select Into/Bulk Copy option
> creates an unstable environment when it is enabled.   They claim that 
there
> are bugs concerning this Select Into option,  because some transactions 
> that
> should produce entries in the log do not when this option is enabled.
> 
> We are running Microsoft Server SQL 6.5 at this time.  I don't know if 
the
> problem they are talking about really exists, or is it just a 6.5 issue 
if
> it does exist.
> 
> In a nut shell we are creating tables that will be used for reports and
> then discarded. We can at times be dealing with several hundred thousand
> rows at a time and we didn't want any entries going to the log by using 
the
> Create Table / Insert, so we had decided to use the Select Into option. 
If
> we can't use the Select Into, could we use the Temp DB area to do some of
> our table processing without creating entries to the Transaction log?
> 
> Thanks,
> Wade