Answered by:
DBCC fails on columnstore index

Question
-
Hi,
we have a tabel with a columnstore index where DBCC fails with the following error:
Msg 5283, Level 16, State 1, Line 1CREATE TABLE [dbo].[factLossToLayer](
[ByesId] [bigint] NOT NULL,
[ByesSequenceID] [bigint] NOT NULL,
[EventID] [bigint] NOT NULL,
[TrialID] [int] NOT NULL,
[TimeOfLossTK] [int] NOT NULL,
[CeltTK] [int] NOT NULL,
[RltTK] [int] NOT NULL,
[BetTK] [int] NOT NULL,
[PMLAreaTK] [int] NOT NULL,
[EventTK] [int] NOT NULL,
[EventPropertiesTK] [int] NOT NULL,
[EventOccurrenceTK] [int] NOT NULL,
[ContractTK] [int] NOT NULL,
[ModelGroupTK] [int] NOT NULL,
[ModelTK] [int] NOT NULL,
[OriginalCurrencyTK] [int] NOT NULL,
[CededLossOriginalCurrency] [money] NOT NULL,
[GrossAmountOriginalCurrency] [money] NOT NULL,
[GrossNetAmountOriginalCurrency] [money] NOT NULL,
[CededLossUSD] [money] NOT NULL,
[GrossAmountUSD] [money] NOT NULL,
[GrossNetAmountUSD] [money] NOT NULL,
[ReinstatementPremiumToPremiumRatio] [decimal](18, 16) NOT NULL,
[ReinstatementPremiumAmountOriginalCurrency] [money] NOT NULL,
[ReinstatementPremiumAmountUSD] [money] NOT NULL,
[ReinstatementPremiumGrossNetAmountOriginalCurrency] [money] NOT NULL,
[ReinstatementPremiumGrossNetAmountUSD] [money] NOT NULL,
[TaxFactor] [decimal](8, 7) NULL,
[RltRowFraction] [decimal](18, 17) NOT NULL,
[PackageExecutionId] [int] NOT NULL,
[RowInserted] [datetime] NOT NULLThe Cross Rowset check on columnstore index object ID 299148111, index ID 16, partition ID 72057698163752960. Drop and recreate the columnstore index.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'factLossToLayer' (object ID 299148111).
CHECKDB found 0 allocation errors and 1 consistency errors in database 'GPIR_DM_Prod'.
I found a blog statiting that states that "Right now, a columnstore index supports only common business data types like int, real, string, money, datetime, the decimal data type has to be less than 18 digits."
But that was on CTP3 and our developers states that the limitation is "up to" 18 digits for decimal...
We have two columns with decimal 18, could that be the problem ? I have tried dropping the index and recreating, but I get the same error.
The server is on 11.0.2332 and here is a table and index definition:
CREATE NONCLUSTERED COLUMNSTORE INDEX [csx_factLossToLayer] ON [dbo].[factLossToLayer]
(
[ByesId],
[ByesSequenceID],
[EventID],
[TrialID],
[TimeOfLossTK],
[CeltTK],
[RltTK],
[BetTK],
[PMLAreaTK],
[EventTK],
[EventPropertiesTK],
[EventOccurrenceTK],
[ContractTK],
[ModelGroupTK],
[ModelTK],
[OriginalCurrencyTK],
[CededLossOriginalCurrency],
[GrossAmountOriginalCurrency],
[GrossNetAmountOriginalCurrency],
[CededLossUSD],
[GrossAmountUSD],
[GrossNetAmountUSD],
[ReinstatementPremiumToPremiumRatio],
[ReinstatementPremiumAmountOriginalCurrency],
[ReinstatementPremiumAmountUSD],
[ReinstatementPremiumGrossNetAmountOriginalCurrency],
[ReinstatementPremiumGrossNetAmountUSD],
[TaxFactor],
[RltRowFraction],
[PackageExecutionId],
[RowInserted]
)WITH (DROP_EXISTING = OFF)
GOMonday, November 5, 2012 1:36 PM
Answers
-
Hello Staffan,
What is your SQL Server build? I think this is fixed in SP1.
Apply SP1 and let me know if it resolves the issue.
http://www.microsoft.com/en-us/download/details.aspx?id=34700
Thank you,
Karthick P.K |My Facebook Group |My Site| Blog Space |Twitter
Please click the Mark as answer button and vote as helpful if this reply solves your problem
- Proposed as answer by Shulei Chen Tuesday, November 13, 2012 9:22 AM
- Marked as answer by Shulei Chen Monday, November 19, 2012 9:27 AM
Monday, November 5, 2012 2:29 PM
All replies
-
Hello Staffan,
What is your SQL Server build? I think this is fixed in SP1.
Apply SP1 and let me know if it resolves the issue.
http://www.microsoft.com/en-us/download/details.aspx?id=34700
Thank you,
Karthick P.K |My Facebook Group |My Site| Blog Space |Twitter
Please click the Mark as answer button and vote as helpful if this reply solves your problem
- Proposed as answer by Shulei Chen Tuesday, November 13, 2012 9:22 AM
- Marked as answer by Shulei Chen Monday, November 19, 2012 9:27 AM
Monday, November 5, 2012 2:29 PM -
I am getting the same error. Dropped and recreated the index and still get the error.
Msg 5283, Level 16, State 1, Line 2
The Cross Rowset check on columnstore index object ID 912722304, index ID 3, partition ID 72057595237302272. Drop and recreate the columnstore index.
DBCC results for 'FactTransactionLines'.
There are 8321458 rows in 229413 pages for object "FactTransactionLines".
CHECKTABLE found 0 allocation errors and 1 consistency errors in table 'FactTransactionLines' (object ID 912722304).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
I am on SP1. Here is exact version:
Microsoft SQL Server 2012 (SP1) - 11.0.3339.0 (X64)
Jan 14 2013 19:02:10
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Monday, May 13, 2013 3:08 PM -
Can some one confirm if the above said issue has been fixed in 2012 SP2 ?
bcoz I'm getting same error in 2012 SP2 server
- Edited by laksinfo22 Thursday, September 1, 2016 11:16 AM
Thursday, September 1, 2016 11:16 AM