You could upload it to the SQL box via FTP (or any machine the SQL box can
see) and trigger it that way - then the file does not need to be named the
same each time giving a little more flexibility.

If you mean BCP then I would advise against it :-) it is not logged.







"This e-mail is from Reed Exhibitions (Oriel House, 26 The Quadrant,
Richmond, Surrey, TW9 1DL, United Kingdom), a division of Reed Business,
Registered in England, Number 678540.  It contains information which is
confidential and may also be privileged.  It is for the exclusive use of the
intended recipient(s).  If you are not the intended recipient(s) please note
that any form of distribution, copying or use of this communication or the
information in it is strictly prohibited and may be unlawful.  If you have
received this communication in error please return it to the sender or call
our switchboard on +44 (0) 20 89107910.  The opinions expressed within this
communication are not necessarily those expressed by Reed Exhibitions." 
Visit our website at http://www.reedexpo.com

-----Original Message-----
From: Rick Root <[EMAIL PROTECTED]>
To: CF-Talk <[email protected]>
Sent: Wed Jul 26 22:26:26 2006
Subject: Re: reading large text file

In addition to doing DTS, you could just use a bulk insert... as long as 
the SQL Server account has privileges to do so, coldfusion can run a 
bulk insert query from <cfquery> ... only thing is the text file has to 
be accessible by the SQL Server (ie, usually residing on the SQL Server 
machine itself)

Rick



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four 
times a year.
http://www.fusionauthority.com/quarterly

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:247835
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to