Select * from dbo.a where not exists (Select * from b where a.key = b.key)

or

Select * from a left outer join b on a.key = b.key where b.key is null

Yes create a temp table with identity(1,1), then insert the data to that table.  That'll create the unique id starting at one.  Also you can truncate that table and reseed...

Yes in that case... but it is a good reflex to try to convert the ors to something else and check for performance benefits

Agreed, if you are to transform the data, then transform it permanently and let the users see the final data, not something autogenerated at each run.

We already answered that question in the link I posted.  Also the question was to use ORs and not ANDs in the query .

Necessary only if your server uses unicode characters (like chinese).  But for global applications like sql server or access, they have to assume that the data can be unicode, that...

Is this an export / import task or will the application will have to be able to update those records (using the view as datasource), cause that ain't gonna be...

It converts the following text to unicode.

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=246782

That makes sens.  Why do you need to have a row id in the data?  There are ways to do it but they all are pretty costly.  Can the application...

What do you need to do exactly?  I have no (or too many) idea on how to help you!

That's easy.

It depends, always test .

Lol, that too... that's why I ask for a query plan for perf troubleshooting .

No need for that : all new posted get special attention, then active posts get special attention, then unanswered psot get recycled after 1 day.  Not to mention that all...

You can't.  that's why I redirect the thread to a single point.