MS SQL Server :: DB Suspect Not Show In Sp

Show Suspect But Not Suspect
One of my database (name XYZ) shows suspect status in EM but when i try to dig further by running below query i get only "OK" ( see query)

SELECT [name],status, case status when (status & 32) then 'Loading'
           when (status & 32) then 'Loading'
           when (status & 64) then 'Pre Recovery'
           when (status & 128) then 'Recovering'
           when (status & 256) then 'Not recoverd'
           when (status & 512) then ' Offline'
           when (status & 1024) then ' Single user'
           when (status & 1024) then ' Read only'
           when (status & 32768) then ' Emergency Mode' else 'OK' end as status
FROM master.dbo.sysdatabases
WHERE [name] NOT IN ('distribution', 'tempdb', 'model','Pubs','Northwind')

also i run this

select * from sysdatabases where databaseproperty(name,N'IsSuspect') <> 1

and here also i get all the database including "XYZ"...i guess if "XYZ" is suspect the resultset should not be including "XYZ"

Why if the EM shows suspect status FOR "XYZ" DATABASE it should come up when i check status column in sysdatabases table?

View Replies !

Database Show (Suspect)
One day I openend the enterprise manager and found that all user defined database have (Suspect) infront of the database name.

What does that means?

By the way, I could not open any user database

View Replies !

Serious Perfomance Problem Using UDFs As Function Arguments. (I Suspect A Bug, Show Me I'm Wrong!)

(From an exchange originally posted on SQLServer.com, which wasn't resolved...)

To return views tailored to the user, I have a simple users table that holds user IDs, view names, parameter names, and parameter values that are fetched based on SUSER_SNAME(). The UDF is called MyParam, and takes as string arguments, the name of the view in use, and a parameter name. (The view the user sees is really a call to a corresponding table returning UDF, which accepts some parameters corresponding to the user.)

But the performance is very dependent on the nature of the function call. Here are two samples and the numbers reported by (my first use of) the performance monitor:
Call to table returning UDF, using local variables:

declare @orgauth varchar(50)
set @orgauth = dbo.MyParam('DeptAwards', 'OrgAuth')
declare @since datetime
set @since = DATEADD(DAY,-1 * dbo.MyParam('DeptAwards', 'DaysAgo'),CURRENT_TIMESTAMP)
select * from deptAwardsfn(@orgauth,@since)

[187 CPU, 16103 Reads, 187 Duration]

Call to same table returning UDF, using scalar UDFs in parameters:

SELECT *
from deptAwardsFn (
dbo.MyParam('DeptAwards', 'OrgAuth')
,DATEADD(DAY,-1 * dbo.MyParam('DeptAwards', 'DaysAgo'),CURRENT_TIMESTAMP)
)
[20625 CPU, 1709010 Reads, 20632 Duration]
(My BOL documentation claims the CPU is in milliseconds and the Duration is in microseconds -- which I question.) Regardless of the unit of measure, it takes a whole bunch longer in the second case.

My only guess is that T-SQL is deciding that the parameter values (returned by dbo.MyParam) are nondeterministic, and continually reevaluates them somehow or other. (What ever happened to call by value?)

Can anyone shed some light on this strange (to me) behavior?

----- (and later, from me)---
(I have since discovered that the reference to CURRENT_TIMESTAMP in the function argument is the cause, but I suspect that is an error -- it should only capture the value of CURRENT_TIMESTAMP once, when making the function call IMHO.)

View Replies !

How To Set Database Status To Suspect.don't Resolve The Suspect Problem,I Want To Suspect Database

Hi
I want to suspect database
stop server first
I try to rename C:Program Files (x86)Microsoft SQL ServerMSSQL.1MSSQLDatamsdbdata.mdf to msdbdata.sav
and then start the server
use command to check:
SELECT status & 256 FROM master.dbo.sysdatabases WHERE name = database_name
if the result is 256,it means the msdb is suspect,but the result is 0,it same as the normal status
do you know how to set database suspect with this way, or do you know other way to suspect databse.
absolutely,I could re-back my server noraml with your way
Thanks

View Replies !

Sp_help
We use sql server 6.5. When I do an sp_help <table_name>,
there is a
last column called "FixedLenNullInSource". What is the
purpose of the
column? How does it get set to "Yes" or "No"?

I am doing a select * into <new_table> from <old_table> in my code. Then I do a insert into that table. It works fine most of the time. When it works fine and I do a sp_help on the <new_table> and all columns have either "FixedLenNullinSource" as n/a or No. Suddenly when it starts working improperly (it pads the varbinary column with zeroes)I checked the table with the sp_help <New_table> command it shows the varbinary column with "FixedLenNullinSource" as Yes. Is there a way to manually make it 'No'?

Any help will be appreciated

View Replies !

SP_Help
I need to write dynamic SQL statment that will delete a code from a table but before you can delete that code...I need to find all the foreign key constraints (all the tables that references this table to either update or delete from them and then delete from this table last) I know how to get this information from SP_Help but i dont know how I can do this dynamically. Please help. Emadkb

View Replies !

Sp_help Can't See My Tables
I'm trying to use sp_help to get information on my tables. I can usesp_help alone to get a list of objects (including user tables), butwhen I pass a table name as an argument I get the following errormessage:exec sp_helpexec sp_help parcelServer: Msg 15009, Level 16, State 1, Procedure sp_help, Line 71The object 'DGM_HILLSHADE2' does not exist in database 'raster'.The table clearly exists, but sp_help fails to find it and returninfo. This is the case in a couple of my databases. I'm connected as'sa' so it seems to me it shouldn't be a permissions problem, right?D Bull

View Replies !

Problem With Sp_Help Proc
Hi All,

I am using Sp_Help <TableName> command to get details of table.
I found out one strange this, can anybody tell me is this problem with sp_Help store Proc.

I have created table AsseType
With AssetID DataType: Int
AssetDesc DataType: nvarchar(30)

If I go to Enterprise Manager right click on it table and Click on Design, I can see size is 30.

But if I go to Query Analyzer and type Sp_Help AssetType
Then I get length as 60.

One thing which I notice is apart from nvarchar datatype for all other datatypes, it returns same field length as seen in Design mode.

I found out this on SQL7 with SP3 and SQL2K with SP1.

Any help.........

Many thanks in Advance.

Regards,
Santosh

View Replies !

HELP: Sp_help And Object Browser Report View Column Sizes Differently
Hi,I've run into a curious problem with MS SQL Server 8.0. Using sp_help andSQL Query Analyzer's object browser to view the columns returned by a view,I find that sp_help is reporting stale information.In a recent schema change, for example, someone lengthened a varchar columnfrom 15 to 50 characters. If we use sp_help to find out about a view thatdepends upon this column, it still shows up as VARCHAR(15), whereas theobject browser correctly reports it as VARCHAR(50).Dropping and recreating the view fixes the problem, but we have quite a fewviews, and dropping and re-creating all of them any time a schema change ismade is something we want to avoid. I tried using DBCC CHECKDB in hopes thatit would 'refresh' SQL Server's information, but no luck.(if you're curious as to why I don't just use the object browser instead,read boring technical details below)Has anyone seen this before? Is there some other way (other thanre-creating every view) to tell SQL Server to "refresh" it's information?Thanks!-Scott----------------------Boring Technical Information:The reason this is an issue for us (i.e., I can't just use the objectbrowser instead) is that our object model classes are built using standardmetadata query methods in Java that seem to be returning the same staleinformation that sp_help is returning. These methods are a part of thestandard JDK, so we can't easily fiddle with them. Anyway, as a result, ourobject model (at least with respect to views) may not match our currentschema!

View Replies !

How To Show ChartFX Reports In ReportServer And How To Show Tooltips For Reports Using Chart Properties

Hi all,

I have two problems.

1. I downloaded ChartFXRSTrial and created one chart, and able to deploy it in ReportServer, but the problem is the reports are not showing there, i checked the configuration of .dll files in the help provided by chartFX, but couldn't get anything, so could help me on this.

2. How to give Tooltip for the X- axis or Y- axis values in the ReportServer , i tried using chartproperties of .rdl file, but didnt understand it. can help me on this, and one more i tried with Dundas too, If im giving tooltip as #valy then, it is showing samething in reportserver instead the values of 'Y-axis'.

Thanks,
Mahesh Manthena

View Replies !

Determining What Are &"system&" Objects In Sp_help Or System Tables
Hi,I have a few things on my databases which seem to be neither true systemobjects or user objects - notably a table called 'dtproperties' (createdby Enterprise manager as I understand, relating to relationship graphingor something) and some stored procs begining with "dt_" (some kind ofsource control stuff, possible visual studio related). These show up whenI use"exec sp_help 'databaseName'"but not in Ent. Mgr. or in Query Analyzer's object browser, and also notin a third party tool I use called AdeptSQL. I am wondering how thosetools know to differentiate between these types of quasi-system objects,and my real user data. (This is for the purpose of a customized schemagenerator I am writing). I'd prefer to determine this info with systemstored procs (ie sp_help, sp_helptex, sp_...etc) but will dip into thesystem tables if needed.Thanks,Dave

View Replies !

DB Suspect
HI everybody:

Today(18nov98) we experimented a problem with a DB. In the Production environment the
log segment get full and our application got down, when we get into SQLServer we noted that
the main db had the "suspected" flag on. A lot of people move to see what we can do for resolve
the problem and the solutions that we found are these:
1) Run the sp_resetstatus (SQLBooks Online)
2) DBCC DBrepair DB, dropdev

After a hard work we finally changed the DB status, but when all the guys joined to see how the
problem was resolve everybody said a little solution but we didnot reach a final and integral
solution.

Ah, I'm tired!!

How must we resolve a problem of these characteris in the future?

View Replies !

Now In Suspect
Hi all,
I have had problems lately with my standby server,when i am trying to do a load from my production it goes into suspect mode
.the load is just fine as per my error log after
5/10 minutes it goes into suspect mode the error is
"Error 3305,Severity 21,State 1"
"Page 559396 in databse "xyz' read in during runtime or load xact was uninitilised"
"Idxact:Dbid:6 is in IN_LOAD state with the following exception raised:major 43,minor 3,pstat:0X400"

Now i have checkd error 3305 everywhere but no answers..please help

Regards

View Replies !

Db Suspect
I have a db in suspect. I want to try to run sp_reset_status and reset the status bit. I believe there is a script that I can run to create sp_reset_status. Where can I find that?

Thanks

Betty Lee

View Replies !

DB Suspect
Every once in a while one the DB on SQL Server 2000 goes suspect. I was thinking it was because there was no back up plan. The problem is usually resolved after a simple start and stop of the SQL Server Agents. Anyone have similar situations that could shed some light?

Thanks
Matt

View Replies !

Suspect DB
I had a database (give it a name A) that was marked suspect. I ran the following query

use master
go
sp_resetstatus <db_name>

I then stopped and restarted SQL Server. This fixed the problem for database A but I got two more that were suspect. After running the same query for both B & C, C got fixed but I still cannot fix B. My question is why did fixing problem A cause a problem for DB B & C?

I tried running the following query on B after the first one failed.

Update sysdatabases set status = -32768 where name='B'

This gave me the following error: Ad hoc updates to system catalogs are not enabled. The system administrator must reconfigure SQL Server to allow this.

Could somebody please help me solve this problem?

View Replies !

Suspect Db
One of my database mark as suspect and resetstaus did not work. From the SQL server error log i find following message. Any suggestion?

source:kernel
SQL Server Assertion: File: <recovery.c>, line=2687
Failed Assertion = 'seenCkptEnd'.
...
source:spid7
Error: 0, Severity: 19, State: 0
...
source:spid7
Location: recovery.c:2687
Expression: seenCkptEnd
SPID: 7
Process ID: 162
...
source:spid7
SqlDumpExceptionHandler: Process 7 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
....
source:spid7
Error: 3414, Severity: 21, State: 1

View Replies !

SUSPECT...
Hi all,
What does this mean? SUSPECT, in SQL server 7? I dont remember what caused one of my database to be SUSPECTed. Can someone let me informed what causes a database to be SUSPECT and what are its implications and how to make the SUSPECTed database work

Thanx in advance
ozone

View Replies !

Suspect DB
One of my databses is saying suspect beside it can this be fixed

View Replies !

Suspect Database
My database is marked as suspectI am using SQL Server 2000,I ran the command sp_resetstatus it executes succesfully. but still the database is in suspect state.can any one tell me how i recover my data.thanks in advance

View Replies !

Database Suspect
I have two questions:(1) How can we diagnose the reason of database suspect? The error logdoesn't tell me much.(2) After restart the server, the suspect is gone, but how can Iensure everthing is fine? DBCC check?Thanks!Saiyou

View Replies !

My Database In Suspect
my database is in suspect,how to correct it?
thx in adance..

View Replies !

Suspect Database
Hi all,

We recently had some kind of error on one of the server's hard drives. The network guys, reinintialized (or something) and were able to bring everything back. However, two of my databases now is "Suspect" and can't be used. Both the MDF & LDF exist, and there are no indications of actual data loss. What can I do with a "suspect" database ? SQL 2K

What should I do to recover these two databases?
Thank you for all your suggestions.

View Replies !

Suspect Database
I could not open my database.It says its Suspect and could not open and not displaying any of the objects
What should be the reason and what is steps i can do make it up and running.

Thanks

View Replies !

Suspect Database.....
:mad:

One of my prodn databases went into suspect mode today..
I was able to recover it.
The tech support guyz had rebooted the server couple of times
(out of ignorance) cos they thought if wud fix it.
I lost the sql errpor log file which had the error details as to why db when into suspect....so my questions are..

1. Probable reasons why db when into suspect mode.
2. Any other way to find out about the error details.
3. When I ran dbcc checkdb with repair_rebuild option
for some tables it gave error

"Parent node for page (1:13075) was not encountered"

How can i resolve the consistency errors.
Is DBCC CHECKTABLE sufficient.???

View Replies !

Database Is Suspect
We have an SQL Server 2000 DB server with several databases on it. Frequently, one of the DBs will have a state of "Suspect." This appears to occur after our 3rd party backup software runs a full backup on the weekends.

How can I begin to troubleshoot the cause of this issue? Has anyone seen anything like this?

thanks,

Jeff

View Replies !

Database Suspect
Hello all:
Today I find my database HQ was suspect, and I can not do anything
about it! What can I do to ?

Thank's
From Daniel

View Replies !

Best Way To Recovery Suspect Db?
steps to recovery suspect database
Log showed a 614 error and probably is a result of a hardware 0/s problem or ?. The database was not
reloaded before the error.
I was recently was called in to help some people who had a SQL Server database marked as suspect.
I have never had to deal with this situation before. I got the database operational by doing the
following steps. Was there an easier or better way?

Executed statement per BOL procedure to allow updates to system tables.

Removed suspect flag per BOL (BOL says to use sp_resetstatus which I did not find in master or msdb,
however the BOL had the code listed so I typed in the pertinent statement). I do not know what the '^ 256
meant in BOL, I used the status code that the nonsuspect databases had '16400'.

SQL Server would not let me restore into a suspect database so I reset the suspect flag. Could have dropped
the database, however I did not have the information to recreate the database so the restore function would
work.

Put database in single user mode.

restored database.

Removed the ability to update system tables per BOL

Set the database back to multi user mode.

View Replies !

<Database> (suspect)
Hi... I have this problem with my database (dunno how this thing happen). Today, 2 of my databases have been marked as 'suspect' (grey color in SQL Enterprise Manager). In ISQL, when I try 2 connect 2 the database (use), the message '
Msg 926, Level 14, State 1
Database 'MYUAT' cannot be opened - it has been marked SUSPECT by recovery. The SA can drop the database with DBCC.'
appeared.

Don't understand Y this occurred...

Thanks in advance for any help...

~Cheers~

View Replies !

SQL "Suspect" Database .... Help!
I am using SQL server 6.5 sp3 and NT 4.0 sp4.
My SMS database has been marked suspect.
I do not have a backup.
I have read several articles about trying to us sp_resetstatus.
I can not find this sp on my server.
When I try the following:
UPDATE master..sysdatabases status=256 WHERE name = ('sms')

I get the following back:
Ad-hoc updates to system catalog not enabled. System Adminstrator must recongifure system to allow this.

I have searched Microsoft KB and everywhere I can think of. If anyone can help I would really appreciate it.
I even tried reapplying sp3 and rebooting...this did not help either.
Can someone please tell me how to change the status back to normal.....I think this is a it will take..

thanks in advance,
nathan

View Replies !

Suspect Databases
Hello,

Today we found a suspect database and after consulting this website went and ran sp_resetstatus on one database with success. After which we stopped and started the server and ran dbcc newalloc, dbcc textall, dbcc checkdb on that database. It successfully changed from its suspect status and random queries showed that the data was still intact.

Exactly the same process was run on another database and it failed to move from the suspect status after restarting the server. We then went through books online, which advised to update sysdatabases setting the database's status to 0. This also failed.

HELP PLEASE.

Does anyone know what else to try? This was a development database with no backups. This would save a weeks work. Thanks for you time.

Cheers
Damian

View Replies !

Suspect Database
I have the original dat files ( 2 seperate log / data) of a database. I have created new devices (same size as originals) and a new database. I replace the new dat files with the originals and the database always comes up as a suspect. I have done this with the other 7 databases on my server and none have similar problems. This database was created different then others using new database and new devices routine rather than creating the devices first. Any Ideas?

Thanks in Advance.

View Replies !

MSDB Suspect
I'm running Win2000/SQL2000 on a Compaq CL380 Cluster Server. After a powerdown to do a physical move, the MSDB is now marked SUSPECT. I have tried the stored procedure SP_RESETSTATUS, a DBCC consistency check, and also have restored the database from backup. The database still shows MSDB is suspect. What can I do? We can't get a good backup as long as it is still this way as it depends on the SQL Agent.

View Replies !

SUSPECT Database
Im running SQL 7.0 with a large heavily used 4Gb database. After a while the database is marked suspect. What can be the cause to this ? Please email me and I can send you additional information about hardware and the system.

View Replies !

Suspect Database
Hi everyone,

I really need help on this, one of my databases is marked suspect. I did tried to execute this command below (scripts):

use master
go
sp_configure 'allow updates',1
go
reconfigure with override
go
update sysdatabases set status=4 where name='security'
go
sp_configure 'allow updates',0
go
reconfigure with override
go

and it release the suspect from the 'Security' database, but it Won't let me access the table,data or nothing. The worse thing is when I stop & start the server again, the database marked suspect again.

Could anybody out the help me on this. Thank in advance, Vu

View Replies !

Removing DB Suspect
I wonder if one can give a hint on remove a DB suspect,
Mind you I have used SP_dbremove still did not remove the DB
This is on SQL 7.0 box

Any idea welcomed

Saad

View Replies !

Suspect DB - Urgent
Hi,

One of my DB got into SUSPECT mode.

I tried "sp_resetstatus" procedure. But it says, the following mesg,
"
Prior to updating sysdatabases entry for database 'DELPHI3', mode = 0 and status = 1077936141 (status suspect_bit = 0).
No row in sysdatabases was updated because mode and status are already correctly reset. No error and no changes made.
".

Can anybody please help me how to make this into normal status.

tks in advance,
vasu

View Replies !

Log Reader Is Suspect
We have continuous replication from a 6.5 server to a 7.0 server and the Log Reader agent falls over periodically with the message:

"The agent is suspect. No response within last 10 minutes"

This happened 1 month ago & I reapplied the replication to sort the problem out. It's started happening again (4 times in the past 24 hours), but when I restart the agent it runs for a few minutes and then fails agan.

Has anyone had a similar problem?

Do you know of a way to fix the agent without resetting all replication?

Have you any suggestions to how we can stop this failing again?

Thanks in advance for replies!

Lesley

View Replies !

Suspect :urgent
Hello guys,
the distribution database on one of the publishers is marked as suspect for me.
when i saw in sql server error log it showed me an error saying log file is full and specifies and operating system error 1502.
the log file is about 85 MB and the data file is about the same.
i saw the disk space that is free it is about(20GB) i don't understand why it went to suspect mode,any way i tried
executing sp_resetstatus <DBname> it seems it didn't work can any one help me in this matter,if possible please give me the steps what i need to do
when i execute sp_resetstatus this is what i get

"Prior to updating sysdatabases entry for database 'distribution', mode = 0 and status = 264 (status suspect_bit = 256).
For row in sysdatabases for database 'distribution', the status bit 256 was forced off and mode was forced to 0.
Warning: You must recover this database prior to access.
"

thanks for any help

View Replies !

Distribution (Suspect)
I've got a distribution database that is marked as "Suspect". I've been trying to drop the database, I don't care about loosing the data, but when I try and drop the database I get an error saying that the "Distribution could not be opened because some of the files could not be activated." I've tried using the dbcc dbrepair(distribution, dropdb) command, but when I run that I get an error message saying that the database is not in suspect mode, although it shows it in Enterprise Manager. Can someone PLEASE help me resolve this issue?

View Replies !

Database Suspect
Hi!

I am using SQL Server 7.0 and i have found that one of our user database was not accessible. I did mark the database status as 'Suspect'. I suppose to reset the status of the database but what i did , i have restarted the SQL Server. It seems like database services are running but i am not able to access the database through Enterprise manager and ISQL utility. If anyone could help me out to resolve this problem, appreciated.

Thanks!

View Replies !

MS SQL In SUSPECT State
Hi, we have a database master not aligned with databases, due to wrong backup procedure. Currently, our database is in suspect state and we are not able to access again to the DB. We are not expert in BD, so we are looking for someone or a company that can restore the database for us.
If you can or you know someone that can do, please, tell us.

tnx in advance
Gianfranco

View Replies !

Suspect Database
I had a "suspect" database. I detached successfully and now I'm trying to attach it. For some reason the LDF file is missing. The "detach" was successfull but the "attach" would not succeed. Whenever I try to attach the database, it would give me an error that says:

"Device Activation Error. The physical filename "xyz...LDF" may be incorrect."

What can I do to save our data from total loss?

Please help

Joel

View Replies !

DB Marked Suspect
I have SQL Express SP1 installed on serveral machines, each has one instance and each instance has more than one database.

Recently, I found out some dbs are marked Suspect. MOM tool reported something like:

The database "your-DB" in the instance "Your-Instance" is in a critical state. The state is: Suspect.

I tried to run "DBCC CHECKDB", but it failed.

Can someone tell me what could cause the problem, and how to fix it?

Thanks,

Peter

View Replies !

Database Suspect
Hi all , i am facing a problem and don't know how to handle the issue. I created a database in sql server 2000 , gave it to a friend who made certain changes to the database and mailed me back.
Now that i try to open the database , in the enterprise manager the icon of the my database is gray with "suspected" written in brackets after the database name. On expandin it , it shows ("No Items"). Kindly help me out guys , i am totally stuck for the moment.
Regards

View Replies !

Suspect Database
Okay, so i have a tabase named "TEST" that i set up, everything in it is for a website i've been designing slowly for the last month, i come in today, and notice the database is marked suspect. look at the log and i see all of this:

Recovery of database 'Test' (7) is 20% complete (approximately 305 more seconds) (Phase 2 of 3).

ForwardLogBlockReadAheadAsync: Operating system error 23(Data error (cyclic redundancy check).) encountered.

Operating system error 23(Data error (cyclic redundancy check).) on device 'C:Program FilesMicrosoft SQL ServerMSSQLdataTest_Log.LDF' during ForwardLogBlockReadAheadAsync.

Error: 3313, Severity: 21, State: 2

Error while redoing logged operation in database 'Test'. Error at log record ID (8440:42526:1)..

Error: 3414, Severity: 21, State: 1

Database 'Test' (database ID 7) could not recover. Contact Technical Support..

Now, honestly, i could care less about the data, the thing the matters most to me, is the couple of stored procedures i've developed.

what can i do?

View Replies !

Suspect Database
Hi everyone,
I hope you could help me.
I have a database that was marked as suspect, i change is state but now i want to extract the information of the database and a couldn't because de database have several erros include 2 allocation erros.
How could i solve this problem? I don't have a recent database backup.
thanks to everyone.

Pedro Silva

View Replies !

Database Is Suspect
Why do i keep getting this error ?

Mary Mary

Yes O !

View Replies !

Suspect Database, Need Help Pls.
Hi all,
I have a suspect database caused by a disk error on a Raid5 disk. I'm a bit of a novice on SQL and am using SQL 2005. I have tried the following and can't get the database status to reset which means the DBCC checkdb command does not run. The client I am fixing this for has no backup of the data at all.

USE master
GO
sp_configure 'allow updates', 1
GO
RECONFIGURE WITH OVERRIDE
GO

EXEC sp_resetstatus 'nhd2007';
GO

sp_configure 'allow updates', 0
GO
RECONFIGURE WITH OVERRIDE
GO

DBCC checkdb ('nhd2007',NOINDEX);
GO

I get the following error back:-
Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
The suspect flag on the database "nhd2007" is already reset.
Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
Msg 926, Level 14, State 1, Line 3
Database 'nhd2007' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.

The error in the SQL Log which is causing all the problems is:-
Message
SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:3425329; actual 25600:1744858624). It occurred during a read of page (1:3425329) in database ID 24 at offset 0x00000688862000 in file 'E:hd2007hd2007.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

Any advice on what I can do to get some access to the data would be great.

Thanks

View Replies !

DB Suspect Not Show In Sp_help