If you had a primary key (even a surrogate one) this would be very easy. Why no primary key? Your table is really a HEAP with all the performance disadvantages that entailsCam you add a surrogate primary key?This will *work* but it's not prettyDECLARE @foo TABLE ( CName NVARCHAR(255) , CDesg NVARCHAR(255) , Cdept NVARCHAR(255) , CGender NVARCHAR(255) , CResult NVARCHAR(255) )DECLARE @bar TABLE ( CName NVARCHAR(255) , CDesg NVARCHAR(255) , Cdept NVARCHAR(255) , CGender NVARCHAR(255) , CResult NVARCHAR(255) )-- Data SetINSERT @foo SELECT 'test', 'te', 'kpt', 'M', 'yes'UNION ALL SELECT 'test', 'te', 'kpt', 'M', 'yes'UNION ALL SELECT 'pos', 'jp', 'obm', 'F', 'yes'UNION ALL SELECT 'Uni', 'lk', 'jhp', 'F', 'yes'SELECT * FROM @foo--Populate @barINSERT @bar SELECT DISTINCT * FROM @foo--wipe @fooDELETE FROM @foo--Populate @fooINSERT @foo SELECT * FROM @barSELECT * FROM @foo
Charlie===============================================================Msg 3903, Level 16, State 1, Line 1736The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION