July 20, 2011 at 10:52 am
... unless one of the connection is not a sysadmin... or maybe the owner of the db is missing and that somehow blocks in the permissions.
July 20, 2011 at 10:54 am
Ninja's_RGR'us (7/20/2011)
... unless one of the connection is not a sysadmin... or maybe the owner of the db is missing and that somehow blocks in the permissions.
You have to be sysadmin to allow updates, so that's not 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
July 20, 2011 at 10:57 am
set allow updates on and then update sysdatabases and set the status to 36767 for that database.
Sorry if this is slightly off topic but isn't modifying system tables disabled in sql server 2005?
July 20, 2011 at 11:00 am
ZZartin (7/20/2011)
set allow updates on and then update sysdatabases and set the status to 36767 for that database.
Sorry if this is slightly off topic but isn't modifying system tables disabled in sql server 2005?
I was lost on this too untill I rescanned the whole thread. He's now trying to revive the DB to a sql 2000 instance after it failed on the new 2k5 one.
July 20, 2011 at 11:04 am
ZZartin (7/20/2011)
set allow updates on and then update sysdatabases and set the status to 36767 for that database.
Sorry if this is slightly off topic but isn't modifying system tables disabled in sql server 2005?
Yes, this is for the 2000 instance. The DB is 2000 and damaged, and it's a terrible idea to try and upgrade a damaged database and in this case it's failing.
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
July 20, 2011 at 11:55 am
GilaMonster (7/20/2011)
halifaxdal (7/20/2011)
The DB is in suspect modeI tried to set the emergency mode but failed
Hang on, you first said the DB is not in the list, then you said it's there in suspect mode. Which is it, it can't both not be there and be there in suspect?
I can't get into the server for now, too many connections, I will be able to get in once the admin kick off some for me.
Thank you again for the help.
As far as I remember, the database is not in the database list in EM or QA
Maybe I was refering to SQL 2005 when I said it's in suspect mode? Sorry for that if I can get in and confirm this.
July 20, 2011 at 11:56 am
GilaMonster (7/20/2011)
ZZartin (7/20/2011)
set allow updates on and then update sysdatabases and set the status to 36767 for that database.
Sorry if this is slightly off topic but isn't modifying system tables disabled in sql server 2005?
Yes, this is for the 2000 instance. The DB is 2000 and damaged, and it's a terrible idea to try and upgrade a damaged database and in this case it's failing.
Indeed yes, it is horrible plus painful, but I am glad you guys are helping me so I am not lonely. Thank you.
July 20, 2011 at 12:03 pm
Where are you located? Halifax??
July 20, 2011 at 12:12 pm
Ninja's_RGR'us (7/20/2011)
Where are you located? Halifax??
I were from there, are you there now? 🙂
Halifax in Canada, bot Britain.
July 20, 2011 at 12:19 pm
halifaxdal (7/20/2011)
Ninja's_RGR'us (7/20/2011)
Where are you located? Halifax??I were from there, are you there now? 🙂
Halifax in Canada, bot Britain.
Montreal.
July 20, 2011 at 12:49 pm
I just get in the server again, I swear I didn't see the database in the server list but now it appears there with Suspect status.
July 20, 2011 at 12:52 pm
And that's the 2000 server?
If so...
allow updates
update sysdatabases, set that DB's status to 32767
see if the DB can be queried.
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
July 20, 2011 at 12:53 pm
p.s. I seriously hope you're not doing this on a production server... It's insanely risky to do something like this on any server of importance.
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
July 20, 2011 at 12:53 pm
I run this: EXEC sp_resetstatus 'CheckListDB_Data'
it failed with:
Server: Msg 15010, Level 16, State 1, Procedure sp_resetstatus, Line 63
The database 'CheckListDB_Data' does not exist. Use sp_helpdb to show available databases.
July 20, 2011 at 12:54 pm
GilaMonster (7/20/2011)
p.s. I seriously hope you're not doing this on a production server... It's insanely risky to do something like this on any server of importance.
No, not prod
Viewing 15 posts - 31 through 45 (of 130 total)
You must be logged in to reply to this topic. Login to reply