cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

Merge NCM and NPM Databases

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.

19 Comments
Level 18

Basically, I agree with everything you said. We are aware of the fact that this change might affect NPM and we would do our best to mitigate the consequences. It's early to expose all the ideas, but believe me that we plan to deploy measures to protect NPM performance.

Level 10

I have to think that the performance hit is substantial.  SQL has its limitations - not sure where they will be met for each of our respective environments and I am by no means a DBA guru.  But time and time again, with multiple products for monitoring they all bog down as you grow and how we manage our methodologies for monitoring.  In my experience I have found it is not hard to bring the best monitoring systems to its knees.  ORION was chosen here in my environment because I had chosen to push it as I have worked with multiple products and this product seems to work very well, very intuitive, and performance was scalable and decent. 

Merging these databases into one...hmmmm....I think I am leaning more toward the side of keeping it separate for each module like dclick mentioned.  I think it makes it more scalable as well as provides better options available to deal with performance issues should you run into them.  If you house your DB's on a single instance server that is fine, but leave that capability to scale out away from that box to another SQL instance if need be due to I/O issues.  But I think we need to have the ability to auto sync within the system so we don't have to keep multiple instances/db synced so it all works well together.  Is this possible even?  If you are a small shop then you can still put it on the same box (single SQL instance but multiple db's).  There needs to be some type of migration path that is fairly straight forward so that a small business can grow into the bigger solution without growing pains.

The syncing issue now is a little thorn in the side between NCM and NPM - I have run into issues where nodes are in one and not the other, etc.  However I want my application for all my business partners to run smoothly with good performance.  I do not want to be responding and spending my time on performance tuning, fixing, issues within my EMS Environment on a regular day to day basis.  That would be very problematic and hinder adoption of monitoring solutions to solve issues and lead our organization into a pro-active type of organization rather than a re-active one.  I also want the ability to collect as much as possible as often as possible so that root cause issues can be drilled down to exactly what happened.  I know that is easier said than done...it is something that I think we all strive toward and I understand it isn't a perfect world so sacrifices are made.  Bigger window for poll times, possibly less metrics collected, or shorter time spans on keeping data before rolled up...etc, etc, etc.

I think the common theme though is "Performance".  You have a daunting task to keep us all happy...   I think I will vote Nay on the merge.  I vote Yes on some type of syncing that we can count on and keeping performance a top factor.  The systems do us no good when they crawl.

Respectfully,

NetEng33

Level 14

I agree with the idea of having a "Core" database and then also having seperate databases for each of the modules.  I don't mind NPM being the core database.  I would like to see NCM, NTA, SAM, VNQM, etc.  There is a lot in these databases that can be stored in the Core database and referenced there.  I do a lot of custom content and need to perform tasks in the databases for this content.  It would be nice to have a Core database, so that I do not have to update multiple tables across multiple databases to change the same data.

Level 14

Another suggestion...A vote against button!

Level 18

You have the possibility to vote against features -- the down arrow.

Level 18

Hi NetEng33,

We totally understand your concerns -- they are similar to other users.

A substantial part of the merge would also be performance optimization and testing.

I believe that we can find a way that will work for everyone.

Regards,

Jiri

Level 18

Implemented in NCM 7.3.

Jiri

Community Manager
Community Manager
Status changed to: Implemented
 
Community Manager
Community Manager
Status changed to: Implemented