Sorry, didn't mean to rant on you .

You have nothing to fear on that matter.

The only slight ill effect is that when you drop/recreate a proc, the dependencies to other objects are lost because they are deleted...

Seems to me like the problem comes from the reporting side of the process. Can you go into debug mode to see why it's being called so often?

This is one case where the wizards of enterprise manager can be usefull... Just create a new view and use the wizard to connect the tables (if you don't already...

I still preffer no damage at all if possible.

I think I would just have restore without its approval (under tableName_restored), then showed him he was working for nothing

Had to do the same here with a linked server... Optimized it as much as I could, but I'm stuck at 20 secs. But since it's used only 2-3...

Sorry, missed that part.

No other idea then. Maybe Jonathan Stokes can help you.

That's what I was figuring... maybe with an exists/join operation on the other table.

But there might be something else in the proc that we're missing. She's setting a lot...

No need to use dynamic sql here, no need for temp table either. Also, this doesn't work for all the tables in the same query and finally this solution...

Nice trick .

Basically sql server has to materialize the view into a pseudo table (like a derived table) to access the data. If you're using too many nested views ,assuming you're...

Maybe you need something like this.

Update Main set Col = 'old' from dbo.OldTable Main inner join

(

Select O.Oldid from OldDb.dbo.OldTable O inner join

NewDB.dbo.NewTable N on O. Oldid = N.NewId)...

If it works, go for it.

If you need performance later on. Maybe you can create a computed column (index) that does the case work, and you'd still have pretty...

Is there a possibility that bad data is occuring in the 5th 1000 rows set??

Maybe there's a difference in the datatypes of the import table and a truncatation or impossible...

Would be easy to write client side. It would only take to while loops... And would be much simpler than any tsql method out there (even if you just...