Personally, Nadya, I find your "need" to "optimize" every piece of code that you come across to be REPUGNANT in the extreme.
I think it is fine, well and good that you want to review/optimize any code, actually, but it is your penchant to so cavalierly expose anyone ELSE'S code TO THE WORLD, with your silly comments about it, that is sooooo irritatingly GAUCHE (second time to use that word today)!

You've noted in prior messages that your "colleagues" of that time did NOT appreciate your wanting to "help" them 'correct' their poor coding techniques. Why do you think that total strangers would feel any different?????

This has gotten RIDICULOUS and I HOPE THAT YOU WILL STOP DOING THIS IMMEDIATELY.

Jim


>Hi everybody,
>
>I was trying to use Steve Saywer's/Doug Henning's RI builder. The idea of using just one simple procedure instead of lots of multiple convoluted procedures is very appealing. I made bunch of modifications in Doug's code trying to optimize this procedure. Perhaps, I made it worse than before. The code originally used Select-SQL for restrict triggers (insert/update/delete). I switched to IndexSeek. The code also looped through array of relationships, I changed it slightly to use ASCAN. In my opinion these changes should have speed the procedure up. Anyway, comparing with the old native RI it seems to be much slower. I'm thinking that I may use KEYMATCH instead of INDEXSEEK. Would it make it run faster? Bellow is the code as I have right now. I would appreciate if you can point me to the problematic pieces. I also tried to incorporate Glen's idea of save/restore environment logic. However, it adds a layer of complexity, which is probably undesired...
<snip>