Sure would be nice... but it doesn't take lon to build the query to fetch the info yourself.

I don't know about Yukon but :

exec sp_helpIndex 'Table_ViewName'

can get you started.

You pretty much said it yourself. The user needs to have direct access to the table if you make the select in dynamic sql. Try this to solve...

Well yes, but that takes a little work.. As I said a sp cannot be used in a straight select (you can't do Select * from exec dbo.MyProc). You can...

Well you can return a table in the sp just by doing a select. but the problem is that you can use a stored proc in an inner join....

That doesn't exist in sqlserver. You must use the profiler and filter for specific table names (never did that so I can't really help more than that).

whoa, nice catch there Nicholas.

quoting myself :

Exec () cannot resolve the statement in the parenthesis, you must set it into a variable and use it like so ...

I don't know why it's like...

Hehe something that seemed so simple turned out to be a real monster. It's a nice touch to see that I didn't account for empty non null names. ...

You can call any amount of stored procs while you're in a stored proc. The only thing you have to watch for is the nesting level.

call sp1 :...

Not confused at all. The trigger gives you access the to inserted and deleted tables. Those tables contain the information on all the lines that have been modified.

Inserted...

What article is this reffering to?

run both and see for yourself, just make sure you have all the indexes you need to run each query.

HTH.

Good luck.

hmm... I don't see a final calculation here :

'abcd' + Substring(name, 5, 999)

If there's a difference it must be so minute that I can't detect it with my test...