| 1. | Some tasks and containers provide additional break conditions for setting breakpoints
一些任务和容器包括用于设置断点的其他中断条件。 |
| 2. | The hit count type , or the rule that specifies when the break condition triggers the breakpoint
命中计数类型，或指定中断条件何时触发断点的规则。 |
| 3. | The hit count , or the maximum number of times that a break condition occurs before the execution is suspended
命中计数，即执行挂起之前中断条件出现的最大次数。 |
| 4. | Inside a loop , verify that the loop s break condition compares the type of the current element and the type of the
，则应验证循环的中断条件是否对当前元素的类型与 |
| 5. | Breakpoints can be enabled at the package level , or at the level of the individual component
断点可在包级或单个组件级启用。如果在任务或容器级上启用中断条件，则在 |
| 6. | For example , a package might have breakpoints set on the break conditions that occur when the package receives the
例如，一个包可能有对中断条件设置的断点（当包接收到 |
| 7. | Integration services provides ten break conditions that you can enable on all tasks and containers
Integration services提供了十个可以在所有任务和容器上启用的中断条件。 |
| 8. | Event , run to the breakpoints in the script , and finally run to the break condition associated with the
事件相关联的中断条件处挂起执行，运行到脚本中的断点，并最终运行到与 |
| 9. | For example , if the type is " hit count equals " and the hit count is 5 , execution is suspended on the sixth occurrence of the break condition
例如，如果类型是“命中计数等于”并且命中计数是5 ，则在中断条件第六次出现时挂起执行。 |
| 10. | If break conditions are enabled at the task or container level , the breakpoint icon appears next to the task or container on the design surface of the
选项卡的设计图面上，相应的任务或容器旁边会显示断点图标。如果在包一级启用中断条件，则在 |
