sql server clear transaction log

SQL ServerAndOracleFeatures of medium Transaction Processing 1Transaction Features (AcidAttribute) NAtomicAtomicityThat is, the transaction should be taken as a unit of work, and the transaction is processed completely. All the work is either saved in the database or completely rolled back, but not retained.. NCon

(X) lock to update. A deadlock occurs because two transactions are converted to exclusive (X) locks, and each transaction waits for another transaction to release the shared-mode lock.To avoid this potential deadlock problem, use the update (U) lock. Only one transaction at a time can obtain an update (U) lock on the resource. If the

SQL server lock mechanism (I)-Overview (lock types and ranges) SQL SERVER lock mechanism (II)-Overview (Lock compatibility and lockable resources) This article introduces the locking mechanism of SQL SERVER (iii) -- Overview (loc

transaction log, instead of backing up (copying) the log to the backup device. Because the logs are not copied, you do not need to specify the backup device when using truncate_only. For example, the syntax for using the truncate_only option to back up the transaction logs of the primary database is as follows:Backup

exclusive (X) lock to update. A deadlock occurs because two transactions are converted to exclusive (X) locks, and each transaction waits for another transaction to release the shared-mode lock.To avoid this potential deadlock problem, use the update (U) lock. Only one transaction at a time can obtain an update (U) lock on the resource. If the

selected as a simple model)This option is often set to true when the checkpoint command is executed if the transaction log file exceeds 70% of its size to clear its contents in the development databaseAuto ShrinkPeriodically check the database when the unused space for a database file or log file exceeds 25% of its si

After careful study, it is still a bit complicated to find the explicit transaction (display transaction) inside SQL Server. Here are some summaries:Commit TRANSACTION commits all nested transaction modifications. However, if the

As we know, the SQL Server transaction log is used primarily to record changes made to the database by all transactions, and if the system fails, it becomes the only source of the latest data. Log operations often have the following applications: One, the

Label:Original: http://www.cnblogs.com/yun_shuai/archive/2010/09/20/1831546.html /*1. Minor error (Severity level 0-10): By default, the client program is not sent an error message to continue working. Which means it can't be caught in a catch.2. Medium error (Severity level 11-19): Can be caught (either in T-SQL or in the client program)3. Critical error (Severity level 20-25): SQL

.*/Cause of the problem:The "xact_abort" switch specifies whether SQL Server automatically rolls back to the current transaction when a run-time error occurs for the Transact-SQL statement. When SET Xact_abort is on, the entire transaction terminates and rolls back if the Tr

Source: http://untitled.spaces.live.com/Blog/cns! 86b82838704e0d5a! 819. Entry Transaction isolation level is a basic concept in a database. Why is there a transaction isolation level? What transaction isolation levels are implemented on SQL server? The premise of