March 28, 2016 at 9:55 am
We are working on building cubes in SSAS using GreenPlum as a source. We are using an OLE DB driver created for GreenPlum to pull the data. We are able to create the data source model and model the dimensions with no issues but when we go to process the dimensions we get the following error (Errors in the back-end database access module. Column -1 is too large for this instance of SQL Server 2014 Analysis Services.) and we are not able to find any solution for that error message on Google. Has anyone run into this error before and found a way to fix it? Thanks.
March 29, 2016 at 5:46 am
sqlchuck4 (3/28/2016)
We are working on building cubes in SSAS using GreenPlum as a source. We are using an OLE DB driver created for GreenPlum to pull the data. We are able to create the data source model and model the dimensions with no issues but when we go to process the dimensions we get the following error (Errors in the back-end database access module. Column -1 is too large for this instance of SQL Server 2014 Analysis Services.) and we are not able to find any solution for that error message on Google. Has anyone run into this error before and found a way to fix it? Thanks.
A few questions.....
1. What is the data type/size of the source column?
2. How have you defined the data type/size in the data source view?
3. Are they different?
4. SSAS Tabular or Multi Dimensional? If the former, the column size limit is 131,072 characters for varchar(max). Why would you need a column this large in a cube if this is the issue?
If the latter, what is the value of the StringStoresCompatibilityLevel for the particular dimension?
March 29, 2016 at 12:43 pm
After looking at your response, I figured out that the issue is that for character fields where a case statement in the source view is used to calculate the field value, GreenPlum is not passing a character field size (i.e. varchar(30) where the the "30" is missing). Is it possible to set these values in the SSAS data source view without creating a named query? (using a named query creates syntax that is not compatible with GreenPlum) Thanks.
March 29, 2016 at 1:04 pm
sqlchuck4 (3/29/2016)
After looking at your response, I figured out that the issue is that for character fields where a case statement in the source view is used to calculate the field value, GreenPlum is not passing a character field size (i.e. varchar(30) where the the "30" is missing). Is it possible to set these values in the SSAS data source view without creating a named query? (using a named query creates syntax that is not compatible with GreenPlum) Thanks.
Well I don't know your exact setup, but I do know that SSAS doesn't always play nice with PostGres syntax - for example SSAS tends to use a lot of square brackets in the SQL it generates, which mean something different in PostGres. Can you not create a linked server and then use OPENQUERY? If not I would suggest that you make sure you have the appropriate up to date driver for what you are doing.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply