Michael Peppler
Sybase Consulting
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
Sybase on Linux FAQ
Sybperl FAQ
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: "Lisa, Thomas P" <thomas dot p dot lisa at ssmb dot com>
Subject: RE: bcp and select, not the same time?
Date: Jul 30 1999 9:31PM

If you're bcping back into an existing table AND that table has
one or more indexes or triggers, the bcp will generate log entries.
Non-logged bcps ("fast bcp") require the absence of any indexes
and triggers. This is per the Sybase Adaptive Server Utility Programs

Tom Lisa

> ----------
> From: 	Robert Lang[]
> Reply To:
> Sent: 	Friday, July 30, 1999 3:45 PM
> To: 	SybPerl Discussion List
> Subject: 	RE: bcp and select, not the same time?
> Personally, I'd go with opening a temporary file, 
> Process the input records one-by-one writing out bcp records to the
> temporary file
> Close the File and then bcp that into the target.
> The advantages of this approach are low memory consumption  (only a single
> input record in memory at one time.)
> better speed  (simple disk read/writes to the local filesystem will be
> faster than bcp'ing into any table)
> less work on the Sybase Server.  (The select into will generate log
> entries,
> while the bcp will not.)
> a single database connection
> no chance the process deadlocking itself.
> The only downside that I can see is if you run out of disk space, you're
> hosed.
> Regards,
> Robert Lang
> -----Original Message-----
> From: WORENKLEIN, David, GCM [mailto:David.Worenklein@GCM.COM]
> Sent: Friday, July 30, 1999 8:42 AM
> To: SybPerl Discussion List
> Subject: RE: bcp and select, not the same time?
> You can bcp into a temp table.  Then, when you're done, you can
> insert into real_table
> select * from temp_table
> -----Original Message-----
> From: []
> Sent: Friday, July 30, 1999 8:16 AM
> To: SybPerl Discussion List
> Subject: Re: bcp and select, not the same time?
> David:
> Thanks for writing. You are right,  my program is locking itself up. I was
> selecting
> and bcp in from/to the same table.   I have never thought that bcp_sendrow
> would
> lock the data page.  I thought bcp_batch is the time when data page get 
> locked.
> The sybook has the following words on bcp_sendrow:
> "rows are permanently saved in SQL Server only when the user calls
> bcp_batch or bcp_done".   I should have read between lines.
> I now have to abandon the bcp idea for what I am doing.  This is bad!
> Thanks again for help
> Heather