|
|
| 71. | %ls statement not allowed within multi-statement transaction. |
| 在多语句事务内不允许使用 %1! 语句。 |
|
|
| | |
| 72. | Maximum time delta between transaction begin and commit |
| 事务开始与提交之间的最大时间增量 |
|
|
| | |
| 73. | The transaction list for '%1' is already displayed in another window. |
| %1 的事务列表已显示在其他窗口中。对于指定的服务器，仅能打开一个事务列表窗口。 |
|
|
| | |
| 74. | Specify the network share where the transaction logs are created. |
| 指定在其中创建事务日志的网络共享。 |
|
|
| | |
| 75. | Average time delta between transaction begin and commit |
| 事务开始与提交之间的平均时间增量 |
|
|
| | |
| 76. | A transaction log file's physical file name cannot be changed once the transaction log file has been |
| 事务日志文件创建后，其物理文件名即无法更改。 |
|
|
| | |
| 77. | The TCAP transaction sublayer is consists of the following transaction types which define operation associations |
| TCAP 事务处理子层由下列定义操作组合的事务类型组成： |
|
|
| | |
| 78. | Transaction cannot have multiple recordsets with this cursor type. |
| 在事务中，不能存在此游标类型的多记录集。更改游标类型、提交事务，或关闭其中一记录集。 |
|
|
| | |
| 79. | This phase is called transaction recovery. |
| SMON自动回滚失败的事务。这个阶段叫事务恢复。 |
|
|
| | |
| 80. | Analogous to EJB transaction attribute of the same name. |
| 和EJB中定义的同名事务属性类似。 |
|
|
| | |