Transfer and Server. Execute , see Sending Content to the Browser . When you declare a page to be transactional, any script commands and objects used on the page are run under the same transaction context. You must add the directive to each page that should be run under a transaction. The current transaction ends when the script finishes processing.
Most applications only require transaction context for certain operations.
For example, an airline site might use transactional scripts for ticket purchasing and seat assignments. All other scripts could be safely run without a transaction context. Because transactions should be used only for pages that need transaction processing, you cannot declare an application's Global.asa file as transactional. If a transaction is aborted, Component Services rolls back any changes made to resources that support transactions. Currently, only database servers fully support transactions because this data is the most critical to enterprise applications.