Microsoft KB Archive/275135

Knowledge Base

FIX: StrToSet Function Returns Error Message when String is Over 1 K in Size

Article ID: 275135

Article Last Modified on 8/7/2006

---

APPLIES TO

• Microsoft SQL Server OLAP Services

---

This article was previously published under Q275135

BUG #: 11193 (PLATO 7.X)

SYMPTOMS

Use of the Multi-Dimensional Expression (MDX) function StrToSet to convert a String to a Set results in an error if the string size is over 1 K.

WORKAROUND

Reduce the size of the input string for the StrToSet function to less than 1 K.

STATUS

Microsoft has confirmed this to be a problem in SQL Server OLAP Services version 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server OLAP Services version 7.0. For information about how to download and install the latest SQL Server OLAP Services Service Pack, see the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?familyid=F62F45E9-24ED-4FA6-BD74-8A26606F96D8

For more information, contact your primary support provider.

This problem does not occur in Microsoft SQL Server 2000 Analysis Services version 8.0.

MORE INFORMATION

Steps to Reproduce the Behavior

1. Run the MDX Sample Application.
2. Connect to the Foodmart sample database.

3. Run the following query from the MDX sample:

   Select StrToSet(
   "{customers.city.langley,
   customers.city.burnaby,customers.city.cliffside,customers.city.haney,
   customers.city.ladner,customers.city.langford,customers.city.metchosin,
   customers.city.[N. vancouver],customers.city.newton,customers.city.[Oak Bay],
   customers.city.[Port Hammond],customers.city.Richmond,customers.city.[Royal Oak],
   customers.city.shawnee,customers.city.sooke,customers.city.vancouver,
   customers.city.victoria,customers.city.westminster,customers.city.[san Andres],
   customers.city.[Santa Anita],customers.city.[Santa Fe],customers.city.Tixapan,
   customers.city.Acapulco,customers.city.Guadalajara,customers.city.[Mexico City],
   customers.city.Tlaxiaco,customers.city.[La Cruz],customers.city.Orizaba,
   customers.city.merida,customers.city.Camacho,customers.city.Hidalgo,
   customers.city.Altadena,customers.city.Arcadia,customers.city.Bellflower,
   customers.city.Berkeley,customers.city.[Beverly Hills],customers.city.Burbank,
   customers.city.Burlingame,customers.city.[Chula Vista],customers.city.Colma,
   customers.city.Concord,customers.city.coronado,customers.city.[Daly City],
   customers.city.Downey,customers.city.[El Cajon],customers.city.Fremont,
   customers.city.Glendale,customers.city.Grossmont,customers.city.[Imperial Beach],
   customers.city.[La Jolla],customers.city.[La Mesa],customers.city.Lakewood,
   customers.city.[Lemon Grove],customers.city.[Lincoln Acres],customers.city.[Long Beach],
   customers.city.[Los Angeles],customers.city.[Mill Valley],customers.city1.[National City],
   customers.city.[Newport Beach]}") 
   on Columns from Sales
                       

Expected results:

• To accept a string of the input size.
  

-or-

• To trap the error and return the appropriate error message, which indicates the string size limitation.

Observed results: Error messages similar to the following occur:

Memory could not be read.

-or-

Abnormal Program Termination

-or-

MDX syntax error.

Afterwards, the MDX sample is unstable and does not run another query until you restart the MDX Sample application.

Keywords: kbbug kbcodesnippet kbfix KB275135

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.