Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Truncate Logs

Status
Not open for further replies.

LtMsMgc

Programmer
Aug 21, 2002
1
US
I have an alert that runs a job when ever a specific log files grows to a certain size and it is working fine. Every time the job runs it writes an error message to the windows application log in Event Viewer. The job is set up to write to application log when the job succeeds, which it does.I have checked the job and it shows that it has completed successfully. Here is an example of the messages I get in the application log.

ERROR

Event
Date: 8/21/2002 Source: MSSQLSERVER
Time: 9:09 Catagory (6)
Type: Error Event ID: 17055


Description:
18278:
Database log truncated: Database: DBName.


That error is followed up by:

INFORMATION:
Date: 08/21/2002 Source: SQLSERVERAGEMT
Time: 9:09 Catagorey: Job Engine
Type: Information EnventID: 208


Description:
SQL Server Schedluled Job Truncate DBName Log
Status Succedded .... The Job Succeeded.....


So again why would it write an error message to the application log and then write the succeeded message. I know the second message is the option I have checked say write to log when succeeded.


Anyone have any ideas??????
 
This is because before making truncate full must have backup previous, or a differential at least where to be able to apply the transactions. If the truncated one cannot obtain a coherence does not take place, marking like correct job, and jobs not taken effect by the execution from the same one. sureto have the last installed Service pack

Regards
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top