August 11, 2016 at 7:02 am
I'm getting two errors when a Database Consistency errors which are the except the object is executed:
The spatial index, XML index or indexed view 'sys.extended_index_1682469418_384000' (object ID 1239532045) does not contain all rows that the view definition produces.
I'm trying to find a solution.
Does anyone recognize error an know how to resolve it?
What action is needed t resolve the issue?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 11, 2016 at 8:02 am
Have you tried dropping & recreating the index on that view? (No, I don't mean using the REBUILD, I mean drop & recreate...)
Got to love DBCC CHECKDB bugs that are closed as "Won't Fix"... https://connect.microsoft.com/SQLServer/feedback/details/795478/unfixable-dbcc-checkdb-error-that-is-also-a-false-positive-and-otherwise-strange
Thomas Rushton
blog: https://thelonedba.wordpress.com
August 11, 2016 at 8:12 am
I was trying to determine what the command would be since I do not think I have the actual index name?
I saw that link that you provided.
Thanks.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 11, 2016 at 8:37 am
How do I get the parent Object?
The following gives me the name of the Index:
select OBJECT_NAME(1239532045)
It returns:
extended_index_1682469418_384000
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 11, 2016 at 9:14 am
I run the following command and it display the table and the extended index name:
SELECT
OBJECT_NAME(PARENT_OBJECT_ID) AS table_object,
name,
create_date
FROM sys.internal_tables it
WHERE INTERNAL_TYPE = 207
AND it.name = 'extended_index_1682469418_384000'
How do resolve the consistency error?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 11, 2016 at 10:00 am
A developer created a spatial index and after it was created the error occurred on the DBCC Command.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 11, 2016 at 10:15 am
I have been searching for a solution.
It appears to be a bug that is not fixable.
Any ideas?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 11, 2016 at 12:28 pm
ThomasRushton (8/11/2016)
Have you tried dropping & recreating the index on that view?
as in, drop the spacial index and recreate it.
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 11, 2016 at 12:43 pm
GilaMonster (8/11/2016)
ThomasRushton (8/11/2016)
Have you tried dropping & recreating the index on that view?as in, drop the spacial index and recreate it.
That is what I wanted to do but I was told not to do that.
I also read a threat that said that would not resolve the issue.
Is there any risk in doing this?
Thanks for your input.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 11, 2016 at 12:46 pm
Welsh Corgi (8/11/2016)
GilaMonster (8/11/2016)
ThomasRushton (8/11/2016)
Have you tried dropping & recreating the index on that view?as in, drop the spacial index and recreate it.
That is what I wanted to do but I was told not to do that.
By who?
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 11, 2016 at 12:48 pm
I run the following command in a test environment which contains the same index and I do not get any errors:
DBCC CHECKDB(PrismData)
WITH EXTENDED_LOGICAL_CHECKS, DATA_PURITY, NO_INFOMSGS, ALL_ERRORMSGS, TABLERESULTS
Hmm.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 11, 2016 at 12:54 pm
Welsh Corgi (8/11/2016)
I run the following command in a test environment which contains the same index and I do not get any errors:
DBCC CHECKDB(PrismData)
WITH EXTENDED_LOGICAL_CHECKS, DATA_PURITY, NO_INFOMSGS, ALL_ERRORMSGS, TABLERESULTS
Hmm.
Why would you expect to get the same corruption on a different database?
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 11, 2016 at 1:16 pm
GilaMonster (8/11/2016)
Welsh Corgi (8/11/2016)
GilaMonster (8/11/2016)
ThomasRushton (8/11/2016)
Have you tried dropping & recreating the index on that view?as in, drop the spacial index and recreate it.
That is what I wanted to do but I was told not to do that.
By who?
The person that created it.
I did not know that it was created until this morning.:unsure:
Thanks.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 11, 2016 at 1:53 pm
Welsh Corgi (8/11/2016)
GilaMonster (8/11/2016)
Welsh Corgi (8/11/2016)
GilaMonster (8/11/2016)
ThomasRushton (8/11/2016)
Have you tried dropping & recreating the index on that view?as in, drop the spacial index and recreate it.
That is what I wanted to do but I was told not to do that.
By who?
The person that created it.
Then ask that person how to fix it, if they know more than I do about corruption.
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 11, 2016 at 1:57 pm
Gail,
I know that you no more than just about anyone.
I ask him to fix it but he declined.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 15 posts - 1 through 15 (of 27 total)
You must be logged in to reply to this topic. Login to reply