Question on where the MDX is deployed to by BIDS Helper

Hi, all experts here,

As we are enabled to deploy the calculation MDX scripts by installing BIDS Helper. But why there is no options for us to decide where the MDX scripts will be deployed to? And where can I find those deployed MDX scripts? Thanks a lot in advance and I am confused and I am looking forward to hearing from you shortly for your help. (Assume I am right, to my understanding, with capability to deploy the calculated MDX scripts we are then able to reuse them?)

With best regards,

Yours sincerely,

Helen999888 wrote:

But why there is no options for us to decide where the MDX scripts will be deployed to?

Because It is deployed to the server and database that is specified in the deployment settings of your project. Which should be the same server that the cube was deployed to in the first place.

Helen999888 wrote:

And where can I find those deployed MDX scripts?

The MDX script is the calculation script that you find in the calculations tab of the cube designer. The deploy calculations feature pushes changes from your client machine up onto the server.

Helen999888 wrote:

(Assume I am right, to my understanding, with capability to deploy the calculated MDX scripts we are then able to reuse them?)

No, the MDX calculations are not persisted anywhere, the xmla alter commands are sent directly to the target server specified in the deployment settings for your project. The xmla command is targeted at a specific DatabaseID and CubeID and usually the calculations would be fairly specific to the structure of the cube.

The main advantage to using the deploy MDX script feature is that it is very quick if you know that all you have done is to make a change to the MDX script.

|||

Hi, Darren,

Thanks very much for your kind advices.

As you advised, all the point of using this feature is to quickly deploy changes of calculations to the analysis services database for the specific cube? Thanks a lot.

With best regards,

Yours sincerely,

question on upper bound primary key of type int

I have several tables in a deployed database in which the primary key is of type int, and autoincrements by 1 each time a record is added. My question is, since ints are 32-bit, what happens when its value reaches 4,294,967,296? I know that seems like an extrememly large amount of records, but when we imported the data into the database it started at key value 1,000,000. I don't know how to make it use lower numbers which are currently not being used (numbers below 1,000,000), and I am worried I will have problems when I reach the upper bound. What kind of problems could this cause? Should I change the primary key's type?

Thanks!

the upper bound is somewhere around 2.1 bill. Yes when you reach that limit your application will fail. You cannot insert any new data. You could put some alert in place to identify or predict when the storm is coming. you could create a job that gets the MAX(ID) every week and you can monitor the growth of the table. Once the ID reaches closer to 2 bil you can increase your frequency of monitoring. To fix it, you need modify the column and change it to BigInt. Please do not even bother to try ALTER TABLE...ALTER COLUMN...the server will hang.|||Ok, I'll just modify the primary key type. Thanks for the response.sql