"Mike Labosh" wrote:

> In my application, I have an ADO.NET DataTable whose schema is the same as
> this table:
>
> CREATE TABLE dbo.CMRPhone (
> CLMRKey INT NOT NULL,
> PhoneNumber NVARCHAR(40) NOT NULL
> )
>
> The PK of the table is a composite of both columns.
>
> The items in the ADO.NET DataTable may or may not have duplicates. I am
> using an ADO.NET SqlDataAdapter's Update method to insert records into the
> db table. Internally, the SqlDataAdapter iterates over the items in my
> DataTable and calls my insert sp once for each record, so the SP must be
> phrased to insert one record, given the two parameters:
>
> CREATE PROCEDURE dbo.LoadCMRPhones (
> @clmrKey INT,
> @phoneNumber NVARCHAR(40)
> ) AS
> INSERT INTO CMRPhone
> SELECT @clmrKey, @phoneNumber
> WHERE NOT EXISTS (
> SELECT @clmrKey, @phoneNumber
> FROM CMRPhone
> )
> GO
>
> But I don't like using sub-selects. Anyone know of a more efficient way of
> phrasing this insert?
>
> --
> Peace & happy computing,
>
> Mike Labosh, MCSD
>
> "Mr. McKittrick, after very careful consideration, I have
> come to the conclusion that this new system SUCKS."
> -- General Barringer, "War Games"
>
>