Deployment to one Database 'Clearing' Another...

Hi,

We have a setup whereby our production server builds to a build cube overnight, and if and when this completes successfully, and passes sanity checks, it automatically backs up and restores the cube over the top of a 'live cube'.

This seemed like a fair enough plan - it allows developers to deploy to the production server without breaking the production-live cube, however, we have noticed that deploying to the build cube database sometimes results in the clearing out of the production cube database (much to the users' dismay!).

Anyone else seen anything similar, or have any ideas as to what the problem could be?

Thanks,

Will.

First time I hear about something like that.

Try and see if you can use Synchronization functionality to deploy your changes from test to production. This is more straightforward then backup-copy-restore.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi Edward,

Thanks for your reply.

We currently build the cube on the production server (and 'deploy' the live cube to a databae on the same server) - we're of the view that synchronization is not possible with two databases on the same server. Is this correct?

Regards,

Will.

|||

You are right. You cannot synch from one database to another on the same server instance.

What I suggest in your case is to install another instance of Analysis Server on the same server machine. This case you achive better separation between test and production. If something wrong goes with the test instance, you can easily restart it or, it would be easier to monitor usage of the production server instance without developers interfere. Then, also you'd be able to use synch. Overall in your case second instance might be cleaner solution.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.