Home Dashboard Directory Help
Search

The size specified for a binding was too small by Pieter M


Status: 

Closed
 as Won't Fix Help for as Won't Fix


8
0
Sign in
to vote
Type: Bug
ID: 219329
Opened: 10/6/2006 1:20:43 AM
Access Restriction: Public
4
Workaround(s)
view
5
User(s) can reproduce this bug

Description

In a SQL Server 2005 Analysis Services project I have the following problem:
when a column width is changed (e.g from 5 to 6) in the relational database and I refresh the dsv in the analysis services project. Not in all places the column value gets updated. When I check the dsv and the dimensions containing this column is set to the right value.
But when I deploy and process the cube I get the following error:

Errors in the back-end database access module. The size specified for a binding was too small,
resulting in one or more column values being truncated.
Errors in the OLAP storage engine: An error occurred while processing the 'Gefactureerde Dienst' partition of the 'Gefactureerde Dienst' measure group for the 'FMR DWH Afgenomen Dienst' cube from the FMR_Kubus database.


When I check the XML of the cube I see that not all widths are updated to the new value.
Details
Sign in to post a comment.
Posted by RajibDotnet on 3/22/2012 at 3:46 PM
Helped me...a trickier one...though
Posted by Valentino Vranken on 3/20/2012 at 1:08 AM
Thank you Darren for mention the BIDSHelper's Dimension Data Type Discrepancy Check feature, it certainly does the works!
Posted by pungit on 12/13/2010 at 1:19 PM
My employer has SSAS on SS2005 and we use the services to support Sales Order analytic's. When I was recently asked to add several fields, drop several others and to add width to several more, most of my work went relatively smoothly. That is until I modified my source feeders (dimension and fact tables). The problem arose when I took a program group id and sales rep id field and added the respective description/name to the fields. This took the fields from 15 character original format to 80 characters.
I found all updates and processing performed properly when (from within VS2008/BIDS) I processed the dimension structure (from Solution Explorer - Dimension - Customer (right click Open) then click on the recycle wheel to process the dimension). Except I received the error noted above.
My solution was relatively simple; In the same Dimension Structure pane of the server explorer, I selected the attribute (field) and then hopped over to the Properties pane and walked through the KeyColumns and NameColumns settings to verify they matched (80=80).
Unfortunately sometimes edits don't make it through (MS Bug) and this needs to be checked/validated. A quick chig-a-tee-boo later and where 80 = 15 (WRONG) was now corrected to 80=80 and fixed.

In all development and maintenance should not rely on automated solutions to always work, so you should have a fall back plan to know-how to correct your code by object if need be. The work around's listed on the following page lead down the same path.

Cheers!
Posted by jvickers on 12/16/2008 at 7:03 AM
This problem still exists in SSAS 2008
Posted by Microsoft on 12/7/2007 at 1:44 PM
Thanks for reporting this issue. Currently the UI provides no means for automatically updating the design of the cube to reflect changes made to the relational data source. This is a complex area which we are hoping to address in a future version.
Posted by Microsoft on 1/9/2007 at 1:13 PM
Thanks for reporting this issue. Currently the UI provides no means for automatically updating the design of the cube to reflect changes made to the relational data source. This is a complex area which we are hoping to address in a future version.

- Matt Carroll
Posted by Microsoft on 10/6/2006 at 12:00 PM
Thank you for reporting this issue. We will investigate and get back to you.
Posted by Microsoft on 10/6/2006 at 11:59 AM
Thank you for reporting this issue. We will investigate and get back to you.
Sign in to post a workaround.
Posted by SwapnilKothari on 2/10/2012 at 12:32 PM
Hi All,

Even I was facing the same issue today.

I added a Fact Table as Dimension (Fact/Degenerate Dimension) which had nvarchar attributes. Once I created Cube Dimension from this table and tried to deploy the solution, it got corrupted and was showing error with some other dimension.

Steps to recover:
1. Deleted the new Cube Dimension with nvarchar attributes.
2. Tried to deploy the whole solution. (Didnt work). Showed the error
Error 6 Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data\AMS Analysis Services 2008.0.db\DIMENSION_TABLE.19.dim.xml'. 0 0

3. Tried to process only the dimension for which it showed the error (DIMENSION_TABLE). (It will show errors, you can ignore and proceed to process the dimension).

4. Tried to process the whole solution. (Worked Fine).

Summary:
Try to process only the dimension separately which throws error by ignoring the deployment errors and then process the whole solution.

Thanks,
Swapnil
Posted by Martin_Ar on 5/5/2011 at 5:21 AM
If working in an "online-mode" SSAS project I don't know if it is possible solve this problem by editing XML files.

What I did was to delete the problematic attribute from all dimensions where it was used in any way, re-process the dimensions (went fine now), and then add the attribute to the dimensions again and re-process. After doing this the problem with "The size specified for a binding was too small..." was gone. Hope this helps.
Posted by Darren Gosbell on 10/7/2010 at 1:02 PM
Use the BIDSHelper Dimension Data Type Discrepancy Check feature to align the data types in your dimension attributes with those in the DSV.

http://bidshelper.codeplex.com/wikipage?title=Dimension%20Data%20Type%20Discrepancy%20Check&referringTitle=Home
Posted by Pankaj.Shinde on 3/18/2009 at 11:34 PM
Step 1: Go to Solution Explorer.
Step 2: Right Click on <file name>.dsv file and open with "view code".
Step 3: Find the field name in which you are getting the error.(Here "FieldName" is the field name)
    E.g. <xs:element name=" FieldName" msdata:ReadOnly="true" msprop:FriendlyName=" FieldName" msprop:DbColumnName=" FieldName" msprop:design-time-name="67f8bc5c-30b9-4051-8b0e-72f5a2ae3b9f" minOccurs="0">
                    <xs:simpleType>
                     <xs:restriction base="xs:string">
                        <xs:maxLength value="1" />
                     </xs:restriction>
                    </xs:simpleType>
                 </xs:element>
Step 4: Change the xs:maxLength value="100" as per your requirement.
Step 5: Save the change carefully.
Step 6: Check the error has come in dim process or in measures.
Step 7: If it is in dim file.
Step 8: Go to Solution Explorer.
Step 9: Right Click on <Dim file name>.dim file and open with "view code".
Step 10: Find the field name in which you are getting the error.(Here "FieldName" is the field name)
    E.g. <Attribute dwd:design-time-name="40935210-43d7-4f73-9a88-90eba2406d3f">
     <ID>FieldName</ID>
     <Name>FieldName</Name>
     <EstimatedCount>8</EstimatedCount>
     <KeyColumns>
        <KeyColumn dwd:design-time-name="d53acec9-22f6-487b-a875-048269f5d850">
         <DataType>WChar</DataType>
         <DataSize>1</DataSize>
         <Source xsi:type="ColumnBinding" dwd:design-time-name="270662c5-fe14-42f9-8562-277530959428">
            <TableID>Table_1</TableID>
            <ColumnID>FieldName</ColumnID>
         </Source>
        </KeyColumn>
     </KeyColumns>
     <OrderBy>Key</OrderBy>
     <InstanceSelection>DropDown</InstanceSelection>
    </Attribute>
Step 11: Change the <DataSize>100</DataSize> as per your requirement.
Step 12: Save the change carefully.
Step 13: From Step 6, Else It is for measures then.
Step 14: Go to Solution Explorer.
Step 15: Right Click on <Cube file name>.cube file and open with "view code".
Step 16: Find the field name in which you are getting the error.(Here FieldName is the field name)
Step 17: Change the <DataSize>100</DataSize> as per your requirement.
Step 18: Save the change carefully.
Step 19: Go to Solution Explorer.
Step 20: Right to the project and "Process" the cube.