Physical-log overflow when transaction logging is turned off
The physical log can overflow if you use simple large objects or smart large objects in a database with transaction logging turned off, as the following example shows.
When the database server processes simple large objects, each portion
of the simple large object that the database server stores on disk
can be logged separately, allowing the thread to exit the critical
sections of code between each portion. However, if logging is turned
off, the database server must carry out all operations on the simple
large object in one critical section. If the simple large object is
large and the physical log small, this scenario can cause the physical
logs to become full. If this situation occurs, the database server
sends the following message to the message log:
Physical log file overflow
The database server then initiates a shutdown. For the suggested corrective action, see your message log.