I just downloaded the NCM 7.0 upgrade and tried to run it to install NCM 7.0 in standalone mode following the instructions in the Quick Start Guide. But the Config Wizard prompted for my existing NPM dabatase and I don't want to integrate NCM and NPM. I have the NCM and NPM databases on the same MS SQL server. And the Guide isn't much help. So how can I install NCM on its own server without NPM integration with its database on a separate MS SQL server?
Hi mkomeara, Yes you can do this as long as NCM and NPM are installed on different servers. In fact you can use the same MS SQL Server you just need to create a new database for the Orion Core instead of choosing the existing NPM database. At that point your NCM will not integrate with your existing NPM.
Hope this helps!
Since the QuickStart Guide seems to have led you astray we would appreciate knowing at what step(s) you were confused and, based on the help you received from support, what additional information would have helped you get the upgrade done without a hitch.
There are others out there with an implementation like yours and we would like to help them avoid the snag you hit.
I have a similar problem. I only have NCM and Engineer Toolkit. When I tried to update NCM to version 7.0, it tried to create another table in SQL Server but I was not logged in with an SA account; therefore the install failed. Now NCM is completely dead - I can't even bring the program up. I've called support three times, waited through 30 minute wait queues trying to find out what table is being created and how much space it will need on the SQL Server. I need to provide this information to our DBA before I will be allowed to use an SA account to create a new table.
I am not trying to integrate NCM with anything else and this is a standalone server.
Does anyone know what table it is trying to create and how much space it needs?
As an update; Support answered with the following:
The following new tables have been added in NCM 7.0:
ApproveQueue – size depends from number of waiting Config change approval requests as well as size of script which needs to be approved. In most cases size is small
ApproveQueueNodes - size depends from number of waiting Config change approval requests as well as size of script which needs to be approved. In most cases size is small.
UserLevelLoginCredentials – size is small