But what exactly does the "last move" mean? What happens when you use this command? So which command should you use instead? Finally, if this command is so problematic, why does Sybase provide it?
Sybase technical support recommends that you regularly dump your transaction log. You must determine the way to dump based on the amount of activity recorded in your database and the size of your database. Some places have monthly dump transactions; some places have nightly dump transactions.
Note: If you are running SQL Server 10.0, you can use sp_thresholdaction to automatically dump tran before space is short; in addition, Backup Server will ensure that the task will not be suspended when dump is in progress. Please get more detailed information in your SQL Server reference manual. The remainder of this article will apply to the realm of running SQL Server prior to System 10.
If you have never dump transaction, the transactionlog will eventually be full. SQLServer uses log (log) for recovery purposes. When the log is full, the server will stop the continued progress of things because the server will not be able to write these things into the log, and the server cannot run most dump tran commands, because SQL Server also needs to record these commands in the log.
This is why no_log is executable when other dump tran commands cannot be executed. But think about the environment in which dump transaction with no_log is designed to execute. All pairs do not perform concurrency checks.
If you use dump transaction with no_log when a modification to the database occurs, you will risk the entire database crashing. In most cases, they are reflected as 813 or 605 errors. To delete inactive parts of the transaction log when the database is modified, dump transaction with trancate_only can be used. When this command is written into transaction log, it also does not have concurrency checks. Both commands have warnings related to them, and you will see them 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 handle certain very urgent situations. To ensure consistency of your database, you should use it as your "last move".
Sybase technical support recommends that you regularly dump your transaction log. You must determine the way to dump based on the amount of activity recorded in your database and the size of your database. Some places have monthly dump transactions; some places have nightly dump transactions.
Note: If you are running SQL Server 10.0, you can use sp_thresholdaction to automatically dump tran before space is short; in addition, Backup Server will ensure that the task will not be suspended when dump is in progress. Please get more detailed information in your SQL Server reference manual. The remainder of this article will apply to the realm of running SQL Server prior to System 10.
If you have never dump transaction, the transactionlog will eventually be full. SQLServer uses log (log) for recovery purposes. When the log is full, the server will stop the continued progress of things because the server will not be able to write these things into the log, and the server cannot run most dump tran commands, because SQL Server also needs to record these commands in the log.
This is why no_log is executable when other dump tran commands cannot be executed. But think about the environment in which dump transaction with no_log is designed to execute. All pairs do not perform concurrency checks.
If you use dump transaction with no_log when a modification to the database occurs, you will risk the entire database crashing. In most cases, they are reflected as 813 or 605 errors. To delete inactive parts of the transaction log when the database is modified, dump transaction with trancate_only can be used. When this command is written into transaction log, it also does not have concurrency checks. Both commands have warnings related to them, and you will see them 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 handle certain very urgent situations. To ensure consistency of your database, you should use it as your "last move".