Post reply

invalid entry in sysobject preventing constraint creation

  • January 4, 2008 at 2:36 pm

    #121758

    Somehow I have an object cataloged in sysobjects under a file that does not exist. Suspect bad upgrade. How do you get the entry out of sysobjects?

  • January 5, 2008 at 3:29 am

    #765058

    I suspect that may be tricky as I've found trying to do anything with system tables almost impossible with sql 2005 , not always for the best. The DAC will give you better access but no graphical view!

    you may be able to still call drop object commands to remove it.

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

  • January 5, 2008 at 7:48 am

    #765069

    There is no way to update any of the system tables in SQL 2005.

    Try running a DBCC CheckDB on that database. I think checkDB checks the system catalogs, so may pick it up and tell you how to fix it

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • January 7, 2008 at 10:31 am

    #765437

    Thanks for the responses, unfortunately I didn't get a chance to try them as we ended up restoring the system and starting the upgrade again. This time all went well.

  • January 7, 2008 at 2:30 pm

    #765515

    Well, that was the brute force solution...

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply