June 14, 2011 at 2:22 am
hi all,
Ive just taken over the "dba" role in our shop so first thing i did was do a search for all the SQL boxs. On my travels ive found a windows Server 2000 running SQL 2000.
I rdp onto the server and low and behold. An error log is on the screen saying that the application log is full. So i save the logs to file and clear. 2 hours later is full again.
The error is always the same:
Event ID: 17052
Error 0 Severity 19 State 0
language_exec: Process 52 generated n access violation. SQL Server is terminating this process.
Any ideas whats up with this error? If its coursing major troubles to the data?
Also what tasks should i set to on the SQL Box. Its basically been left to run and run for apparently 5 years with no one looking at it as its worked.
I see auto shrink is on and i see that no page currption is on. Should that be the first task?!
Thanks for any help on either problem!
S
June 17, 2011 at 1:47 am
You may check for the details at http://www.eventid.net/display.asp?eventid=17052&eventno=551&source=MSSQLServer&phase=1.
I got the error too, about two months ago. Just found it was an old instance without SP4. After installing SP4 everything went ok.
June 17, 2011 at 7:38 am
Found this to be a good checklist for inheriting db servers and a "primer of database maintenance best-practices for all the involuntary DBAs".
http://technet.microsoft.com/en-us/magazine/2008.08.database.aspx
_____________________________________________________________________
- Nate
June 17, 2011 at 9:29 am
If it is at all possible I would apply the latest SP to the instance (so long as it does not interfere with any 3rd party applications using the data). Second, turn off the Auto-shrink. There are numerous articles here that explain why.
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply