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.
We can set our DataBase read-only, and it restricts some commands like Auto-Shrink, Auto Statistics, and DBCC commands. But it also gives a high performance with limiting that features.
We can use
ALTER DATABASE dbName SET READ_ONLY
command to set DB read only. But, why we should use Read Only Databases? What are the advantages, and what are the usage areas?
Thank you.
Some times you may have a database which is shared by a publisher – historical data, stock data, statistics, studies. Or potentially your own archived data.
It may or may not start as a SQL Server database, but the data is static.
You never want it to be altered by anyone at all, accidentally or intentionally.