If you do updates through stored procedures, make the change there. If you have updates through T-SQL and want to be sure they are captured, use a trigger.

Yes, goes as a named instance.

I've seen something similar when the secure channel between teh SQL server and the domain controller is broken. Can't authenticate. Is this a new user? Or someone that hasn't logged...

Thanks for the replies and it's interesting to read.

Luke! Send me some SQL-Beer samples and I'll get them reviewed for the site! Always on the lookout for new and interesting...

Congrats on the MS job. Let us know how it goes if you can.

I've tended to use different accounts for each server. Since you rarely set them up, it works well. Store the passwords in Password Safe or something similar and then yo...

If you have multiple statements in the task, they're each separate. When you run the proc, the temp table exists, but it should go out of scope when the proc...

You could use a subquery.

Delete from a

where a.pk not in (select b.pk from b where a.xx = b.xx)

Something like that. You'd have to work out the joins you...

Yes, use the column name instead of the *

Which indexes?

Please don't cross post.

This is answered here: http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=334004

#temp tables are not necessarily memory resident either. They both can go to disk.

These are inserts the same as any other table. No order is every guarenteed. You do not know when things are inserted, unless you are timestamping, and then you only...

I agree with Nigel. Old backups, or the T-log.

Also, do you drop the tables before doing the transfer? If so, you might be stuck.

Are these end users?

I'd avoid giving this to end users. Reporting Services, with the Report Builder, is supposed to address a lot of these concerns.