No you can't.

Insert, then select.

Please post some sample data and the exact required result after the transfer has been made.  That way we can all be sure of the problems you fear to encounter.

That's why i said runt he restore on ANOTHER SERVER, or as another db if the server option is not available.  Then reimport the table.

Do you have all the latest patches for XP, Access and mdac?

Good points Jeff.  But I'm curious, what is the real overhead of an instead of trigger?  I'm sure there is one, but I wouldn't expect it to be as bad...

Please do not cross post, we check all questions regardless of the board.

Continue this thread here : http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=357&messageid=391847

Actually, why not run that code on a dev server.  Then script the table, recreate it in production and import the data from dev?

Talking about a comment or the article?

Possible... I didn't think this one through before posting .

In theory...

what about if a team plays against hitself?

Well there's always those 2 commands

net stop server

net start server.

But that might cause some minor problems .

Not always.  But when there is the inner join usually wins.  It's also more obvious of what you want to do and it also avoids hidden cross joins!!!  which can...

Can you create a small app that will execute as SA (or any minumum privilege to put it back online)?  MS Access will most likely be enough as they only...

EXEC sp_changeobjectowner 'ObjSQL', 'prg'

Just generate the code with a select on the information schema tables.

What he said .