Slice does not require any database schema change.
Slice不要求任何的数据库模式的变更。
You'd also capture any change to undo any schema changes.
还要捕获任何变化，从而能够取消模式变化。
And if the code version causing the schema change is in any way deficient, the change must often be rolled back by hand.
如果造成模式变化的代码版本仍然处在不完善的状态，那么经常必须手工回退变化。
Merge the schema change script into the mainline as 01.00.0046, and fix the 2.0 baseline script to incorporate this change.
将数据库变更脚本合并到当前主线版本01.00.0046的脚本中，并在基线版本2.0中进行相应的修复来处理这一变更；
For some XML configuration files, there is no XSL file because there is no schema change for them between versions 2.0.1 and 2.5.
对有些XML配置文件，没有XSL文件，因为2.0.1和2.5版本之间没有模式变化。
Each team member can now easily assess which parts of their application would get impacted by a proposed schema change by the DBA.
现在，每个团队成员能够轻松地评估他们的应用程序的哪些部分将受到DBA提出的模式更改的影响。
Figure 2: By associating actions to high level groups, you can add "team-specific" subgroups to the action without making a schema change.
图2：通过同高级别的群体联合行动，您能够将“团队特定的”子群体添加到行动中，而且不需要对计划做出改变。
Meanwhile, data update and schema change are possible to coexist under the concurrent environment which brings about many problems to view maintenance.
在并发环境下，数据更新和模式更新极有可能同时存在，这对视图维护工作带来极大的困难。
The new online schema change features in DB2 9.7 help DBAs and application developers significantly reduce the database downtime associated with planned outages.
DB 2 9.7中的新的在线模式修改特性帮助DBA和应用程序开发人员显著减少与计划内宕机有关的数据库宕机。
In order to use the examples that demonstrate the new online schema change capabilities in DB2, you first need to create a sample database that will serve as the required infrastructure.
要使用演示DB2的新的在线模式变更功能的示例，首先需要创建一个用作必要基础设施的样例数据库。
Is a customer reporting a bug on build 3.1.5.6723? Pull the source code tagged or labeled with that version number and run the baseline, then all schema change scripts included in the tag.
如果客户报告了一个关于build 3.1.5.6723的bug，那么，你所需要做的就是获取相应版本标号或标记过的源码，然后运行这一基线和这一标记下所有的数据库变更脚本。
What if you now need a new communication mechanism or change to a data schema?
如果你现在需要一个新的通信机制或者数据模式变化了呢？
The problem here is that the order of elements in the schema must not change from one conversion to another.
这里的问题是模式中的元素顺序在转换成另一个模式时不一定改变。
For those cases where you cannot change the schema, JAXB provides another solution.
对于那些无法更改架构的情况，JAXB提供了另一种解决方案。
You could change the default schema here if you used separate schemas for testing and deployment.
如果您要使用单独的测试和部署方案，那么您可以在这里改变默认的方案。
While we prefer our solution, that solution requires you to change the XML schema.
尽管我们喜欢这个解决办法，但该办法需要更改x ML架构。
You can choose either to change the schema, or disable the JAX-RPC data binding and integrate alternate data binding technologies.
您要么可以选择改变这个模式，要么禁止JAX-RPC数据绑定和整合候补数据绑定技术。
You can choose either to change the schema, or disable the JAX-RPC data binding and integrate alternate data binding technologies.
您要么可以选择改变这个模式，要么禁止JAX - RPC数据绑定和整合候补数据绑定技术。
Based on that taxonomy, we overview the impact of each change on schema validation.
按照这种分类，说明每种变化对模式验证的影响。
As a developer, I have no need to update or change a schema, much less deploy one!
作为开发人员，我无须更新或更改架构，更谈不上部署架构了！
The schema cannot change and the database cannot move without changes to all applications.
在没有改变的情况下，模式不能改变且数据库不能移植到所有的应用程序中。
Note that I'm not implying that you can't change a schema; I'm just saying that change is more easily accommodated without one.
注意，我并非暗示不能更改架构；我只是说，可以更轻松地适应变化。
You've taken a deep dive into a single migration but still haven't created a single change in the schema.
现在已经深入研究了单一迁移，但是还没有在模式中进行变化。
You could argue that a database schema doesn't change very often, but the fact is that it can and does change.
你可能争辩说数据库的Schema不会经常改变，但事实却恰恰相反。
To resolve the errors, change the location of the schema Department.xsd.
要解决这些错误，请更改架构Department . xsd的位置。
If you need to change a name after you have started work on your schema, make sure that everyone is aware of that change.
在您开始处理一个方案之后，您需要更改一个名字，那么您要确定每个人都意识到了您所做的更改。
This upgrade does not require any change in application code or the database schema.
这种升级不需要在应用程序代码或数据库模式方面做任何更改。
It meant that every time your service data structures changed the schema would also change, and clients would need to regenerate their code using the new schema.
它意味着，每次你的服务数据结构的改变都会引起模式的改变，客户端将需要使用新的模式重新生成它们的代码。
Which development schema was the change made in?
变更是在哪一个开发方案中作出的？
The first time that you cannot answer the question "In which version of which development schema was change X made?"
当您首次不能回答问题“更改x是在开发方案的哪一个版本之中完成的呢？”
应用推荐