Those are just statistics that the server is using for the queries (or used only once). The index tuning wizard could point out some new indexes to use. ...

The problem is per column update... not by tsql batch.

While it can't be used here it could certainly help him someday.

Check the books online in the trigger section. The only way you can access deleted data is in a trigger in the Deleted table. After that you need...

check out this section of the books online for a solution :

UPDATE, UPDATE (described)

I already answered here :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=291&messageid=276417

I have a simple math solution for you :

2 servers = 2 times the costs

2 servers also means that the data has to be written twice instead of one...

The best solution would be to create 4 separate procs to handle all possible cases (actually 1 per table combinaison). Have that proc call the appropriate procedure. If...

And may I ask why you are using dynamic sql for this???

Why exactly do you want to be able to do this?

I rarely see the need (valid) for this in a production environement.

I want to drop a table.

But I want to delete data.

That's the just way I hear it... but now he knows he can do both.

Another solution.. Generate the drop commands with a select query :

select 'Drop table dbo.' + Name as DropCommand from dbo.SysObjects where XType = 'U' and name like 'T%'

Once you...

Run the query in query analyser. Click on the results pane.

Then go in the file menu and hit save.. If you have correctly clicked on the results pane, then...

Don't know him... maybe I'll ask my ubiquitus spook.

You could always have 2 sets of data.  On one server you would have the active data (let's say the last 4-6 months depending on your requirements).  Then you'd have...

How about??

CREATE PROCEDURE dbo.GetMember @ad_id as varchar(20)

AS

SELECT DISTINCT members.ad_id FROM departments WHERE departments.mgr_ad_id = @ad_id