SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Deploy after changing data type


Deploy after changing data type

Author
Message
raffaelet
raffaelet
Forum Newbie
Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)

Group: General Forum Members
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!
Sam Vanga
Sam Vanga
SSC-Enthusiastic
SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)

Group: General Forum Members
Points: 148 Visits: 502
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 Vanga
http://SamuelVanga.com
lordzoster
lordzoster
SSC Rookie
SSC Rookie (45 reputation)SSC Rookie (45 reputation)SSC Rookie (45 reputation)SSC Rookie (45 reputation)SSC Rookie (45 reputation)SSC Rookie (45 reputation)SSC Rookie (45 reputation)SSC Rookie (45 reputation)

Group: General Forum Members
Points: 45 Visits: 102
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.



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search