MSDE and the 500/3000 rule

[Preston Gallwas]

Suppose we use 500 devices with MSDE. We're using 500 of our "events" already, too, since you cannot delete the "Discovered system" events....so its effectively 2500 events.

Whats the reason behind this?
Is it possible to migrate a SIM5 installation to a full sql enviornment? Is there a process in place for doing so? (we currently monitor 800 devices...whoops ;))

[Igor Karasik]

If you plan upgrade to SQL on same box - use:
http://support.microsoft.com/default.aspx?scid=kb;en-us;325023

[Preston Gallwas]

Thanks -- we have a seperate box dedicated for SQL - I'm hoping the added SIM instance won't adversely affect traffic. But getting the SQL processing off the box its on now would actually be beneficial.

Whats the 'rule of thumb' for Full-MSSQL?

[Igor Karasik]

Preston, see
"Moving HP Systems Insight Manager 5.0 to a New System"
http://h10018.www1.hp.com/wwsolutions/misc/hpsim-helpfiles/hpsim_5_migratingNewSystem.pdf

Or "Moving HP Systems Insight Manager 4.2 to a New System"
http://h10018.www1.hp.com/wwsolutions/misc/hpsim-helpfiles/hpsim_migratingNewSystem.pdf
if you still use 4.2 version

[Preston Gallwas]

Thanks Igor. This guide says its for migrating to a new CMS -- we still want the APP on the server it is on, but the database elsewhere, while maintaining the links. Is this possible? It wasnt really clear from that document (at least to me)

[Igor Karasik]

You case seems to be simpler than described in the guide.
You need to Export your MSDE database to remote SQL server (according instructions in the guide) and change ODBC Data source name in start -> settings -> control panel
-> administrative tools -> data sources -> system DSN
I think it will work fine.
Regards, Igor

[Preston Gallwas]

Great, thanks!

[Preston Gallwas]

We've changed the ODBC sources but it still seems to be trying to connect to the local SQL instance, as SIM wont load when we stop the local SQL service.

[Preston Gallwas]

I believe we resolved this issue by editing database.props and database.admin in /config