sql database suspect

hi,
Our DB admin jst quit - evrything was workin fine so far up until this morning. The main database has a suspect next to it and i have no clue as to wut should be done and how can it be recovered. any help will be appreciated.
johny911Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Anthony PerkinsCommented:
First step is start reading up on your disaster recovery plan, which should include location of all recent backups.
0
EugeneZ ZhitomirskySQL SERVER EXPERTCommented:
what is your sql server version\edition?

if it is 2000:
solution from:
http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/Q_21439242.html?sfQueryTermInfo=1+eugenez+suspect

if sql server 2005:

--thanks to Bob Ward from Microsoft
-- Note that SSMS shows suspect_db SUSPECT
-- and this command will fail
--
use suspect_db
go
--
-- Let's go see what the ERRORLOG says before
-- we decide to just repair it
--
use master
go
alter database suspect_db set emergency
go
use suspect_db
go
--
-- CHECKDB is clean. Why suspect?
--
dbcc checkdb(suspect_db)
go
--
-- I've got a row in this table. Is that ok?
--
select * from mytab
go
--
-- Go ahead and repair it
--
use master
go
alter database suspect_db set single_user
go
dbcc checkdb(suspect_db, repair_allow_data_loss)
go
alter database suspect_db set multi_user
go

alter database suspect_db set online
go

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Anthony PerkinsCommented:
Second step you need to do and BEFORE you attempt to remedy anything is to determine the reason it became Suspect.  That includes looking at the SQL Server Error Logs and Windows Events.
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

James MurrellProduct SpecialistCommented:
0
johny911Author Commented:
is there a step by step procedure that i can follow? i do know that the system was backed up last night -there is no disaster recovery program other than the backup.
0
johny911Author Commented:
in the most recent SQL server logs it states 'by passin the recovery of the database cuz its marked suspect'
0
johny911Author Commented:
"The LSN (261:507:1) passed to log scan in database 'database' is invalid.." - that is another error i found
0
abhijit_kCommented:
Use DBCC REBUILDLOG COMMAND
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.