hi!!!
i have this error 823, when i choise tables in a database, the description is input output error bad page id was detected during ...
if you have any sugections to recovery database, i'm great for them
thanks
manuel ralha
http://www.karaszi.com/sqlserver/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:66C39796-BD18-4E6C-AED0-DB07AF001973@.microsoft.com...
> hi!!!
> i have this error 823, when i choise tables in a database, the description is input output error bad page id
was detected during ...
> if you have any sugections to recovery database, i'm great for them
> thanks
> manuel ralha
|||hi, thanks
thats a good idea, but when i execute de dbcc checkdb , the error ocurs again
thanks
manuel ralha
|||You didn't say which advice you followed.
Are you saying that you restore the latest clean db backup and all subsequent log backups and one of the log
backups re-introduced the corruption?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:371F4671-4653-4A3A-923C-22790C47AD7E@.microsoft.com...
> hi, thanks
> thats a good idea, but when i execute de dbcc checkdb , the error ocurs again
> thanks
> manuel ralha
|||hi:
the error is this in query analiser or in osql:
I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in file 'D:\cedile\cedile_data.mdf'
manuel ralha
|||What I'm trying to communicate is (as is the article on the web site I suggested) that your best option is
probably to use your backups to restore a clean database, If you feel uncertain about the actions to take, I
suggest you let MS Support help you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:8A7D909A-E787-419A-B926-CA0323CF1600@.microsoft.com...
> hi:
> the error is this in query analiser or in osql:
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in file 'D:\cedile\cedile_data.mdf'
> manuel ralha
>
|||hi
thanks for your help, i'm read your web page, and, i follow all steps. but unhappyly, thoesn't work in this database, i have the same errors.
thanks for your collaboration and help.
manuel ralha
Showing posts with label choise. Show all posts
Showing posts with label choise. Show all posts
Monday, March 26, 2012
error 823
hi!!
i have this error 823, when i choise tables in a database, the description is input output error bad page id was detected during ..
if you have any sugections to recovery database, i'm great for the
thank
manuel ralhahttp://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/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:66C39796-BD18-4E6C-AED0-DB07AF001973@.microsoft.com...
> hi!!!
> i have this error 823, when i choise tables in a database, the description is input output error bad page id
was detected during ...
> if you have any sugections to recovery database, i'm great for them
> thanks
> manuel ralha|||hi, thank
thats a good idea, but when i execute de dbcc checkdb , the error ocurs agai
thank
manuel ralha|||You didn't say which advice you followed.
Are you saying that you restore the latest clean db backup and all subsequent log backups and one of the log
backups re-introduced the corruption?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:371F4671-4653-4A3A-923C-22790C47AD7E@.microsoft.com...
> hi, thanks
> thats a good idea, but when i execute de dbcc checkdb , the error ocurs again
> thanks
> manuel ralha|||What I'm trying to communicate is (as is the article on the web site I suggested) that your best option is
probably to use your backups to restore a clean database, If you feel uncertain about the actions to take, I
suggest you let MS Support help you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:8A7D909A-E787-419A-B926-CA0323CF1600@.microsoft.com...
> hi:
> the error is this in query analiser or in osql:
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in file 'D:\cedile\cedile_data.mdf'
> manuel ralha
>|||hi
thanks for your help, i'm read your web page, and, i follow all steps. but unhappyly, thoesn't work in this database, i have the same errors
thanks for your collaboration and help
manuel ralha
i have this error 823, when i choise tables in a database, the description is input output error bad page id was detected during ..
if you have any sugections to recovery database, i'm great for the
thank
manuel ralhahttp://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/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:66C39796-BD18-4E6C-AED0-DB07AF001973@.microsoft.com...
> hi!!!
> i have this error 823, when i choise tables in a database, the description is input output error bad page id
was detected during ...
> if you have any sugections to recovery database, i'm great for them
> thanks
> manuel ralha|||hi, thank
thats a good idea, but when i execute de dbcc checkdb , the error ocurs agai
thank
manuel ralha|||You didn't say which advice you followed.
Are you saying that you restore the latest clean db backup and all subsequent log backups and one of the log
backups re-introduced the corruption?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:371F4671-4653-4A3A-923C-22790C47AD7E@.microsoft.com...
> hi, thanks
> thats a good idea, but when i execute de dbcc checkdb , the error ocurs again
> thanks
> manuel ralha|||What I'm trying to communicate is (as is the article on the web site I suggested) that your best option is
probably to use your backups to restore a clean database, If you feel uncertain about the actions to take, I
suggest you let MS Support help you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:8A7D909A-E787-419A-B926-CA0323CF1600@.microsoft.com...
> hi:
> the error is this in query analiser or in osql:
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in file 'D:\cedile\cedile_data.mdf'
> manuel ralha
>|||hi
thanks for your help, i'm read your web page, and, i follow all steps. but unhappyly, thoesn't work in this database, i have the same errors
thanks for your collaboration and help
manuel ralha
Subscribe to:
Posts (Atom)