Just wondering about the impact to the ePO SQL database when you add EEPC V6 to the mix.Beyond the added files that you register, what kind of additional size can the EEPC product add? Our ePO DB is already pretty large and growing. The DB admins will faint dead away if i tell them it's going to double in size with V6 added!
Bumping this for any updated info. Anyone?
Is there any documentation showing what EEPC does to the SQL database? Does it add any tables for its own use, or modify the DB in anyway?
What about info/events collected for EEPC? We're about to upgrade our DEV ePO in order to begin EEPC evaluation. When we go into production, our SQL group is going to ask us these types of questions. It's good to be prepared
of course it's going to get bigger - there's new information, but as to how much, I don't know.
what choices do they have though? If you want to use EEPC6 you're going to have to absorb the information, there's no way around it.
It does modify the ePO SQL DB. We're only running a couple eval systems so I can't answer the size question with any certainty. Having nothing else to work from we've told our DBAs to expect the DB to grow by the same amount as our current EE V5 DB occupies in the filesystem (without the slack). Just guessing, of course, but it seems like a reasonable high water mark for planning.
BTW, as soon as we turned on LDAP user sync in ePO for the V6 product our DBAs identified a need to add two indexes to optimize execution of a couple queries. Your mileage may vary.
Consider indexing ParentID and UserName in EPOLeafNodeUser table. All the usual cautions apply: SQL tuning is highly dependent on the unique factors of each enviroment so proceed only after extensive testing, yada, yada. Please share if you come up with numbers more accurate than my hack.
I guess you have answered one of my questions already. ie Does the addition of other products such as EEPC simply hook into the same EPO SQL database?
I was wondering if there was any possibility of creating separate SQL instances for ePO (AV), EEPC and DLP as a means of more creating more granular reporting and as a means of spreading the risk of DB corruption. Has anyone attempted this?