Prev: Windows Delayed write error when backing up to network share
Next: ldf file missing...
From: Julie on 11 Feb 2005 04:08
Dear All,
Our database was maked as suspect today, I ran the store
procedure exec sp_resetstatus 'DBNAME' but got the
message 'Prior to updating sysdatabases entry for
database 'ParisProduction', mode = 0 and status = 16
(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 anyone tell me what to do ?

J
From: Tibor Karaszi on 11 Feb 2005 04:34
Recommended actions for corrupt or suspect databases :

http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/


"Julie" <anonymous(a)discussions.microsoft.com> wrote in message
news:045201c51019$4b678730$a501280a(a)phx.gbl...
> Dear All,
> Our database was maked as suspect today, I ran the store
> procedure exec sp_resetstatus 'DBNAME' but got the
> message 'Prior to updating sysdatabases entry for
> database 'ParisProduction', mode = 0 and status = 16
> (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 anyone tell me what to do ?
>
> J


From: Julie on 11 Feb 2005 06:47
Thanks Tibor


>-----Original Message-----
>Recommended actions for corrupt or suspect databases :
>
>http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.a
sp
>
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>http://www.sqlug.se/
>
>
>"Julie" <anonymous(a)discussions.microsoft.com> wrote in
message
>news:045201c51019$4b678730$a501280a(a)phx.gbl...
>> Dear All,
>> Our database was maked as suspect today, I ran the store
>> procedure exec sp_resetstatus 'DBNAME' but got the
>> message 'Prior to updating sysdatabases entry for
>> database 'ParisProduction', mode = 0 and status = 16
>> (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 anyone tell me what to do ?
>>
>> J
>
>
>.
>
 | 
Pages: 1
Prev: Windows Delayed write error when backing up to network share
Next: ldf file missing...