+ Post New Thread
Results 1 to 7 of 7
Windows Thread, Constant corruption of system MSSQL 2005 files in Technical; We have a server with a fairly standard Microsoft SQL 2005 SP3 install, for some reason the system SQL files ...
  1. #1

    Join Date
    Jan 2007
    Posts
    980
    Thank Post
    12
    Thanked 48 Times in 28 Posts
    Rep Power
    25

    Constant corruption of system MSSQL 2005 files

    We have a server with a fairly standard Microsoft SQL 2005 SP3 install, for some reason the system SQL files (i.e. master, msdb etc etc) seem to be corrupting at random under very little load.

    I'm starting to think it could be disk hardware failure, is there a disk checking utility that works on Intel server motherboards and Samsung HD501LJ drives?

  2. #2

    AngryTechnician's Avatar
    Join Date
    Oct 2008
    Posts
    3,730
    Thank Post
    698
    Thanked 1,212 Times in 761 Posts
    Rep Power
    394
    I assume you've already used chkdsk? You could also try Samsung's ESTool, not sure how well it plays with RAID though.

  3. #3

    Join Date
    Jan 2007
    Posts
    980
    Thank Post
    12
    Thanked 48 Times in 28 Posts
    Rep Power
    25
    Quote Originally Posted by AngryTechnician View Post
    I assume you've already used chkdsk? You could also try Samsung's ESTool, not sure how well it plays with RAID though.
    Did try chkdsk a few weeks ago, may try it again. Just running the intensive scan on ESTool now, for some reason my boot CD didn't like the server but the ISO off the Samsung site works fine

    For the record we have uninstalled and reinstalled SQL 3 - 5 times over the past few weeks and it always seems to end up back at the corrupt file issue! Also we can't use the command prompt to put the Sql Server service in single user mode when we want to because it complains our SQL install is either corrupt or has been tampered with!

  4. #4
    tarquel's Avatar
    Join Date
    Jun 2005
    Location
    Powys, Mid-Wales, UK
    Posts
    1,740
    Thank Post
    13
    Thanked 45 Times in 35 Posts
    Rep Power
    29
    Few thoughts...

    Does the server do anything else other than have a SQL 2005 install on it? i.e. running any other software on it, etc?

    While its likely to be disc related, have you checked and/or swapped out the RAM modules? Even slightly duff RAM sticks could be causing it to corrupt etc IMO.

    Regards
    Nath.

  5. Thanks to tarquel from:

    AngryTechnician (22nd September 2009)

  6. #5

    AngryTechnician's Avatar
    Join Date
    Oct 2008
    Posts
    3,730
    Thank Post
    698
    Thanked 1,212 Times in 761 Posts
    Rep Power
    394
    Excellent advice, beat me right to it when I was thinking again about this earlier. Faulty RAM could absolutely cause this. The free version of memtest86 would be my recommendation for testing that.

  7. #6

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,572 Times in 1,252 Posts
    Rep Power
    340
    I suspect it's either a combination of hard drive and memory or just one of the two. If you've run Scandisk and it comes back clean, then I suspect memory is the culprit. I presume you're using ECC memory? This is a must in any server.

  8. #7

    Join Date
    Jan 2007
    Posts
    980
    Thank Post
    12
    Thanked 48 Times in 28 Posts
    Rep Power
    25
    Quote Originally Posted by googlemad View Post
    Did try chkdsk a few weeks ago, may try it again. Just running the intensive scan on ESTool now, for some reason my boot CD didn't like the server but the ISO off the Samsung site works fine

    For the record we have uninstalled and reinstalled SQL 3 - 5 times over the past few weeks and it always seems to end up back at the corrupt file issue! Also we can't use the command prompt to put the Sql Server service in single user mode when we want to because it complains our SQL install is either corrupt or has been tampered with!
    We rebuilt the server using a brand new hard drive and Server 2003 install, was getting the same 'Corrupt / Tampered' error on a fresh SQL install!

    What Microsoft helpfully failed to point out is when using the SQLSERVR.EXE command line utility you need to do sqlservr.exe -s <instancename> for it to work if using anything other than a Default Named Instance!!! (Finally found it on Google but how does 'Your SQL Install is corrupt / tampered with' error help me!

SHARE:
+ Post New Thread

Similar Threads

  1. offline synchronized files cause system to freeze
    By mpatsb in forum Network and Classroom Management
    Replies: 20
    Last Post: 12th February 2009, 11:39 AM
  2. Local system permissions on SQL Server 2005
    By powdarrmonkey in forum Coding
    Replies: 2
    Last Post: 30th September 2008, 12:38 PM
  3. System state and Files backup
    By trickstar in forum Windows
    Replies: 9
    Last Post: 13th March 2008, 11:26 AM
  4. SIMS on MSSQL 2005
    By AlexB in forum MIS Systems
    Replies: 9
    Last Post: 7th November 2007, 09:20 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •