I have the same issue. I have capped the log file to 30GB so we can run the Netflow service until we hit the log file limit. Typically this gives us 30-45 mins. I have a case open and am awaiting help. Let me know if you find out anything and I will do the same.
This KB from microsoft should help you.
"How to stop the transaction log of a SQL Server database from growing unexpectedly" - http://support.microsoft.com/kb/873235.
We have started having this problem this week. Netflow is eating up 30GB of log files in less than 30 mins. This causes Orion to no longer be able to connect to the DB at all. Ihave to have my SQL admins go in and clear up the log and then the DB has to run a repair on itself. I have cut my Netflow dvices back as far as I can right now to 61 interfaces, but I have decent hardware. Dedicated SQL server. 3.0 Ghz processor with 12GB RAM on front end. I have had my SQL developer read the above KB article and his feedback is:
# Back up the transaction log files regularly to delete the inactive transactions in your transaction log.
- We would have to do this every 5 minutes
# Design the transactions to be small.
- Dependent on the application (Orion)
# Make sure that no uncommitted transactions continue to run for an indefinite time.
- Dependent on the applicaiton (Orion)
# Schedule the Update Statistics option to occur daily.
- Doesn't matter as the log fills in 30 mins.
I have sent some of my data to support. I seem to be spending more time babysitting this app lately.
I too am haaving the same problem... Netflow is useless at the moment because of it...
Solarwinds, is there a patch or fix for this issue yet?
We are aware of this issue and are actively working it. No update to share as of now.
any update on a fix for this?
did you get a resolution to your problem yet? I am having the same issue and have had no luck getting it resolved.
Has there been any resolution to this matter. We are having the same problem.
Is there any current solution to this. We have this issue as well. My log file is growing out of control and we just had a 4 hour outage on both npm and nta as a result. We are currently running nmp 10 and NTA 3.6
We have netflow on 24 devices and about 3 interfaces per device.
Log file grows is mostly caused by a very long transaction. You can determine culprit of it, open SQL management studio and run command.
DBCC OPENTRAN
If there is some transaction for a very log time, you can see log file grows very rapid. After you have it, you can post it here and we can do some tuning.
Also log file grows behavior depends on your [recovery model], do you use recommended simple mode?
We did have it set to simple but in order to try and keep the system running we have changed it to Full and are running tlog backups every 15 min just to keep the log file empty. We have also capped the log at 100g to prevent the corruption issue we had.
I will look for long open transactions.
No open transactions for more than a few seconds that I have seen so far.
