Hello,
I am running some DBCC checks as a routine maintenance task on my sql server 2000 servers. I am running DBCC CHECKDB, DBCC CHECKCONSTRAINTS and DBCC CHECKCATALOG. I have established a set of procedures and tables to capture the output from the error log after running these DBCC commands. After running all three, it appears the same info captured for CHECKDB is not logged for these two: CHECKCONSTRAINTS and CHECKCATALOG. Does anyone know why these are not logged and if it is even necessary for me to run these 2 extra DBCC checks? If not, can anyone recommend what database consistency checks should be executed on a daily basis for a production database server?
DBCC CHECKDB (DBNAME) executed by lshores found 0 errors and repaired 0 errors. Elapsed time: 0 hours 20 minutes 32 seconds.I found help for this question in this article http://www.sql-server-performance.com/ak_inside_sql_server_maintenance_plans.asp
and further info in BOL (sqlmaint Utility.)
Showing posts with label checkconstraints. Show all posts
Showing posts with label checkconstraints. Show all posts
Thursday, March 8, 2012
Tuesday, February 14, 2012
DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS...
Friends,
A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
discovering inconsistencies after a catastrophic power failure. (They
didn't even suspect trouble until weeks later, and at this point all backups
contain the inconsistencies.) The DBCC command now completes without
errors, but we worry that data (actual "row" data, not just index data)
might have been lost. We also worry about resulting integrity problems,
orphaned foreign key references, etc.
It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
be the command we are looking for. If we understand things correctly, it
will report rows that violate some constraint.
Is our thinking correct here? Will system tables and constraints be checked
too? Is there anything else we should be concerned about? (Other than lost
business data, and a UPS for the customer, of course.)
Any words, links, and thoughts of your will be very much appreciated.
Thanks in advance for your time!
James Hunter Ross
Senior Software Developer
O'Neil Software, Inc.Hi
DBCC CHECKCONSTRAINTS will check the integrity of CHECK constraints and FKs
wrt to the data that is present, but it won't tell you if consistencies not
enforced in the database are still correct or if both referenced/referencing
data is missing. If you have copies of historical reports you may want to ru
n
them to compare what they returned previously and now.
John
"James Hunter Ross" wrote:
> Friends,
> A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
> discovering inconsistencies after a catastrophic power failure. (They
> didn't even suspect trouble until weeks later, and at this point all backu
ps
> contain the inconsistencies.) The DBCC command now completes without
> errors, but we worry that data (actual "row" data, not just index data)
> might have been lost. We also worry about resulting integrity problems,
> orphaned foreign key references, etc.
> It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
> be the command we are looking for. If we understand things correctly, it
> will report rows that violate some constraint.
> Is our thinking correct here? Will system tables and constraints be check
ed
> too? Is there anything else we should be concerned about? (Other than lo
st
> business data, and a UPS for the customer, of course.)
> Any words, links, and thoughts of your will be very much appreciated.
> Thanks in advance for your time!
> James Hunter Ross
> Senior Software Developer
> O'Neil Software, Inc.
>
>
A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
discovering inconsistencies after a catastrophic power failure. (They
didn't even suspect trouble until weeks later, and at this point all backups
contain the inconsistencies.) The DBCC command now completes without
errors, but we worry that data (actual "row" data, not just index data)
might have been lost. We also worry about resulting integrity problems,
orphaned foreign key references, etc.
It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
be the command we are looking for. If we understand things correctly, it
will report rows that violate some constraint.
Is our thinking correct here? Will system tables and constraints be checked
too? Is there anything else we should be concerned about? (Other than lost
business data, and a UPS for the customer, of course.)
Any words, links, and thoughts of your will be very much appreciated.
Thanks in advance for your time!
James Hunter Ross
Senior Software Developer
O'Neil Software, Inc.Hi
DBCC CHECKCONSTRAINTS will check the integrity of CHECK constraints and FKs
wrt to the data that is present, but it won't tell you if consistencies not
enforced in the database are still correct or if both referenced/referencing
data is missing. If you have copies of historical reports you may want to ru
n
them to compare what they returned previously and now.
John
"James Hunter Ross" wrote:
> Friends,
> A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
> discovering inconsistencies after a catastrophic power failure. (They
> didn't even suspect trouble until weeks later, and at this point all backu
ps
> contain the inconsistencies.) The DBCC command now completes without
> errors, but we worry that data (actual "row" data, not just index data)
> might have been lost. We also worry about resulting integrity problems,
> orphaned foreign key references, etc.
> It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
> be the command we are looking for. If we understand things correctly, it
> will report rows that violate some constraint.
> Is our thinking correct here? Will system tables and constraints be check
ed
> too? Is there anything else we should be concerned about? (Other than lo
st
> business data, and a UPS for the customer, of course.)
> Any words, links, and thoughts of your will be very much appreciated.
> Thanks in advance for your time!
> James Hunter Ross
> Senior Software Developer
> O'Neil Software, Inc.
>
>
DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS...
Friends,
A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
discovering inconsistencies after a catastrophic power failure. (They
didn't even suspect trouble until weeks later, and at this point all backups
contain the inconsistencies.) The DBCC command now completes without
errors, but we worry that data (actual "row" data, not just index data)
might have been lost. We also worry about resulting integrity problems,
orphaned foreign key references, etc.
It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
be the command we are looking for. If we understand things correctly, it
will report rows that violate some constraint.
Is our thinking correct here? Will system tables and constraints be checked
too? Is there anything else we should be concerned about? (Other than lost
business data, and a UPS for the customer, of course.)
Any words, links, and thoughts of your will be very much appreciated.
Thanks in advance for your time!
James Hunter Ross
Senior Software Developer
O'Neil Software, Inc.Hi
DBCC CHECKCONSTRAINTS will check the integrity of CHECK constraints and FKs
wrt to the data that is present, but it won't tell you if consistencies not
enforced in the database are still correct or if both referenced/referencing
data is missing. If you have copies of historical reports you may want to run
them to compare what they returned previously and now.
John
"James Hunter Ross" wrote:
> Friends,
> A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
> discovering inconsistencies after a catastrophic power failure. (They
> didn't even suspect trouble until weeks later, and at this point all backups
> contain the inconsistencies.) The DBCC command now completes without
> errors, but we worry that data (actual "row" data, not just index data)
> might have been lost. We also worry about resulting integrity problems,
> orphaned foreign key references, etc.
> It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
> be the command we are looking for. If we understand things correctly, it
> will report rows that violate some constraint.
> Is our thinking correct here? Will system tables and constraints be checked
> too? Is there anything else we should be concerned about? (Other than lost
> business data, and a UPS for the customer, of course.)
> Any words, links, and thoughts of your will be very much appreciated.
> Thanks in advance for your time!
> James Hunter Ross
> Senior Software Developer
> O'Neil Software, Inc.
>
>
A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
discovering inconsistencies after a catastrophic power failure. (They
didn't even suspect trouble until weeks later, and at this point all backups
contain the inconsistencies.) The DBCC command now completes without
errors, but we worry that data (actual "row" data, not just index data)
might have been lost. We also worry about resulting integrity problems,
orphaned foreign key references, etc.
It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
be the command we are looking for. If we understand things correctly, it
will report rows that violate some constraint.
Is our thinking correct here? Will system tables and constraints be checked
too? Is there anything else we should be concerned about? (Other than lost
business data, and a UPS for the customer, of course.)
Any words, links, and thoughts of your will be very much appreciated.
Thanks in advance for your time!
James Hunter Ross
Senior Software Developer
O'Neil Software, Inc.Hi
DBCC CHECKCONSTRAINTS will check the integrity of CHECK constraints and FKs
wrt to the data that is present, but it won't tell you if consistencies not
enforced in the database are still correct or if both referenced/referencing
data is missing. If you have copies of historical reports you may want to run
them to compare what they returned previously and now.
John
"James Hunter Ross" wrote:
> Friends,
> A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
> discovering inconsistencies after a catastrophic power failure. (They
> didn't even suspect trouble until weeks later, and at this point all backups
> contain the inconsistencies.) The DBCC command now completes without
> errors, but we worry that data (actual "row" data, not just index data)
> might have been lost. We also worry about resulting integrity problems,
> orphaned foreign key references, etc.
> It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
> be the command we are looking for. If we understand things correctly, it
> will report rows that violate some constraint.
> Is our thinking correct here? Will system tables and constraints be checked
> too? Is there anything else we should be concerned about? (Other than lost
> business data, and a UPS for the customer, of course.)
> Any words, links, and thoughts of your will be very much appreciated.
> Thanks in advance for your time!
> James Hunter Ross
> Senior Software Developer
> O'Neil Software, Inc.
>
>
DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS...
Friends,
A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
discovering inconsistencies after a catastrophic power failure. (They
didn't even suspect trouble until weeks later, and at this point all backups
contain the inconsistencies.) The DBCC command now completes without
errors, but we worry that data (actual "row" data, not just index data)
might have been lost. We also worry about resulting integrity problems,
orphaned foreign key references, etc.
It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
be the command we are looking for. If we understand things correctly, it
will report rows that violate some constraint.
Is our thinking correct here? Will system tables and constraints be checked
too? Is there anything else we should be concerned about? (Other than lost
business data, and a UPS for the customer, of course.)
Any words, links, and thoughts of your will be very much appreciated.
Thanks in advance for your time!
James Hunter Ross
Senior Software Developer
O'Neil Software, Inc.
Hi
DBCC CHECKCONSTRAINTS will check the integrity of CHECK constraints and FKs
wrt to the data that is present, but it won't tell you if consistencies not
enforced in the database are still correct or if both referenced/referencing
data is missing. If you have copies of historical reports you may want to run
them to compare what they returned previously and now.
John
"James Hunter Ross" wrote:
> Friends,
> A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
> discovering inconsistencies after a catastrophic power failure. (They
> didn't even suspect trouble until weeks later, and at this point all backups
> contain the inconsistencies.) The DBCC command now completes without
> errors, but we worry that data (actual "row" data, not just index data)
> might have been lost. We also worry about resulting integrity problems,
> orphaned foreign key references, etc.
> It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
> be the command we are looking for. If we understand things correctly, it
> will report rows that violate some constraint.
> Is our thinking correct here? Will system tables and constraints be checked
> too? Is there anything else we should be concerned about? (Other than lost
> business data, and a UPS for the customer, of course.)
> Any words, links, and thoughts of your will be very much appreciated.
> Thanks in advance for your time!
> James Hunter Ross
> Senior Software Developer
> O'Neil Software, Inc.
>
>
A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
discovering inconsistencies after a catastrophic power failure. (They
didn't even suspect trouble until weeks later, and at this point all backups
contain the inconsistencies.) The DBCC command now completes without
errors, but we worry that data (actual "row" data, not just index data)
might have been lost. We also worry about resulting integrity problems,
orphaned foreign key references, etc.
It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
be the command we are looking for. If we understand things correctly, it
will report rows that violate some constraint.
Is our thinking correct here? Will system tables and constraints be checked
too? Is there anything else we should be concerned about? (Other than lost
business data, and a UPS for the customer, of course.)
Any words, links, and thoughts of your will be very much appreciated.
Thanks in advance for your time!
James Hunter Ross
Senior Software Developer
O'Neil Software, Inc.
Hi
DBCC CHECKCONSTRAINTS will check the integrity of CHECK constraints and FKs
wrt to the data that is present, but it won't tell you if consistencies not
enforced in the database are still correct or if both referenced/referencing
data is missing. If you have copies of historical reports you may want to run
them to compare what they returned previously and now.
John
"James Hunter Ross" wrote:
> Friends,
> A customer of ours had to do a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS after
> discovering inconsistencies after a catastrophic power failure. (They
> didn't even suspect trouble until weeks later, and at this point all backups
> contain the inconsistencies.) The DBCC command now completes without
> errors, but we worry that data (actual "row" data, not just index data)
> might have been lost. We also worry about resulting integrity problems,
> orphaned foreign key references, etc.
> It appears that the command DBCC CHECKCONSTRAINTS WITH ALL_ERRORMSGS might
> be the command we are looking for. If we understand things correctly, it
> will report rows that violate some constraint.
> Is our thinking correct here? Will system tables and constraints be checked
> too? Is there anything else we should be concerned about? (Other than lost
> business data, and a UPS for the customer, of course.)
> Any words, links, and thoughts of your will be very much appreciated.
> Thanks in advance for your time!
> James Hunter Ross
> Senior Software Developer
> O'Neil Software, Inc.
>
>
DBCC CHECKCONSTRAINTS
Hi all,
I run a
DBCC CHECKCONSTRAINTS WITH ALL_CONSTRAINTS
on my database, and i am prompted this message :
Server: Msg 8170, Level 16, State 2, Line 1
Insufficient result space to convert uniqueidentifier value to char.
The statement has been terminated.
I have tried to specify a table, and it seems to be caused by a
non-validating foreign key in the uniqueidentifier type.
I have found (on the web and this newsgroup) several posts about this
problem, but nobody gave (or found ?) the explaination/solution.
Can anybody tell me how to solve this problem ?
Thanks
PS :
Hope my frenchy english is clear enough ...
I need this DBCC, so don't explain me how to prevent FK violation ;o).
We have fixed this bug in SP4 for SQL 2000. Have you tried the beta yet? You can sign up at http://support.microsoft.com/default...;en-us;290211. Please let us know if you still have problems.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
"SFauvel" <sylvainfauvel@.free.fr> wrote in message news:7a9148e7.0501210833.be22e21@.posting.google.co m...
> Hi all,
> I run a
> DBCC CHECKCONSTRAINTS WITH ALL_CONSTRAINTS
> on my database, and i am prompted this message :
> Server: Msg 8170, Level 16, State 2, Line 1
> Insufficient result space to convert uniqueidentifier value to char.
> The statement has been terminated.
> I have tried to specify a table, and it seems to be caused by a
> non-validating foreign key in the uniqueidentifier type.
> I have found (on the web and this newsgroup) several posts about this
> problem, but nobody gave (or found ?) the explaination/solution.
> Can anybody tell me how to solve this problem ?
> Thanks
> PS :
> Hope my frenchy english is clear enough ...
> I need this DBCC, so don't explain me how to prevent FK violation ;o).
I run a
DBCC CHECKCONSTRAINTS WITH ALL_CONSTRAINTS
on my database, and i am prompted this message :
Server: Msg 8170, Level 16, State 2, Line 1
Insufficient result space to convert uniqueidentifier value to char.
The statement has been terminated.
I have tried to specify a table, and it seems to be caused by a
non-validating foreign key in the uniqueidentifier type.
I have found (on the web and this newsgroup) several posts about this
problem, but nobody gave (or found ?) the explaination/solution.
Can anybody tell me how to solve this problem ?
Thanks
PS :
Hope my frenchy english is clear enough ...
I need this DBCC, so don't explain me how to prevent FK violation ;o).
We have fixed this bug in SP4 for SQL 2000. Have you tried the beta yet? You can sign up at http://support.microsoft.com/default...;en-us;290211. Please let us know if you still have problems.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
"SFauvel" <sylvainfauvel@.free.fr> wrote in message news:7a9148e7.0501210833.be22e21@.posting.google.co m...
> Hi all,
> I run a
> DBCC CHECKCONSTRAINTS WITH ALL_CONSTRAINTS
> on my database, and i am prompted this message :
> Server: Msg 8170, Level 16, State 2, Line 1
> Insufficient result space to convert uniqueidentifier value to char.
> The statement has been terminated.
> I have tried to specify a table, and it seems to be caused by a
> non-validating foreign key in the uniqueidentifier type.
> I have found (on the web and this newsgroup) several posts about this
> problem, but nobody gave (or found ?) the explaination/solution.
> Can anybody tell me how to solve this problem ?
> Thanks
> PS :
> Hope my frenchy english is clear enough ...
> I need this DBCC, so don't explain me how to prevent FK violation ;o).
DBCC CHECKCONSTRAINTS
Hi all,
I run a
DBCC CHECKCONSTRAINTS WITH ALL_CONSTRAINTS
on my database, and i am prompted this message :
Server: Msg 8170, Level 16, State 2, Line 1
Insufficient result space to convert uniqueidentifier value to char.
The statement has been terminated.
I have tried to specify a table, and it seems to be caused by a
non-validating foreign key in the uniqueidentifier type.
I have found (on the web and this newsgroup) several posts about this
problem, but nobody gave (or found ') the explaination/solution.
Can anybody tell me how to solve this problem ?
Thanks
PS :
Hope my frenchy english is clear enough ...
I need this DBCC, so don't explain me how to prevent FK violation ;o).This is a multi-part message in MIME format.
--=_NextPart_000_007F_01C4FFB4.8F43D500
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
We have fixed this bug in SP4 for SQL 2000. Have you tried the beta =yet? You can sign up at =http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;290211. =Please let us know if you still have problems.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
"SFauvel" <sylvainfauvel@.free.fr> wrote in message =news:7a9148e7.0501210833.be22e21@.posting.google.com...
> Hi all,
> > I run a > DBCC CHECKCONSTRAINTS WITH ALL_CONSTRAINTS
> on my database, and i am prompted this message :
> > Server: Msg 8170, Level 16, State 2, Line 1
> Insufficient result space to convert uniqueidentifier value to char.
> The statement has been terminated.
> > I have tried to specify a table, and it seems to be caused by a
> non-validating foreign key in the uniqueidentifier type.
> > I have found (on the web and this newsgroup) several posts about this
> problem, but nobody gave (or found ') the explaination/solution.
> Can anybody tell me how to solve this problem ? > > Thanks
> > PS : > Hope my frenchy english is clear enough ...
> I need this DBCC, so don't explain me how to prevent FK violation ;o).
--=_NextPart_000_007F_01C4FFB4.8F43D500
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
We have fixed this bug in SP4 for SQL 2000. =Have you tried the beta yet? You can sign up at http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;290211.&nb=sp; Please let us know if you still have problems.
Thanks,
Ryan StonecipherMicrosoft SQL Server Storage =Engine, DBCC
"SFauvel" wrote in message news:7a9148e7.0501210833.be22e21@.posting.google.com...> =Hi all,> > I run a > DBCC CHECKCONSTRAINTS WITH =ALL_CONSTRAINTS> on my database, and i am prompted this message :> > Server: =Msg 8170, Level 16, State 2, Line 1> Insufficient result space to convert uniqueidentifier value to char.> The statement has been terminated.> > I have tried to specify a table, and it =seems to be caused by a> non-validating foreign key in the uniqueidentifier type.> > I have found (on the web and this newsgroup) =several posts about this> problem, but nobody gave (or found ') the explaination/solution.> Can anybody tell me how to solve this =problem ? > > Thanks> > PS : > Hope my frenchy =english is clear enough ...> I need this DBCC, so don't explain me how to =prevent FK violation ;o).
--=_NextPart_000_007F_01C4FFB4.8F43D500--
I run a
DBCC CHECKCONSTRAINTS WITH ALL_CONSTRAINTS
on my database, and i am prompted this message :
Server: Msg 8170, Level 16, State 2, Line 1
Insufficient result space to convert uniqueidentifier value to char.
The statement has been terminated.
I have tried to specify a table, and it seems to be caused by a
non-validating foreign key in the uniqueidentifier type.
I have found (on the web and this newsgroup) several posts about this
problem, but nobody gave (or found ') the explaination/solution.
Can anybody tell me how to solve this problem ?
Thanks
PS :
Hope my frenchy english is clear enough ...
I need this DBCC, so don't explain me how to prevent FK violation ;o).This is a multi-part message in MIME format.
--=_NextPart_000_007F_01C4FFB4.8F43D500
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
We have fixed this bug in SP4 for SQL 2000. Have you tried the beta =yet? You can sign up at =http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;290211. =Please let us know if you still have problems.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
"SFauvel" <sylvainfauvel@.free.fr> wrote in message =news:7a9148e7.0501210833.be22e21@.posting.google.com...
> Hi all,
> > I run a > DBCC CHECKCONSTRAINTS WITH ALL_CONSTRAINTS
> on my database, and i am prompted this message :
> > Server: Msg 8170, Level 16, State 2, Line 1
> Insufficient result space to convert uniqueidentifier value to char.
> The statement has been terminated.
> > I have tried to specify a table, and it seems to be caused by a
> non-validating foreign key in the uniqueidentifier type.
> > I have found (on the web and this newsgroup) several posts about this
> problem, but nobody gave (or found ') the explaination/solution.
> Can anybody tell me how to solve this problem ? > > Thanks
> > PS : > Hope my frenchy english is clear enough ...
> I need this DBCC, so don't explain me how to prevent FK violation ;o).
--=_NextPart_000_007F_01C4FFB4.8F43D500
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
We have fixed this bug in SP4 for SQL 2000. =Have you tried the beta yet? You can sign up at http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;290211.&nb=sp; Please let us know if you still have problems.
Thanks,
Ryan StonecipherMicrosoft SQL Server Storage =Engine, DBCC
"SFauvel"
--=_NextPart_000_007F_01C4FFB4.8F43D500--
DBCC CHECKCONSTRAINTS
Hi all,
I run a
DBCC CHECKCONSTRAINTS WITH ALL_CONSTRAINTS
on my database, and i am prompted this message :
Server: Msg 8170, Level 16, State 2, Line 1
Insufficient result space to convert uniqueidentifier value to char.
The statement has been terminated.
I have tried to specify a table, and it seems to be caused by a
non-validating foreign key in the uniqueidentifier type.
I have found (on the web and this newsgroup) several posts about this
problem, but nobody gave (or found ') the explaination/solution.
Can anybody tell me how to solve this problem ?
Thanks
PS :
Hope my frenchy english is clear enough ...
I need this DBCC, so don't explain me how to prevent FK violation ;o).We have fixed this bug in SP4 for SQL 2000. Have you tried the beta yet? You can sign
up at http://support.microsoft.com/defaul...b;en-us;290211. Plea
se let us know if you still have problems.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
"SFauvel" <sylvainfauvel@.free.fr> wrote in message news:7a9148e7.0501210833.be22e21@.posting.
google.com...
> Hi all,
>
> I run a
> DBCC CHECKCONSTRAINTS WITH ALL_CONSTRAINTS
> on my database, and i am prompted this message :
>
> Server: Msg 8170, Level 16, State 2, Line 1
> Insufficient result space to convert uniqueidentifier value to char.
> The statement has been terminated.
>
> I have tried to specify a table, and it seems to be caused by a
> non-validating foreign key in the uniqueidentifier type.
>
> I have found (on the web and this newsgroup) several posts about this
> problem, but nobody gave (or found ') the explaination/solution.
> Can anybody tell me how to solve this problem ?
>
> Thanks
>
> PS :
> Hope my frenchy english is clear enough ...
> I need this DBCC, so don't explain me how to prevent FK violation ;o).
I run a
DBCC CHECKCONSTRAINTS WITH ALL_CONSTRAINTS
on my database, and i am prompted this message :
Server: Msg 8170, Level 16, State 2, Line 1
Insufficient result space to convert uniqueidentifier value to char.
The statement has been terminated.
I have tried to specify a table, and it seems to be caused by a
non-validating foreign key in the uniqueidentifier type.
I have found (on the web and this newsgroup) several posts about this
problem, but nobody gave (or found ') the explaination/solution.
Can anybody tell me how to solve this problem ?
Thanks
PS :
Hope my frenchy english is clear enough ...
I need this DBCC, so don't explain me how to prevent FK violation ;o).We have fixed this bug in SP4 for SQL 2000. Have you tried the beta yet? You can sign
up at http://support.microsoft.com/defaul...b;en-us;290211. Plea
se let us know if you still have problems.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
"SFauvel" <sylvainfauvel@.free.fr> wrote in message news:7a9148e7.0501210833.be22e21@.posting.
google.com...
> Hi all,
>
> I run a
> DBCC CHECKCONSTRAINTS WITH ALL_CONSTRAINTS
> on my database, and i am prompted this message :
>
> Server: Msg 8170, Level 16, State 2, Line 1
> Insufficient result space to convert uniqueidentifier value to char.
> The statement has been terminated.
>
> I have tried to specify a table, and it seems to be caused by a
> non-validating foreign key in the uniqueidentifier type.
>
> I have found (on the web and this newsgroup) several posts about this
> problem, but nobody gave (or found ') the explaination/solution.
> Can anybody tell me how to solve this problem ?
>
> Thanks
>
> PS :
> Hope my frenchy english is clear enough ...
> I need this DBCC, so don't explain me how to prevent FK violation ;o).
Subscribe to:
Posts (Atom)