Hi All,
I'm working with VSM 9.1.5 on SQL2010 - web and DB on separate virtual servers, Windows Server 2008 R2 Enterprise.
I've recently unleashed quite a lot of the SAM Fed CMDB connector capabilities, and I've ended up with rather a large CMDB....! These are all necessary items - its not just any old CI 'bloat'.
For the 4 AM-PM domains currently active (4 more planned), VSM is scanning 220,000 items from SAM (Smarts) on a hourly basis.
Of the scanned items, approx 120,000 are being imported into the CMDB as CIs. VSM is also automatically managing about 200,000 links between these items.
This is definitely one of the biggest fully functional CMDBs I have heard of. Its certainly the biggest I have ever seen, or been involved with.
Does anyone have any info on what the upper limit on CMDB scalability in VSM might be? Am I worrying about nothing?
At the moment the DB is (just) 25GB in size. The servers aren't really breaking a sweat.
If anyone has advice on how this is likely to grow, or any gotchas I should watch out for, I'd be grateful...
Many thanks,
Holly.