Implemented

Merge NCM and NPM Databases

NCM now uses two databases to store its data -- NPM/Core db and NCM db. The suggestion is to store all NCM data in the NPM/Core database. The expected benefit is simpler db management; issues connected with node synchronization should disappear.

Please provide your comments.

Parents
  • I'm not 100% sure I agree with this.  I definitely see the management benefits and value to consolidated data, but I also see possible performance issues.  NPM 10.4 (not sure about 10.5 yet, I just installed it) already has an issue with fragmentation due to the amount of indexes it creates and deletes.  Additionally, while this poll is all about NPM/NCM, if I consider all the Orion product "modules" and the integrations, I feel a more "Federated" database makes more sense to me.  Keep NPM and NCM data separate, split out NTA (which I believe is coming), split out VNQM, IPAM, and SAM, and create a "Core" DB that contains all the common data elements.  Every element already has an ID number, that is the hook the web page can use to display data.

    I know, I know, this would mean a total rewrite of the application, but look at the long term value to integrating all the new stuff you've purchased, like Storage Manager ("Profiler"), LEM ("TriGeo"), and Virtualization Manager ("Hyper9"), etc.  You simply point those products to the "Core" DB and it populates the devices.

    Just my 2 cents.

    D

Comment
  • I'm not 100% sure I agree with this.  I definitely see the management benefits and value to consolidated data, but I also see possible performance issues.  NPM 10.4 (not sure about 10.5 yet, I just installed it) already has an issue with fragmentation due to the amount of indexes it creates and deletes.  Additionally, while this poll is all about NPM/NCM, if I consider all the Orion product "modules" and the integrations, I feel a more "Federated" database makes more sense to me.  Keep NPM and NCM data separate, split out NTA (which I believe is coming), split out VNQM, IPAM, and SAM, and create a "Core" DB that contains all the common data elements.  Every element already has an ID number, that is the hook the web page can use to display data.

    I know, I know, this would mean a total rewrite of the application, but look at the long term value to integrating all the new stuff you've purchased, like Storage Manager ("Profiler"), LEM ("TriGeo"), and Virtualization Manager ("Hyper9"), etc.  You simply point those products to the "Core" DB and it populates the devices.

    Just my 2 cents.

    D

Children
No Data