HP SIM Sql Enterprise Database Sizing

[Robert Durenkamp]

Hello everyone,

We are going to install a HP CMS with around 500 managed W2003 HP servers. We are going to use a remote sql enterprise database on a cluster.

Can anyone tell me where I can find information on database sizing.

I can only seem to find use MSDE or Sql.

Any help will be greatly appreciated.

Robert

[Jason Hindson]

Robert,

I know this is an old post, but did you ever find an answer to this question? I'm currently looking at reinstalling my HP SIM server due to a server rebuild. I would like to begin using our SQL cluster instead of MSDE. I know the DBA's are going to be asking me about sizing requirements for the SIM database.

Thanks in advance.

Jason

[OlivierV]

For information, we have 484 devices in our CMS and the DB is 1.3 Gb, the log file is about 8 Gb (shrinked every night).

[David Claypool]

Rule of thumb, although your mileage may vary:

MSDE: up to 500 devices and 5 000 events
SQL2000: up to 5 000 devices and 50 000 events

[Darrin Rawls]

Database sizing depends on a number of factors - the most important is the number of events. For each event, SIM stores several aspects that equals about 3.8kb of space (do the math for the number of events you expect to have in the database). Add to that about 200 MB for every 500 devices (that's a rule of thumb, not exact).

For the database size, I would go into the DB properties, change the Recovery Model from "Full" (default) to "Simple" and set the Transaction Log to "Auto Shrink". YOu will probably have to stop/restart the SQL service to make this take affect. SIM doesn't do anything with the transaction log, so don't bother keeping this/backing it up/etc. I would also limit the Transaction file growth to no more than 1 GB or something...

Hope this helps.

[OlivierV]

Hi.

Setting the maximum size of the log file may cause problems. I had such settings but when the log file reached it's maximum size, the tasks were not running anymore and I wasn't able to add more devices. I removed this setting and created a scheduled task to shrink the log file, no more issue.

Regards.