您要查找的是不是:
- Log shipping does not guarantee against data loss. 日志传送不保证不丢失数据。
- This section lists this kind of data loss errors. 此节列出这类数据丢失错误。
- Now, what about the data loss issue itself? 现在,关于数据丢失问题本身,该怎么办呢?
- Misuse of this cmdlet will cause data loss. 错误地使用此cmdlet将导致数据丢失。
- Retain file formats with no data loss. 保留文件格式,没有数据丢失。
- Otherwise, you may experience data loss and unpredictable behavior. 否则,您可能会遇到数据丢失和不可预知的行为。
- These repairs can be performed without risk of data loss. 执行这些修复时不会有丢失数据的危险。
- This data loss will occur the next time the user logs off. 在下次用户注销时将发生此数据丢失。
- This data loss will occur the next time you log off. 在下次您注销时将发生此数据丢失。
- Data loss is frequently minimal; however, it may be catastrophic. 数据丢失通常影响不大,不过也可能具有灾难性影响。
- It is essential to understand that forcing service can cause data loss. 一定要注意,强制服务可能会造成数据丢失。
- Widening conversions always succeed at run time and never incur data loss. 扩大转换在运行时始终是成功的,且从不会导致数据丢失。
- Some time after the Log_2 log backup, data loss occurs in the database. 在Log_2日志备份后的某个时间,数据库出现数据丢失。
- Clear the Block incremental deployment if data loss might occur check box. 清除“如果可能发生数据丢失则阻止增量部署”复选框。
- Clarkson has now apologised and admitted that data loss is a serious issue. 克拉克森现在已道歉,并承认数据丢失是一个严重的问题。
- This device does not allow write caching to be disabled. A power outage or equipment failure might result in data loss or corruption. 这个设备不允许停用写入缓存。停电或仪器故障可能会导致数据遗失或损坏。
- Because Abandon Changes involves significant data loss, the user should be protected with clear warning signs. 因为这种功能会可能造成数据大量丢失,因此应该用清晰的警报标志保护用户。
- Most commercial environments consider it good enough if a high-availability system fails over in 3 or 4 seconds with no data loss. 多数商用系统认为,如果一个高可用性系统失效3或4秒而无数据丢失,就够好的了。
- Therefore, full or incremental populations take longer to complete, but there will not be any data loss. 因此,完成完全填充或增量填充需要更长的时间,但是不会丢失任何数据。
- Will the replication solution prevent all possibility of data loss short of simultaneous outage at all sites? 复制解决方案是否可以避免所有可能的数据丢失(除了所有站点同时中断服务之外)?