Our front end application uses\ pointed to a different database now in SQL Server 2008R2 in the same instance, so to prevent users from accidentally updating data in the old production database, is it simply just changing the Database Read Only State to "True"? As
ADMIN users may still need to access it in case, to verify migrated data to the new DB matches the Old DB but not be able to modify anything.
Also, is it a good idea to change the recovery model for this old production database to
Full? and no need to run its Jobs or maintenance plans ?
In worse cases, I always can set it back to Read and Write at anytime with no issues correct? Thanks for any advice.