When I regenerate the .mdc file for an existing cube model, and then access the cube in Analysis Studio, I do not see changes in model, only in the numbers themselves. That is, if my underlying data changes, it is reflected in the values of the measures, but if I change the transformer model, say by adding a new measure, it seems I do not see that new measure until the Cognos service is restarted. Is this expected behavior? Is there a way around it? I don't like bouncing the service during the day when users may be on-line, so I have been changing the mdc file name to be able to see model changes, but that also requires setting up a new datasource and package for each name change, so it gets a bit tedious.
-Jim
I would assume the structure of the cube is being cached in a runtime metadata file (rtm) on your server. As far as I'm aware, this will remain active as long as the connection pool is active.
MF.
Sent from my iPad using Tapatalk HD
I'm not clear which version of 8.x you are on, but I know at least with 8.4 if not earlier there are options on the cube properties for automated deployment. If you use those you should always see changes, though you may have to close an open Analysis Studio session and re-open it. Although I am now on 10.x I did this many times under 8.4 and the automated deploy worked great. Our Cognos server services were seldom restarted.
If the automated deployment is not working, you should open a support ticket.
Thanks for the tips. I'm not sure I'm doing a true "deployment", maybe that is my issue. I'm working with a contractor's setup, and the cube builds in one folder, and is copied to the "production" folder where the data source points it to. Cognos support gave me some hints about a more formal deployment too. Thanks.
jim
Re-publish the cube package