Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

database maintenance in version 3.1

I'm a little confused by the changes in v 3.1 regarding database maintenance. In the Global Settings, you choose the time intervals to keep both uncompressed and compressed data. That much is like previous versions.

Now you also have Database Maintenance Settings. How do the two work together? For instance, if I elect to keep uncompressed data for 1 hour and compressed data for 30 days, and i also set the "compress databae and log files frequency" to once every ten days, what exactly is going to be happening?

I guess i don't understand how the settings chosen on the "Global Settings" screen work in conjunction with the settings on the "Database Maintenance Settings" page.

Can anyone give me an explanation based on some hypothetical settings on both screens?

I would really appreciate it.

Oh, one more thing. Are the NetFlow data handling settings treated independently from the database maintenance setting in Orion NPM? Or, is there some netflow data summarization performed by Orion.

Find more posts tagged with

Accepted answers

All comments

davidmaltby

You know, now that I think about the wording of both of those, I see the confusion. So, to explain, the uncompressed and compressed settings are the same as they were in NTA 3.0. They have to do with the flow data itself. The Maintenance setting indicates how often to perform a shrink on the SQL Server's database and transaction log files. In Server SQL, those files can automatically grow as new database data and transactions in the database are made, but those files never get shrinked by the SQL Server. It is left up to the database administrator or the application using the database to instruct SQL Server to shrink those files.

Further the NetFlow database maintenance is completely independent of the Orion maintenance.

Hope this helps,

David Maltby

freemen

Thanks David. That's what I was after. A couple more questions if you don't mind.

Under Global Settings, raw, uncompressed data is kept for the designated time, then it is compressed and kept for that designated time? Is that right? After that, it becomes "expired flow data"?

If not, then what exactly is "expired flow data"? What is the function of the "IPs to process at a time" setting?

Thanks.

freemen

David?

davidmaltby

Yes. The uncompressed data is kept that way for 1 hour by default. Then it is compressed and stays in the database until it is deleted. Which is by default 30 days.

The "IPs to process at a time" is for the nightly maintenance. It controls the number of IPs that are cleaned up in one transaction to the SQL Server. Some customer databases have restrictions on how large their transaction log can grow, so they may need to make this number smaller. It was questionable as to whether we should have exposed this setting to the customer. You typically shouldn't need to adjust it.

Thanks,

David

freemen

What do you mean by IPs that are cleaned up? What exactly is happening? Sorry to be so dense.