Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How does the Migration Workbench handle the @@TRANCOUNT global variable?

global migration workbench
0
Posted

How does the Migration Workbench handle the @@TRANCOUNT global variable?

0

You can set the emulation of the @@TRANCOUNT global variable on or off by choosing the Object > Parse option within the Migration Workbench. When you have selected the parser option, each reference to the @@TRANCOUNT variable within the SQL Server stored procedure is replaced with a reference to the omwb_emulation.globalPkg.trancount packaged variable within the destination Oracle database. However, if you do not select the Emulate @@TRANCOUNT variable parser option, the @@TRANCOUNT variable is treated as a normal variable. The following example compares the SQL Server statement with the equivalent Oracle Server statement when you select the Emulated @@TRANCOUNT variable option in the parse option. SQL Server Statement IF @@trancount > 100 Oracle Statement IF omwb_emulation.globalPkg.trancount > 100 Note: You access the emulated variable through the typical user.package.variable format. The SQL Server statements that affect the value of the @@TRANCOUNT variable, for example BEGIN TRANS

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123