>If not, the best thing may simply be to make the field a UNIQUE key (if
>the SQL Server of the Beast will allow it) and /try/ to insert the
>record. If you can't, don't.
Or even better if you can check for existence using something equivalent
to:
If not exists (select uniquevalue from thetable
Craig Cardimon wrote:
I am working with huge ASCII text files and large text fields.
Define "huge" and "large"
As needs and wants have changed, I will be reprocessing data we have
already gone through to see if more records can be extracted.
I will need to compare strings to ensure that records I
[EMAIL PROTECTED] wrote:
> I am working with huge ASCII text files and large text fields.
>
> As needs and wants have changed, I will be reprocessing data we have
> already gone through to see if more records can be extracted.
>
> I will need to compare strings to ensure that records I am inserti
> -Original Message-
> From: Craig Cardimon [mailto:[EMAIL PROTECTED]
> I will need to compare strings to ensure that records I am inserting
> into our SQL Sever 2000 database are not duplicates of records already
> there.
why don't you just put a constraint in the relevant tables, and m
I am working with huge ASCII text files and large text fields.
As needs and wants have changed, I will be reprocessing data we have
already gone through to see if more records can be extracted.
I will need to compare strings to ensure that records I am inserting
into our SQL Sever 2000 database
