Are you talking about altering a definition? It doesn't pull back data but it does have to validate syntax, check permissions, validate against metadata etc, and more if you...

Can't you just comment everything in the body of the proc?

You should also ask the developer about permissions required by the app(s) as this will dictate how tightly you can secure the logins. There really shouldn't be any need...

If you only care about duplicates, and not whether the value changed or not, then something like this should work:

select itemID, recID

from mytable

group by itemID, recID

having count(1) > 1;

Not sure what you mean by "online restore" - users have to be out of the database for a log backup to be applied. There is an option "Disconnect...

Here is an example. Your case may be as simple as using a case statement in the select clause or it may involve multiple statements, but ultimately your source...

You are explicitly inserting a null value into that column (you are selecting rows where post_pd is null); the default will only apply if you don't insert explicitly to that...

I think the vendor needs to explain why they are using global temp tables; do they really understand how they work under the covers? I'm not sure how...

Can you post the table definition and a sample insert statement?

You should use an instead-of trigger; you can simply read the information from the inserted pseudo-table and insert it into your target table with any necessary modifications.

A better...

Your final solution will also depend on what you are trying to protect against, what downtime tolerance you have, and where the backup server(s) will be located. There is...

Something along these lines?

create procedure dostuff (@id1 int)

as

insert into table1 (id1, id2, text)

select @id1, max(id2) + 1, 'new' from table1 where id1 = @id1;

go

You need to identify what is causing your current performance problems, in order to determine the hardware required to remove any bottlenecks in your system. Once you have that...

Look for the section titled "Passive Servers and Failover Support" in this document.

http://www.microsoft.com/sqlserver/2005/en/us/Special-Considerations.aspx

It's hard to say without seeing any code or execution plans; if you can at least post the plans in .sqlplan format then we can see if anything obvious jumps...