Even though I have installed the latest sql server service pack (4). When I
run the dbcc checkdb statement with the arithabort set to on for one of my
production databases, I still get a few line with the error:
Server: Msg 8964, Level 16, State 1, Line 4
Table error: Object ID 2. The text, ntext, or image node at page (1:380425),
slot 2, text ID 2789285298176 is not referenced.
Even when I run: SELECT @.@.VERSION system stored procedure it returns
Microsoft SQL Server 2000 -8.00.2039(Intel x86)
As the version that I am using. I have also just today re-applied the
service pack following step by step the instruction in the sqlreadme for
service pack 4. I have read a solution that suggested re-installing sql
server but that is just not an option right now, because of the fact that it
is a production database that is in constant use. I'm also starting to think
that these arent necessarily errors that are critical. Could someone
help\advise?
Many thanksHi
There is nothing wrong with your SP level, but you have corruption in your
DB that applying a SP can not help to fix. SP's do not affect user DB's,
only system DB's.
run DBCC with the REPAIR_ALLOW_DATA_LOSS option. For more information on
the command, look in Books Online.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Fazz" <farayi@.lovetm.co.uk> wrote in message
news:u%23QrmC9$FHA.2320@.TK2MSFTNGP11.phx.gbl...
> Even though I have installed the latest sql server service pack (4). When
> I run the dbcc checkdb statement with the arithabort set to on for one of
> my production databases, I still get a few line with the error:
> Server: Msg 8964, Level 16, State 1, Line 4
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:380425), slot 2, text ID 2789285298176 is not referenced.
> Even when I run: SELECT @.@.VERSION system stored procedure it returns
> Microsoft SQL Server 2000 -8.00.2039(Intel x86)
> As the version that I am using. I have also just today re-applied the
> service pack following step by step the instruction in the sqlreadme for
> service pack 4. I have read a solution that suggested re-installing sql
> server but that is just not an option right now, because of the fact that
> it is a production database that is in constant use. I'm also starting to
> think that these arent necessarily errors that are critical. Could someone
> help\advise?
> Many thanks
>
Monday, March 19, 2012
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment