![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Thread-Topic: The sort order specified for distinct count records is incorrect. thread-index: AcYwY8OmKqbHpXZTS2KcoX4hIzB6sA== X-WBNR-Posting-Host: 203.202.23.100 From: "=?Utf-8?B?QWNpdXM=?=" <acius (AT) nospam (DOT) nospam Subject: The sort order specified for distinct count records is incorrect. Date: Sun, 12 Feb 2006 22:07:26 -0800 Lines: 17 Message-ID: <EB2D80DE-3BE1-4579-BC8E-A072DF317F63 (AT) microsoft (DOT) com MIME-Version: 1.0 Content-Type: text/plain; charset="Utf-8" Content-Transfer-Encoding: 7bit X-Newsreader: Microsoft CDO for Windows 2000 Content-Class: urn:content-classes:message Importance: normal Priority: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 Newsgroups: microsoft.public.sqlserver.olap NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250 Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.olap:67148 X-Tomcat-NG: microsoft.public.sqlserver.olap Getting the following error Errors in the OLAP storage engine: The sort order specified for distinct count records is incorrect. setting CheckDistinctRecordSortOrder to 0 gets around the error but why does it happen? Since Analysis Services 2005 generates the query and the sort wouldn't it have to be in the correct order? The query being run has ORDER BY "AS_PAYROLL_VCZP"."EMP_ID" ASC so the sort is happening. The problem has only happened on queries returning 1 million+ records, could the message be volume(or time to process) related? Thanks |
#3
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |