Power failure using simple mode transaction Log

Any comments about what happens when we get a power failure using simple mode
transaction Log?
I had 3 Power failure and there has not been any problems with the data.
The auto recuperation informs that 5343 rows where commited and 0 rolled back.
Can I expect this behaviour in the future? (another power failure).
Note that I have a UPS, but I didn't have time to shutdown properly.
Run DBCC CHECKDB if you haven't already.
You should configure your UPS to shutdown the server automatically after N
minutes of power failure.
David Portas
SQL Server MVP
|||If you have hardware write cache, you need to make sure it is properly backed up, and follows a
certain set of rules. If it does, the database should not go corrupt because of a power failure. If
you don't have hardware write cache, then you probably don't have battery backup and you can see a
torn page. See http://www.microsoft.com/technet/pro...lIObasics.mspx for
full information.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"juan carlos via droptable.com" <forum@.droptable.com> wrote in message
news:51122050ED1E0@.droptable.com...
> Any comments about what happens when we get a power failure using simple mode
> transaction Log?
> I had 3 Power failure and there has not been any problems with the data.
> The auto recuperation informs that 5343 rows where commited and 0 rolled back.
>
> Can I expect this behaviour in the future? (another power failure).
> Note that I have a UPS, but I didn't have time to shutdown properly.

Power failure using simple mode transaction Log

Any comments about what happens when we get a power failure using simple mod
e
transaction Log?
I had 3 Power failure and there has not been any problems with the data.
The auto recuperation informs that 5343 rows where commited and 0 rolled bac
k.
Can I expect this behaviour in the future? (another power failure).
Note that I have a UPS, but I didn't have time to shutdown properly.Run DBCC CHECKDB if you haven't already.
You should configure your UPS to shutdown the server automatically after N
minutes of power failure.
David Portas
SQL Server MVP
--|||If you have hardware write cache, you need to make sure it is properly backe
d up, and follows a
certain set of rules. If it does, the database should not go corrupt because
of a power failure. If
you don't have hardware write cache, then you probably don't have battery ba
ckup and you can see a
torn page. See http://www.microsoft.com/technet/pr...>
Obasics.mspx for
full information.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"juan carlos via droptable.com" <forum@.droptable.com> wrote in message
news:51122050ED1E0@.droptable.com...
> Any comments about what happens when we get a power failure using simple m
ode
> transaction Log?
> I had 3 Power failure and there has not been any problems with the data.
> The auto recuperation informs that 5343 rows where commited and 0 rolled b
ack.
>
> Can I expect this behaviour in the future? (another power failure).
> Note that I have a UPS, but I didn't have time to shutdown properly.