Sometimes - especially when a large site update is required MCMS customers decide to use database copy rather than using Site Deployment to move the changes to the production machine. That is a valid way to do this but some things need to be considered when doing this step:
- Users assigned to rights groups might need to be adjusted after you moved the database
It is a common scenario that users on a production server server are different than in the authoring environment. After copying the database these users need to be adjusted again
- All items in the database have to be approved
That is a very important step! If you miss this then site deployment will not work correct in the future when the non-approved items should be adjusted. Actually items which are not in approved state on the destination server will not get replaced with the content in the SDO file!