SSAS Deployment Error

Question

SSAS Deployment Error

cboneill181

Ten Centuries

Points: 1383
More actions
July 23, 2016 at 9:48 pm

#147663

I am trying to deploy an SSAS project running in tabular mode and am getting the following error:
Error returned: 'The table 'Date' has two columns with the IsKey property set to True.
So, it seems obvious, however, I can't find this 'IsKey' property anywhere, I've been trying to look it up for a while now and am not finding any documentation anywhere on it either.
Any help pointing me in the right direction would be appreciated.

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

cboneill181 Ten Centuries Points: 1383 More actions · Answer 1

So, I changed the name of the database I am deploying to and it's deploying fine now. Any idea why I am getting that error when trying to overwrite the database that originally existed?

Eirikur Eiriksson SSC Guru Points: 182916 More actions · Answer 2

cboneill181 (7/23/2016)
So, I changed the name of the database I am deploying to and it's deploying fine now. Any idea why I am getting that error when trying to overwrite the database that originally existed?

The isKey would be defined in the data model, look at the column properties.

😎

cboneill181 Ten Centuries Points: 1383 More actions · Answer 3

Thanks for the reply. I don't see that property anywhere. When I look at the column properties there is no 'IsKey' property. Can you provide a little more detail exactly where to find this property?

I'm currently in diagram view and I select a column from this table, F4 for properties and there is no IsKey property. Should I be looking somewhere else? I also looked in the table properties and don't see where a column may be set as the key there either.

AaronLS SSC Enthusiast Points: 119 More actions · Answer 4

Right click in VS and choose View Code, which will open the xml definition. Then you can use Find to find the reference. Do this for the DSV, Dimensions, and Cube, since they all have a XML definition.

Also sometimes deploy errors are really processing errors after deploy. Connect with SSMS and perform a process. You will sometimes actually get a more detailed error that way that will reveal the actual issue.

cboneill181 Ten Centuries Points: 1383 More actions · Answer 5

cboneill181

Ten Centuries

Points: 1383

July 28, 2016 at 5:57 pm

#1892561

Thanks for the tip, I'll check that out.

grant-665832 Valued Member Points: 70 More actions · Answer 6

Hi, I just ran into this problem. My first time with tabular. The solution as dboneill181 says is simply to drop the destination SSAS cube database and then redeploy. Works fine. This is a well known problem with many versions of SSAS multi-dimensional where some corruption occurs in the project files which apparently cause this problem. I've encountered it many, many times throughout the years. It is transient and I don't expect Microsoft to admit it or fix it (unless some other fix by accident remedies it).

li_310 SSC Enthusiast Points: 108 More actions · Answer 7

grant-665832 - Monday, December 5, 2016 12:30 PM
Hi, I just ran into this problem. My first time with tabular. The solution as dboneill181 says is simply to drop the destination SSAS cube database and then redeploy. Works fine. This is a well known problem with many versions of SSAS multi-dimensional where some corruption occurs in the project files which apparently cause this problem. I've encountered it many, many times throughout the years. It is transient and I don't expect Microsoft to admit it or fix it (unless some other fix by accident remedies it).

The error will be gone after delete
"isKey": true,
in the column list from Code View of the model.

MMartin1 One Orange Chip Points: 27799 More actions · Answer 8

The place where I know the dimension key(s) are defined is when creating the dimension through the wizard. I choose 'use an existing table' and select the date dimension from the DSV. The next dialogue screen defines the key columns for you, and based on what if any key is already defined in the base table. Maybe you added an extra field there to be part of the key even though it does not coincide with how the base table defines its key?

You may find it quicker and better to drop the dimension and start fresh.

----------------------------------------------------

srinivasulu.choudary Newbie Points: 7 More actions · Answer 9

Date Dimension of date attribute name should be given the different name instead of Date because Data Type as Date . naming conflict( Key word )
Step1; Key Columns in Date Dimension .let says Invoice Date and this column datatype is Date.if Invoice date names as Date and Data Type is date. both are conflict.