Limitations of the Database Submitted by the Log

In SQL 2005, what things should you not do with the database on which logging is enabled (and works under the full version)?

I understand that scheduling additional backups of the transaction log elsewhere will result in failure of the log delivery (since the full chain of logs no longer reaches the secondary server).

I also collect that the Truncate table is in order with log delivery (starting with Sql 2000).

Are there any other actions / commands that should be avoided?

edit: for example, a crash in database shrinking or log shrinking?

+3
source share
2 answers

. - Log Shipping, , .

, , Ad-Hoc, , - , , SQL Server, . LS_Backup. LSN.

, , , .

, :

SQL Server, , , SQL Server .

, , .

, , SQL Server SID, , .

, . .

+6

/ / , , . , , :

BACKUP LOG WITH TRUNCATE_ONLY

( , )

, REINDEXES , .

+2

Source: https://habr.com/ru/post/1707852/


All Articles