You can script out all your sp's and include the files in an SSMS project and then do Find and Replace against the scripts.

Before I answer your question I have a couple of suggestions. First you should not name user stored procedures with SP as the query optimizer will first look for...

Jason Whitney (11/25/2008)

---

Jack Corbett (11/25/2008)

---

...

Isn't it better to reward the thrifty instead of punishing them? What's better saving money or going back to the till for more later because...

william (11/25/2008)

---

A couple of things in your column deserve discussion, Steve.

First, you seem to discount the value of those "feel good" trips. From a purely pragmatic point of view, they...

I think I understand what you are looking for now. I do have a questions.

Your design allows for a many to many relationship between prop and item...

I think you understand my trigger better than I understand your design. Can you post the DDL for the 3 tables including the relationships like, itemproplink.prop_id = prop.prop_id ?

I did a simple test and the execution plans are the same with no apparent reference to the function or Output.

Hey Grant, any idea on performance impact of Scope_Identity vs. the Output clause? I would imagine that they are similar, but doesn't hurt to ask.

BOL is also available on the MS web site and, I believe, is downloadable on it's own. The OUTPUT clause goes after your INSERT. Like this:

[font="Courier New"]DECLARE @table(CustomerId...

You actually can't truncate a table that is a parent in a foreign key relationship even if there is no data in the child table. You either have to...

Here is an idea I'd do it if I were to do it in a trigger, which I wouldn't:

[font="Courier New"]CREATE TRIGGER ITEMPROPLINK_AFTDEL ON ITEMPROPLINK

AFTER DELETE

AS

BEGIN

   SET NOCOUNT ON...

In SQL Server the correct way to avoid orphaned rows is to use DRI (Declared Referential Integrity) also known as foreign key constraints. When using DRI you can define...

Well the tables are listed alphabetically so you can use that to figure out where it should be. Also as you select a table the column list changes so...

Any errors in the event log?

What account is the service set to run under?

I'm not sure why you would see such a difference when putting in a stored procedure although the most likely issue is parameter sniffing. You can look that up...