Environment versions
Network:
Windows 2008 Server
>Good morning,
>
>I have a function in my application that is used in many, many places. The function receives a SQL Select expression and executes it using a Macro substitution. Once in a while I get an error from customers where the execution of SQL Select fails. I am thinking that I should wrap this macro substitution call in TRY/CATCH. My concern is that I think I read something here that TRY/CATCH slows down the execution. If so, is it still (in your opinion) worth a slight delay in execution to have TRY/CATCH around such a frequently used function?
>
Yes. And I doubt there is much performance penalty unless you have a ton of logic in the Catch block.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only