William Vaughn
11/8/2007 6:31:00 PM
Ah, wait. You never bulk copy directly into a production table--import to a
working table such as EvilData.
Once in the server, run a stored procedure to validate, massage and do your
code-based magic as you insert the rows into the production table(s).
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------
"Michael Bray" <mbray@ctiusa_dot_com> wrote in message
news:Xns99E0DEFF4C6A4mabarayactiusacom@207.46.248.16...
> =?Utf-8?B?S2VycnkgTW9vcm1hbg==?=
> <KerryMoorman@discussions.microsoft.com> wrote in
> news:D73C84A9-7869-417C-9F68-3E61D432FDC6@microsoft.com:
>
>> Michael,
>>
>> SQLBulkCopy is the tool you need to use for this application.
>>
>
> Can it support logical operations? The data that I am importing doesn't
> import directly. For example, if a particular column is Y then I want to
> set a 'bit' field true, otherwise false. Another example, a column might
> have 'N/A' in which case I would want the field to be set NULL.
>
> -mdb