It's a long shot and it doesn't always work but I've had some success in the past with such a thing.
1. Make sure the database in question is detached and that the MDF file is in a safe place. "Safe place" means NOT on the drive that you normally store your MDF files, in this case.
2. Create a new database with the same name as the database in question. Note that the logical and physical file names should match the old ones.
3. Properly detach the new database.
4. Copy (not move) the old MDF file from Step 1 over the new MDF file created in Steps 2 and 3.
5. Try to reattach the new database.
It doesn't always work but the answer is always "No" unless you "ask".
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs