sql server clear transaction log

Copy Code code as follows: DECLARE @name VARCHAR (25) DECLARE @SQL VARCHAR (1000) DECLARE @logid INT DECLARE sysdatabase_name CURSOR for SELECT name from master.dbo.sysdatabases OPEN Sysdatabase_name FETCH NEXT from Sysdatabase_name into @name While @ @FETCH_STATUS = 0 BEGIN IF (@name not in (' xxx ')-database name that does not require log shrinkage BEGIN

Tags: base upd src inf paid erro values CLU pointOriginal: SQL Server log file structure and error operation data retrievalI. Overview In SQL Server, there are data files. mdf and log files. ldf, the

Tags: style blog color ar sp div on log bsSelect * fromBankInsert intoBankValues(10000)Insert intoBankValues(20000)--Open a transactionbegin Tran--Defining temporary variablesDeclare @num int = 0;UpdateBankSetBalance=Balance-15000 whereId=1Set @num = @num + @ @error;--Previous statement error countUpdateBankSetBalance=Balance+15000 whereId=2Set @num = @num + @ @error;if @num 0 begin--rolling back a transactionrollback TranEndElse begin--Commit a

References: Http://msdn.microsoft.com/en-us/library/ms187103.aspxOverview SQL Server uses log transmission, you can automatically back up transaction logs in the "primary database" on the "primary server" instance to one or more "secondary databases" on the separate "seconda

In the query analyzer, perform the following three steps in sequence, where databasename is your database file name1. Clear logs: Dump transaction databasename with no_log 2. truncate transaction logs: backup log databasename with no_log 3. shrink the database: DBCC shrinkdatabase (databasename) --/////////////////////

In the query analyzer, perform the following three steps in sequence, where databasename is your database file name 1. Clear logs: dump transaction databasename WITH NO_LOG 2. truncate transaction logs: backup log databasename WITH NO_LOG 3. shrink the database: dbcc shrinkdatabase (databasename) --///////////////////

1. Delete Log 2. Clear the Log 3. Shrinking database files 4. truncating the transaction log The performance of the database is the DBA need to focus on, the increase of log files seriously affect the performance

I have read many articles about transactions before this article. Most of them are profound and difficult for beginners to understand. Here we will use a very simple example to explain the application of transactions. First, create a temporary table and fill in some data. Create Table # tab (ID int, country nvarchar (10), popu INT) insert into # tab values (1, 'China', '123 ') insert into # tab values (2, 'America ', '000000') insert into # tab values (3, 'Canada', '000000') insert into # tab v

Deleting a message will cascade the reply information. At this time, we need to use the transaction, as shown in the following SQLCopy codeThe Code is as follows:Alter procedure [dbo]. [proc_tb_leaveword_delete](@ LeavewordID INT,@ Record TINYINT OUTPUT)ASBEGINBEGIN TRYBEGIN TRANSACTIONDelete from tb_leavewordID WHERE leavewordID = @ leavewordIDDelete from tb_reply WHERE leavewordID = @ leavewordIDSET @ record = 0 -- SuccessCOMMIT TRANSACTIONEND TRYBE

Label:This article was reproduced from: http://www.cnblogs.com/sky_Great/archive/2013/01/09/2852417.html SQL Normal Transaction begin TransactionTRDeclare @error int; Set @error=0; Select * fromCar_brandSet @error=@error+@ @ERROR Select 1/0 Set @error=@error+@ @ERROR Select * from AreaSet @error=@error+@ @ERROR Print 'I have executed!' Set @error=@error+@ @ERROR Print '@ @error:'+cas