SQL database requirments

[Timothy Schaffer]

Are there any requirments for using an external SQL database instead of MSDE?

[Jadrice Toussaint]

IF you're running SIM on windows, you can either use Microsoft SQL 2000 standard or enterprise edition. If you're running SIM on Linux or HPUX, you can postgres.

[Enes Dizdarevic]

If you want to use external SQL, you have to install MDAC 2.7 (SQL client) on your HPSIM server before you install HPSIM.

[Rob Buxton]

Just that SQL Server be at SP3 or later.

It's a fairly easy install to use an external database.

[Timothy Schaffer]

No table space requirments or anything to that effect?

thx,
Tim

[Jadrice Toussaint]

No, SIM will take care of the database creation and such.

[Meier Daniel]

Jadrice

Is there a special maintenance job to plan for the insight database. Cause our Insight_v1_0Log File is blowing up to 11 Gigs with 20 Systems that we manage. Yesterday then i shrinked the log file to 1 Gig and this morning its already growed to 2 Gigs.

[James Kennedy_4]

I'm having an awfull time with the SQL Log files. They're growing to insane amounts of disk space. What's the command to truncate the SQL logs??

[Meier Daniel]

James

Searched a long time and found this KB on microsoft.com

KB272318
Shrinking the Transaction Log in SQL Server 2000 with DBCC......

After i have done this the database was shrinked to 2 Gigs, but this morning its again 4 Gigs and i manage only 21 Systems. At the moment i'm not very happy with the new HP Systems Manager, this never happens with the OLD CIM 7.2

[Jadrice Toussaint]

Guys -

Limit the amount of memory the SQL server is using to about 250 megs. There is a documentation on this but can't find it right now. Open up the SQl server enterprise manager and right click on the servername then select properties. click the memory tab and adjust the maximum memory to 250 megs. That should solve your log issues. My current log right ow is at 32 megs

[James Kennedy_4]

Jadrice
Good suggestion, however my SQL server is home to several high end databases so limiting the memory for SQL Server is definately not an option.

I just can't figure out what the heck is going on inside SIM that is generating SO much logging.

I setup a SQL backup job to purge the logs every day. This seems to help a lot. It brought my 4 GB log down to about 100 MB.

[Jadrice Toussaint]

Gotcha. Well the only thing I can suggest, is to run SIM on a different database server with that memory limit. This works for me. Although I must admit that when I do move this into production, I will definitely make sure that a dedicated SQL server is available for that kind of modification.

[Stanley Yau]

Does anyone have an update on this issue?

I've got Systems Insight Manager installed on one of our boxes (managing only 3 servers), and over the period of a week, it managed to log just over 7GB of logfiles...

This is, quite frankly, ridiculous.

No idea what's causing it. We have an almost duplicate setup for another office, and the Insight log there is only running to a few hundred meg...

If anyone has any idea what's happening, I'd appreciate hearing it... Thanks!

[James Kennedy_4]

This really is driving me insane too. My production database server just crapped out again. Log files were about 8 GB. When the log is full it starts filling up the SQL error log until there's no disk space left. Also you can't truncate the log when there's no space left on the drive. I'm not really sure what to do anymore. I think i'm going to setup a SQL job that truncates the log every few hours. It's something that shouldn't have to be done though.