July 28, 2009 at 3:08 am
Chirag (7/28/2009)
VishalFirst thing - Do you have proper backups?
check this article http://www.sqlservercentral.com/articles/65804/
Hi Chirag, Thanx Mann I have been to this article and I found its very decent and nice.
July 28, 2009 at 3:12 am
Vishal Singh (7/28/2009)
For restoring from backups I had to go 15 days back because I have a full backup running everyday (WITN INIT) and the conistency error I found was started 10-14 days back.pretty much through...isn't?
restoring may caused loosing others data (pertty much more than what I lost while repairing with data_loss).
Then you need to seriously sit down and review both your backup strategy (because it failed you here) and the frequency that you run consistency checks.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 28, 2009 at 3:14 am
Vishal Singh (7/28/2009)
Additionally, Look on to the error message Its Error 8964:
Yup, I saw. What of it? It's a fairly standard corruption message saying that there's damage to the blob pages
Was there any other alternative in my situation?
as there any other alternative in my situation.?
Since the minimum level to repair was specified as repair_allow_data_loss, your options are limited to repair with data loss or restore from backup.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 28, 2009 at 3:20 am
manoj2001 (7/28/2009)
So please check in your procedure wherver you are importing data into database.
It's not possible to insert out-of-range values via stored procedures. The SQL query processor will catch that. Data purity errors (which, by the way, these are not) are generally the result of IO corruption or buggy ODBC/OLEDB drivers that do bulk data loads
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 28, 2009 at 3:23 am
Vishal Singh (7/28/2009)
My databases are on 2000 only where I believe there is no DATA_PURITY option available?
Please post SQL 2000-related questions in the SQL 2000 forums in the future. If you post in the 2005 forums, you're very likely to get 2005-specific solutions.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 28, 2009 at 4:10 am
I have consistency check running every week. The only thing, which makes it failed here, is that the consistency checker has been ignored last week due to server maintenance and reboot.
and then after (when the server is up it was Monday morning) it never been executed for that week.
(Tightened hands cannot help)
Now when it failed this week I came to know about these errors.
July 28, 2009 at 4:13 am
Yup, I saw. What of it? It's a fairly standard corruption message saying that there's damage to the blob pages
I mean here is that error 8964 doesn't left any other repair options rather data_loss incase you can't go for a backup.
July 28, 2009 at 4:17 am
Please post SQL 2000-related questions in the SQL 2000 forums in the future. If you post in the 2005 forums, you're very likely to get 2005-specific solutions.
I see..I posted it in rush... so went in 2005 group. thanx for bringing it to my notice.
July 28, 2009 at 8:28 am
Vishal Singh (7/28/2009)
Yup, I saw. What of it? It's a fairly standard corruption message saying that there's damage to the blob pages
I mean here is that error 8964 doesn't left any other repair options rather data_loss incase you can't go for a backup.
There's a lot of CheckDB errors that don't leave any option other than repair or restore. All the ones that refer to the heap or the clustered index pages. There are also a lot of checkDB errors that the only option is restore, they can't be repaired.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 1, 2009 at 2:21 am
Hi VS,
Based on error mentioned by you:
"the Smaple errors were like this:
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 206623779. The text, ntext, or image node at page (1:4846), slot 7, text ID 18859360256 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 206623779. The text, ntext, or image node at page (1:4846), slot 9, text ID 18859425792 is not referenced."
Microsoft had already confirmed that this was a problem in SQL server 2000 product and resolved in Service Pack 1.
Can you please check Service pack is installed in your server, i mean your servers are upgraded by latest SPs.
Manoj
August 2, 2009 at 10:04 pm
manoj2001 (8/1/2009)
Hi VS,Based on error mentioned by you:
"the Smaple errors were like this:
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 206623779. The text, ntext, or image node at page (1:4846), slot 7, text ID 18859360256 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 206623779. The text, ntext, or image node at page (1:4846), slot 9, text ID 18859425792 is not referenced."
Microsoft had already confirmed that this was a problem in SQL server 2000 product and resolved in Service Pack 1.
Can you please check Service pack is installed in your server, i mean your servers are upgraded by latest SPs.
Manoj
Well Microsoft has accepted many errors as a bug which actually not a bug but sometimes they are raised because of a bug.
This error in particular was not caused by any bug but it was caused my I/O subsystem.
My SQL Servers are running with SP4 (Enterprise Edition)
Viewing 11 posts - 16 through 25 (of 25 total)
You must be logged in to reply to this topic. Login to reply