Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Deploy after changing data type Expand / Collapse
Author
Message
Posted Tuesday, February 5, 2013 7:15 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, February 22, 2013 1:41 AM
Points: 7, Visits: 91
Hallo
I needed to change surrogate keys data type from int to char: I updated the DSV and verified that dimensions properties report actual data type.
Now when I deploy the solution I get the "OLE DB was unable to convert a value to the data type requested for column..." error message.

I tried deleting the database but the deployment stops anyway.
Have you got any hint, please?
thanks in advance!
Post #1415823
Posted Tuesday, February 5, 2013 12:31 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, October 21, 2014 1:01 PM
Points: 43, Visits: 324
If the error says "OLEDB Error", more than likely the problem is in the data source. If you're using named query or view check if the query is working in SSMS.

Also, check data type of the error column in BIDS. Go to properties of the attribute, expand Key column, see data type is updated.

Is there a reason you're using Char for surrogate key? This could cause serious performance problems. Isn't INT data type solving your need?


~Sam.

http://svangasql.wordpress.com
Post #1416033
Posted Tuesday, February 5, 2013 4:02 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, October 8, 2014 9:50 AM
Points: 12, Visits: 89
Hallo Sam and thank you for you reply.
Actually query was working, data type in Key columns in BIDS were updated and everything else seemed to be fine. At the end I preferred removing and recreating the two dimensions.

Switching to CHAR hasn't be a good deal. Actually, I wanted to keep trace in the surrogate keys of the sources (the Customer dimension is fed by multiple sources and I horribly thought to prefix the INT with a CHAR denoting the source), but actually here is where the surrogate key comes in hand! So I did quite a little (a couple of hours) big mess, as of my first cube.

I'm gonna take the path of a durable super-natural key from this article of the Kimball Group Reader.



Post #1416140
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse