Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. I can not drop table after upgrading to sql 2008 r2 from sql 2005

I can not drop table after upgrading to sql 2008 r2 from sql 2005

Scheduled Pinned Locked Moved Database
databasesql-serversysadminhelp
4 Posts 2 Posters 1 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Y Offline
    Y Offline
    yousefshokati
    wrote on last edited by
    #1

    Hi. I had a database that was working very well in sql server 2005. I upgraded my SQL to SQL 2008 R2 . After upgrading , I wanted to drop one of my tables. But i could not. It gives this error No catalog entry found for partition ID 281474980577280 in database 5. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption I don't know what to do

    P 1 Reply Last reply
    0
    • Y yousefshokati

      Hi. I had a database that was working very well in sql server 2005. I upgraded my SQL to SQL 2008 R2 . After upgrading , I wanted to drop one of my tables. But i could not. It gives this error No catalog entry found for partition ID 281474980577280 in database 5. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption I don't know what to do

      P Offline
      P Offline
      Pete OHanlon
      wrote on last edited by
      #2

      Just as a wild guess, but why not run DBCC CHECKDB?

      *pre-emptive celebratory nipple tassle jiggle* - Sean Ewington

      "Mind bleach! Send me mind bleach!" - Nagy Vilmos

      CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

      Y 1 Reply Last reply
      0
      • P Pete OHanlon

        Just as a wild guess, but why not run DBCC CHECKDB?

        *pre-emptive celebratory nipple tassle jiggle* - Sean Ewington

        "Mind bleach! Send me mind bleach!" - Nagy Vilmos

        CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

        Y Offline
        Y Offline
        yousefshokati
        wrote on last edited by
        #3

        I did it but it gave me again the same error

        P 1 Reply Last reply
        0
        • Y yousefshokati

          I did it but it gave me again the same error

          P Offline
          P Offline
          Pete OHanlon
          wrote on last edited by
          #4

          The easiest option would be to open the instance up in SQL Server 2005 from your last working backup. If this is not an option for you. you might want to read this[^] article. Warning! Anything you do here is at your own risk - if you don't have backups to go back to, you could be well and truly stuffed.

          *pre-emptive celebratory nipple tassle jiggle* - Sean Ewington

          "Mind bleach! Send me mind bleach!" - Nagy Vilmos

          CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups