如果应用程序能继续向下运行并且恢复到以前，就可以幸运地忽略故障发生前正在做的事情，因为中间件和数据库保证了数据的完整性。
If the application does go down and come back up, it can be blissfully ignorant of what it was doing before the failure, since the middleware and databases guarantee data integrity.
所以正在建立的连接的类型无关紧要，因为数据库的启动将恢复事务日志中所有未完成的事务，以便保持数据完整性。
So the type of connection being established does not matter because the act of booting the database will recover any incomplete transactions in the transaction log in order to preserve data integrity.
由于您正在使用您的应用程序的云版本，您可以删除并恢复您的数据库，这不会引起用户的抱怨。
Because you're using the cloud version of your application, you can delete and restore your database without any users complaining.
如果您对现有数据库启用前滚恢复，将主日志的数量更改成当前正在使用的主日志和辅助日志的数量总和，再加1。
If you are enabling an existing database for roll-forward recovery, change the number of primary logs to the sum of the number of primary and secondary logs you are currently using, plus 1.
备份数据库与正在使用的数据库具有相同的参数状态，这样在数据库故障中，只需作必须的最少恢复，最大限度地缩短了恢复时间。
Backup database and the database that using have same parameter state, such is in in database breakdown, need only must restore the least, utmost ground shortened restore time.
备份数据库与正在使用的数据库具有相同的参数状态，这样在数据库故障中，只需作必须的最少恢复，最大限度地缩短了恢复时间。
Backup database and the database that using have same parameter state, such is in in database breakdown, need only must restore the least, utmost ground shortened restore time.
应用推荐