We have a server “Program” document to run the Compact task on all databases with more than 20% whitespace (“-S20”) on the server each morning at 3AM.
However, there is one database that we would like to exclude from that Program, since it is 13GB and is compacted each Sunday instead.
I know that you can explicitly specify the folder on which Compact should run, but can you specify multiple folders? The database I wish to exclude resides in its own folder, so that would be ideal. However, I don’t want to have to create multiple Program documents just to cover all of the other folders.
Ideally, I would love to have an additional field on the Program document that allows you to define the database(s)/folder(s) that is excluded from the program.
Does anyone have any suggestions?
Cheers!
T.
Subject: Solution found - COMPACT_FILTER
I know it has been quite a while since posting this question, but I thought I’d post this info for anyone conducting a search for a similar solution.
Check out the “COMPACT_FILTER” NOTES.INI parameter - it may just help you accomplish this…
http://www.lntoolbox.com/en/notesini-reference/bycategory/3415-compact_filter.html
Hope it helps someone else!
Subject: Compact Task and DB Exclusion
Did you find a solution for this?
We have the same need. Our servers contains some huge db, that need to be compacted only once a month.
Subject: I don’t believe you can exclude a db from compact
Which is unfortunate as compacting all dbs in an folder except for ones specified would be nice.
Subject: You can use an IND file.
You can create a text file (.ind extension) detailing all the databases minus the one you don’t want.
Then use the compact with an IND file. See this link.
http://tinyurl.com/o9gds2
Subject: I was hoping to avoid…
I had hoped to avoid the use of IND files (but thanks for the response Simon!).
The databases are changing all the time (there are ALOT of them!), and I only want to exclude 1 or 2 databases on the whole server.
I know I could probably create an agent to automatically update the IND file contents (excluding the aforementioned databases at the same time), but a native solution would be so much more easy to implement.
Cheers,
T.