日志应该表明故障转移中使用的设备类型和位置。
The log should indicate the type and location of the device used in the failover.
使用大型视图可以在日志设备和视图重构目录中引起很大的资源问题。
The use of larger views can cause noticeable resource issues in the logging device and the view rebuild directory.
此方法的一个替代策略是使用磁盘镜像来对日志设备进行镜像。
An alternative strategy is to use disk mirroring to mirror the log device.
您甚至会怀疑即使事务数量很少，使用大型视图时事务日志设备也将成为性能的瓶颈。
You might suspect that the transaction logging device, even with the limited number of transactions, added a bottleneck to performance when large views were used.
而为联邦服务器日志使用不带写缓存的慢速设备(例如内部SCSI驱动器)，将增加启用F2PC的影响，因为附加的磁盘写要花费更长的时间。
Using slow devices without write caching for the federated server logs (such as internal SCSI drives) increases the impact of enabling F2PC because the additional disk writes take longer.
在理想情况，我们会希望将日志放在可靠的设备上，然后会使用singlewrite值。
Ideally we would want the log on a reliable device and then we could use a value of SingleWrite.
如果您与磁盘提供商的讨论结果满意，日志所在的设备能够确保写入完整性，则请使用SingleWrite来获得最佳的性能。
If you are satisfied as the result of a discussion with your disk provider that the device on which one which the log is located can assure write integrity, then use SingleWrite for best performance.
同样地，如果使用了任何其它设备，而且这个脚本如这里所描述的那样定制，那么这个门户服务器日志将指示相应的设备细节。
Similarly, if any other device is used and the script is customized as described here, the portal server logs will indicate the corresponding device details.
考虑为日志使用原始设备(raw device)，但是要注意，这样管理起来要更困难些。
Consider a raw device for the log, but note that management is more difficult.
考虑为日志使用原始设备(raw device)，但是要注意，这样管理起来要更困难些。
Consider a raw device for the log, but note that management is more difficult.
应用推荐