sql server transaction log reader

An overview By default, the SQL Server Agent creates error logs to record warnings and errors. The following warnings and errors are displayed in the log: A warning message that provides information about a potential problem, such as "a job is deleted when it is executed." Error messages, which typically require system administrator intervention, such as "Unab

Myth #19: TRUNCATE TABLE operations are not logged to the log Error Actions in the user table are recorded in the log. The only operation in SQL Server that is not logged to the log is row versioning in tempdb. The Truncate table statement deletes all data from the enti

(Customer information) --Shrink the specified data file, 1 is the file number, you can query through this statement: SELECT * FROM Sysfiles DBCC Shrinkfile (1) 4. In order to maximize the reduction of log files (if it is SQL 7.0, this step can only be done in Query Analyzer) A. Detaching a database: Enterprise Manager--server--database--right key--detach databas

step can only be done in Query Analyzer). A. Detach database: Enterprise Manager--server--database--right----detach database. B. Delete log files on my computer. C. Additional database: Enterprise Manager--server--database------Append database. This method will generate a new log with a size of only 500 KB or in c

the Options page, select: Except for the transaction log, where the other red box parcels are strongly recommended. and ensure that the database does not have someone else on the connection, because the tail of the backup log causes the database to be in a restored state, deny connections to other sessions, and cannot be backed up without disconnecting other con

set your database attributes to the standard mode. The operation method is the same as the first one, because logs are often an important basis for restoring the database in case of exceptions.However, the following statement can be executed on the server in the query Analyzer:CopyCodeThe Code is as follows: Dump transaction [jc8] With no_logBackup log [jc8] Wit

server| Solution | data | database The first is to provide a complex method for compressing logs and database files as follows: 1. Empty logDUMP TRANSACTION Library name with NO_LOG2. Truncate the transaction log:BACKUP LOG database name with NO_LOG3. Shrink the database file (if not compressed, the database file will

AccessThe operation is very simple. The specific steps are as follows: Open your mdb database, tools> Database Utilities> compress and restore the database (c )...SQL SERVER In general, the contraction of the SQL database does not greatly reduce the size of the database. Its main function is to shrink the log size. Thi

SQL Server database log backup and recovery steps SQL Server database log backup and recovery steps -- Create a Test DatabaseCreate database Db GO -- Back up the database Backup database Db to disk = 'C: \ db. Bak' WITH FORMA

always closed), normal after the big file can be deleted.Of course, the best way is to plan in advance, set up, add a job schedule, so that will automatically back up, shrinkage and the like, control in a certain size range.After learning, the other simple processing methods:1: Empty the LogDUMP TRANSACTION Library name with NO_LOG2: Shrink LogEnterprise Manager--Right click on the database you want to shrink--all tasks--shrink the database--Shrink t

Common logs for diagnosing SQL Server problems There are two main: (1) Windows Event Log (2) SQL Server ErrorLog 1, Windows Event Log event logs As a windows open and Managed service program, Windows logs information about th

"Problem scene" has a database, its name is called Cnblogstext, the log file occupies 23G hard disk space, and the transaction log has been truncated (Truncate), the actual log content is very small, 1G are not. 23G of space only put 1G log, like a villa with a pet, too extr