Update transactions have no results.

Thanks Jay; I know that update statements have no results but the transaction also contains a select statement which does not seem to execute . If I put the select statement first then it executes it and it gives me the result  but it does not execute the Update statement.

I would like both executed, ideally in this order : update first and then SELECT and then get the results of the select statement

If I use the transaction as it is in SQL server management studio I executes the update statement and then gives me the result of the select statement

The same SQL transaction used through the CS0120 executes only the first statement in the transaction.

Thanks Jay; I know that update statements have no results but the transaction also contains a select statement which does not seem to execute . If I put the select statement first then it executes it and it gives me the result  but it does not execute the Update statement.

I would like both executed, ideally in this order : update first and then SELECT and then get the results of the select statement

If I use the transaction as it is in SQL server management studio I executes the update statement and then gives me the result of the select statement

The same SQL transaction used through the CS0120 executes only the first statement in the transaction.

Yes, CS0120 has lots of limits.  For your example I would probably have added a simple trigger to the Sage table.