February 3, 2010 at 10:48 pm
Rebooted the environment so that both machines would have MSSQL released at the same time ..and of course its still there.. =[ I am truely at a loss and you have been very helpful.
Any more ideas... also i am giving you all the information i can... lol and if things slip my mind its not on purpose
ok ok one more idea before i call it a night.... heheh
-D-
DHeath
February 3, 2010 at 10:52 pm
Here is the best way to think about it. We are volunteers with our own jobs that need to be done. We don't have access to your systems. When you sit down to post a problem, think about those things and ask yourself, what would I need to know to help some one in a similar situation.
Once you start thinking like that, you should find it easier to provide what is needed to get the help you are looking for. It helps me when I ask for help. But you are correct, some things may still slip your mind as I'm sure it does mine.
I must thank you for being very responsive and helpful in your replies. That doesn't happen all the time.
February 3, 2010 at 11:01 pm
How about...
Take a Trans log backup on the second server.
Kill all the processes on the database.
Try restoring the Trans log backup with recovery on the first and the OLD server where the DB is in readonly.
SO that the DB comes live.
hope yo u have tried, but still..
Just a thought..
Sorry if i screwed wrongly...
Cheers,
- Win.
" Have a great day "
February 3, 2010 at 11:02 pm
And i also appreciate the help you have offered as well...This is just one of those "freek" situations that even when i tried to recreate it all things worked and no issues..so now i am having to try and resolve this one. I know when i try to post a situation its usually complex and then to add my lack of skills to explain..hehehe makes it even worse..o well the obsticles we have... lol
I will check back in the morning and see if anyone has found the solution ..i even have Microsoft trying to figure it as well..and right now they are not sure what to do either..so its a challenge.
I will try to make it a point to volunteer more of my time here but i then start enjoying SQL on my time off by being here... hehehe
Once again thanks for your time... YOU ROCK!!!! as does everyone else that has taken a second to even start reading this thread and even more kudos to those that get this far.
-D-
DHeath
February 3, 2010 at 11:05 pm
Post a reply when you fix this with steps if you can...
It might help others in future...
Cheers,
- Win.
" Have a great day "
February 3, 2010 at 11:20 pm
Winlet...your idea is excellent... i have already tried to do the Tlogs recover and all and no luck as the database is in use and the logs are not found by the server itself but like i said... I do have a working database of the exact data on the server.. i just need to get rid of this corrupt situation i have here.
And yes IF/WHEN i get a solution (please dont let it be server rebuild) i will update this post. Who knows maybe MS can give me the know how tomorrow.. hehehe
-D-
DHeath
February 3, 2010 at 11:37 pm
We can always hope. Good luck, as I am currently out of ideas. Plus, it's time for bed.
February 4, 2010 at 4:10 am
Can you elaborate what exactly the status of the DB is now and error you are getting, after all tries ???
Cheers,
- Win.
" Have a great day "
February 4, 2010 at 6:28 am
The state has not changed after all these tries and 24+ hrs later...(In Recovery/Read-Only).
Thanks for asking and your time
-D-
DHeath
February 4, 2010 at 1:44 pm
Have you tried setting the database into single user or offline, then dropping it?
ALTER DATABASE {yourdatabasehere} SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
GO
DROP DATABASE {yourdatabasehere};
GO
Or - Offline:
ALTER DATABASE {yourdatabasehere} SET OFFLINE WITH ROLLBACK IMMEDIATE;
GO
DROP DATABASE {yourdatabasehere};
GO
Either of those should work and allow you to drop that database.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
February 4, 2010 at 1:50 pm
Just noticed that the database is read only - so, first thing you need to do is get the database out of read only mode, then you can drop it.
ALTER DATABASE {yourdatabasehere} SET READ_WRITE;
GO
Now, you should be able to drop the database. If not, take the database offline and then drop.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
February 4, 2010 at 1:51 pm
UPDATE :
The database has been removed FINALLY!!!!... that is the good... the bad is i think it was just time that fixed it =[ The reason i say this is that early this morning myself and y coworker just started back at scratch and when we right clicked on the database name it gave us the opportunity to delete the database and datafiles. This is something that was tried many many times and ususally we would get that the database was in use and not allow this. Well to make a long story short everything is "A" ok. The sad thing is i dont know what fixed it and IF i ever get back in this situation(hopefully i wont and neither will any one else) there is nothing i can say "fixed" it. I think it was jsut a conglomerant of everything tried and at some point either the system released the files gave way...
I must let all know i appreciate EVERY second and response that was given and this is why SSC ROCKS!!!!!!!!
-D-
big kudos Lynn for hanging in and doing all you did.. =]
DHeath
Viewing 12 posts - 31 through 41 (of 41 total)
You must be logged in to reply to this topic. Login to reply