I've read that DBCC REINDEX is an offline operation, because while the REINDEX is in progress, the underlying table is locked.
I would like to set up a DBCC REINDEX script to run at off-peak times. I would like to have the application still available to users while this is running. (I know that performance will be hampered, but that's acceptable as a very small number of users (if any) will be using the system during this period). I would like to make this an automated job, and don't want to have to log in to manually kill the application services before running the script.
Do I risk corrupting the database if I run this while the database is online? Or is it just recommended to be run offline because the table of the index being updated is locked?