Ok - I'm still confused. If we enable transaction logging, it appears we would only want to compact databases with no options or with the -b option so that the database will retain it's DBIID. This does not, however, reduce the size of the database which a user and/or Admin may need to do if the user is over quota. Is there a way to compact a database to reduce the size but NOT change the DBIID?
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!