Actually Botchief's MSSQL feature seems to have a big issue on MSSQL. On a failed transaction, it does not reset its internal transaction status, attemping to reuse an already failed, but commited transaction - rendering the MSSQL module completely unusable, even when changing to another user, it tries to use the same, not available transaction.
SQL Server Version 10.50.400
Could you please show me the screenshot of your command settings? Because it is helpful to us.
Thank you.
Very simple to verify the issue...
A suggestion I have - especially when it comes to Databases - the variables should be more strictly typed. Not directly related to the issue here, but in general - working with quite "open" variables on very strongly typed systems (like MS SQL) will lead to more issues than actually rely on strong typing.
