Shulou(Shulou.com)05/31 Report--

This article focuses on "what are the dangers of the use of dump transaction with no_log", interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn what are the dangers of using dump transaction with no_log.

But what exactly does "last resort" mean? What happens when you use this command? Which command should you use to replace it? Finally, if this command is so problematic, why does Sybase provide it?

Sybase Technical support recommends that you dump your transaction log on a regular basis. You must decide how to use dump based on the amount of diary activity in your database and the size of your database. Some places dump transaction; monthly and some places dump transaction every night.

Note: if you are running SQL Server10.0, you can use sp_thresholdaction to automatically dump tran; before there is a shortage of space, and Backup Server will ensure that the task will not be suspended while dump is in progress. Please find more detailed information in your SQL Server reference manual. The rest of this article will apply to areas where you are running SQL Server prior to system 10.

If you have never dump transaction, transactionlog will eventually be full. SQLServer uses log (logs) for recovery purposes. When the log is full, the server will stop things from continuing because the server will not be able to write these things to the log, and the server will not be able to run most dump tran commands because SQL Server also needs to record these commands in the log.

This is why no_log can be executed when other dump tran commands cannot be executed. But think about the environment in which dump transaction with no_log is designed and executed. All do not do concurrency test.

If you use dump transaction with no_log when changes to the database occur, you run the risk of the entire database crashing. In most cases, they are reflected as 813 or 605 errors. In order to delete inactive parts of the transaction log when the database is modified, you can use dump transaction with trancate_only. This command is written into transaction log, and it also does unwanted concurrency checks. Both commands have warnings related to them, which you will see in the command reference manual. Make sure you understand these warnings and instructions before using any of these commands. Syase provides dump transaction with no_log to deal with some very urgent situations. To ensure the consistency of your database as much as possible, you should use it as a "last resort".

At this point, I believe you have a deeper understanding of "what are the dangers of the use of dump transaction with no_log?" you might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.