SQL newbie so I'm not sure if this is the right group for these
questions (but it does involve BCM). Currently I run a script every
morning (12:30 am) shutting down the (SQL) service, backing up the .mdf
file to a file server and starting up the service again. When I
remember to do it, I run the back option in Outlook. (Business Tools |
Manage Database, click on Back up Database).

So my questions are:

* What is the difference between the .msbcm and .mdf files in BCM?

* .msbcm is smaller than .mdf, when backing up via Outlook who is
compressing it? Outlook/BCM or SQL?

* Is there any benefit to backing up via Outlook (creating the .msbcm
file)?

* Which is recommended and would allow easier restoring if the
situation calls for it, .msbcm or .mdf?

* Should I back up the .ldf file as well?


Using Outlook 2003 w/ BCM

..mdf files are SQL's raw database files, that it uses directly to store
your data while the database is running.

SQL can then create a backup of your database. BCM takes that file,
compresses it, and saves it as a .msbcm file.

Trade-offs:
It is probably easier to remount a database from an mdf file (doesn't
require Outlook/BCM), but an msbcm takes up less storage.

If you don't know what an ldf file is, you can safely ignore it.

Thanks Luther.

I'm going to just back up the .mdf file since space is not an issue
with the backups. As a test I took the backup copy and compressed it
and was amazed at the file reduction. 129MB .mdf file down to 14MB
WinRAR, 23MB WinZIP. I would of expected a size around 100MB with
either compress tool.

Interesting (to me anyway)

That sounds typical. If you don't fill every field in your database
with data (consider that the middle name field in BCM can hold 320
characters...), most of the space is going be empty and easy to
compress.