SQL.Log fills up in SIM 4.2 sp2

[RHagen_1]

after backing out a sim5 upgrade, I keep gettings this SQL.log file filling up (it got to over 2gb at one time). the actual SQL W2k sp4 server is remote on the same domain. and that SQL DB is showing entries or data coming into the tables...

Does anyone know how to either stop or have the file purge itself?

[Igor Karasik]

Ralph,
You can change the recovery model from full to simple
See also
http://support.microsoft.com/?kbid=873235

[RHagen_1]

This file is on the SIM server not the remote SQL server. the system was always set up for remote SQL server and not MSDE.. so this SQL.log file is now on the SIM server. does this fix still apply?

[Igor Karasik]

Does SQL.LOG file is log file for SQL database?

[RHagen_1]

I'm not sure... it's gathering info for or from all the different SIM services like PMP, wsd14.jar, pmptools, mxdomainmgr. It's on the SIM server. I set the remote SQL DB to 'simple', cleared the log file, set to overwrite bi-weekly, set log file to autoshrink and had it on our enterprise Netbackup daily backup but still keeps growing... and ideas??

[Mikael Rönnbäck]

Got a similar issue, if using local SQL database with database model = simple then database shrink works fine.
However if using remote SQL database instance with database model either full or simple, does not matter, then database logs will grow rather fast (due to my number of devices it grows with approx. 5 GB per hour up to 30 GB where it stops growing for a while).

Autoshrink for some reason does not work, so as a workaround I have had to schedule a job within SQL server that performs a shrink on the database daily

After shrink what remains is just 1 MB log.

[RHagen_1]

So SIM treats this SQL log file like transaction log... so a daily job to purge the remote DB will do the job? OK... I give it a try today...

[RHagen_1]

I think we're mixing up logs here...

On my remote SQL server all the items recommended here work fine...

My problem is with a 2nd SQL log file that SIM installed on SIM server. that is the file that is filling up... I'm not having any problems with the SQL log file on the SQL server. all my problems are with this SIM SQL log file (and why is it even there? Transaction logs to ship to the SQL server?). At first I thought it was performance data for SIM PM but after looking at the logs, it has all kinds of Data... How about it HP???... how do I keep this SIM server log file down to reasonable size.. I've already followed the SQL log suggestions for the SQL server's log files..