Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a database that is read-only in nature. So it seems to make sense to boost performance by setting it to readonly. Then I get updates for this database once a month. At that point I would like to switch to readwrite, do the updates, and switch back to readonly. I’ve looked around and haven’t seen too much mention of this. Are there any problems I’m going to run into with this approach or is this as safe and basic as you get?
thanks
No problems with this approach.
Remember to rebuild index and update stats before making it read only again.
Then again, keep it simple and read write always…?