Compact -S 10 -b changes DBIID?

I have notice this situation with compacts on our servers

I use a compact -S 10 -b program document on all my servers but has soon haqs tha compact does find a database that needs to be compacted

the DBIID gets changed even with the -b switch

Does the usage of the -S10 switch would cause the DBIID change ?

See example below

02/18/2011 06:01:07 PM Compacting AgentRunner.nsf (Java AgentRunner), -S10 -b

02/18/2011 06:01:07 PM Recovery Manager: Assigning new DBIID for F:\Notes\data\AgentRunner.nsf (need new backup for media recovery).

02/18/2011 06:01:08 PM Compacted AgentRunner.nsf, 192K bytes recovered (33%)

02/18/2011 06:01:09 PM Compacting Belair\DiagnosticHabitationON.nsf (Property Diagnostics Ontario), -S10 -b

Subject: switch

the -S10 switch simply directs the compact task to only select databases with 10% or more of white space, the compaction will still cause the DBIID to change, meaning you may need to back up the database again. We tie up our compaction schedule with our backup schedule for this very reason.

Subject: -b (does not change DBIID)

-b is the only switch that will not change the DBIID of a database if transactional logging is enabled.