Re Recorcer suspect database

Hi
One of my client give me a suspect database, but he doesn't have any backup
of this base.
When i try to recorver the data with the command : DBCC CHECKDB with
REPAIR_REBUILD (or REPAIR_ALLOW_DATA_LOSS)
(http://65.214.43.26/articles/18/view.asp?id=7381), i got an error :
Serveur : Msg 8946, Niveau 16, tat 12, Ligne 2
Erreur de table : La page d'allocation (1:1) a des valeurs d'en-tte de page
PFS_PAGE incorrecte. Le type est 0. Contrlez le type, et les ID d'objet et
de page pour cette page.
What can i do?
The Microsoft support is too expensive, and i want to find an other solution
for the futur, to recorver my data.
When i try MSSQLRecorvery, i recorver all data, and it seems to be the best
solution. What do you think about this software?
Best regards
Herv RESCOURIO
"Hari Prasad" <hari_prasad_k@.hotmail.com> a crit dans le message de news:
eulsf9bNFHA.1948@.TK2MSFTNGP14.phx.gbl...
> Hi,
> First identify the cause for the Suspect. If it is due to some file access
> issues you do not want to use any tools instead use the SQL Server
> commands
> to recover the database.
> Various Reasons for database going to suspect Status.
> 1. The MDF or LDF file for the database is not available during startup
> 2. LDF file missing or Corrupted
> 3. MDF file page allocation problems.
>
> 1. The first one can be resolved by executing "sp_resetstatus" stored
> procedure and restart SQL server services
> 2. Start the database in Emergency mode , Update the Status column in
> master..sysdatabases table for that database to 32768.
> After this database will be usable with out transaction log. AFter this
> create a new database and use DTS to transfer objects and data.
> 3. Third one is critical , try executing DBCC CHECKDB with REPAIR_REBUILD
> option. If the problem is not rectified
> wither restore from Backup or contact Microsoft support.
>
> How to set to Emergency Mode
> --X-
> Use emergency mode (also called bypass mode) to recover data when SQL
> Server marks a database suspect and the automatic recovery will fail.
> Setting the database status to emergency mode tells SQL Server to skip
> automatic recovery and lets you access the data. To get your data, use
> this script:
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
>
> Thanks
> Hari
> SQL Server MVP
>
> "Herv RESCOURIO" <hr@.segilog.com> wrote in message
> news:ufots5bNFHA.3296@.TK2MSFTNGP15.phx.gbl...
>
> One of my client give me a suspect database, but he doesn't have any
backup
> of this base.

> The Microsoft support is too expensive, and i want to find an other
solution
> for the futur, to recorver my data.
> When i try MSSQLRecorvery, i recorver all data, and it seems to be the
best
> solution. What do you think about this software?
Just do the backups.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com

Re Recorcer suspect database

Hi
One of my client give me a suspect database, but he doesn't have any backup
of this base.
When i try to recorver the data with the command : DBCC CHECKDB with
REPAIR_REBUILD (or REPAIR_ALLOW_DATA_LOSS)
(http://65.214.43.26/articles/18/view.asp?id=7381), i got an error :
Serveur : Msg 8946, Niveau 16, tat 12, Ligne 2
Erreur de table : La page d'allocation (1:1) a des valeurs d'en-tte de page
PFS_PAGE incorrecte. Le type est 0. Contrlez le type, et les ID d'objet et
de page pour cette page.
What can i do?
The Microsoft support is too expensive, and i want to find an other solution
for the futur, to recorver my data.
When i try MSSQLRecorvery, i recorver all data, and it seems to be the best
solution. What do you think about this software?
Best regards
Herv RESCOURIO
"Hari Prasad" <hari_prasad_k@.hotmail.com> a crit dans le message de news:
eulsf9bNFHA.1948@.TK2MSFTNGP14.phx.gbl...
> Hi,
> First identify the cause for the Suspect. If it is due to some file access
> issues you do not want to use any tools instead use the SQL Server
> commands
> to recover the database.
> Various Reasons for database going to suspect Status.
> 1. The MDF or LDF file for the database is not available during startup
> 2. LDF file missing or Corrupted
> 3. MDF file page allocation problems.
>
> 1. The first one can be resolved by executing "sp_resetstatus" stored
> procedure and restart SQL server services
> 2. Start the database in Emergency mode , Update the Status column in
> master..sysdatabases table for that database to 32768.
> After this database will be usable with out transaction log. AFter this
> create a new database and use DTS to transfer objects and data.
> 3. Third one is critical , try executing DBCC CHECKDB with REPAIR_REBUILD
> option. If the problem is not rectified
> wither restore from Backup or contact Microsoft support.
>
> How to set to Emergency Mode
> --_-
> Use emergency mode (also called bypass mode) to recover data when SQL
> Server marks a database suspect and the automatic recovery will fail.
> Setting the database status to emergency mode tells SQL Server to skip
> automatic recovery and lets you access the data. To get your data, use
> this script:
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
>
> Thanks
> Hari
> SQL Server MVP
>
> "Herv RESCOURIO" <hr@.segilog.com> wrote in message
> news:ufots5bNFHA.3296@.TK2MSFTNGP15.phx.gbl...
>> One of my client give me a suspect database, but he doesn't have any
backup
> of this base.

> The Microsoft support is too expensive, and i want to find an other
solution
> for the futur, to recorver my data.
> When i try MSSQLRecorvery, i recorver all data, and it seems to be the
best
> solution. What do you think about this software?
Just do the backups.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com