Hello All,I have a confusion on using "Try-Catch" and "Rollback" on stored procedures.In general as understand if we have a stored procedure that does operations like inserts or updates, it makes perfect sense to use a rollback operation within a transaction.So, if something goes wrong and the transaction does not complete, all changes will be reverted and an error description will be thrown for example.Nevertheless, does using a rollback within a try catch statement, make sense in a [b]read only[/b] stored procedure, that practically executes some dynamic sql just to select data from some tables?I have around 100 Stored procedures, all of them read only. Today a colleague suggested adding try-catch blocks with rollback to all of them. But since they are just selecting data, I don't see a clear benefit of doing so, compared to the hassle of changing such a big number of SP's..Any thoughts welcome!Thank you.Serlal
↧