In database operations, additional database read-only behavior tends to occur, resulting in loss of other operations on the database. How to solve it? Here are one by one of the way.
Wordy words will not say more, straight into the subject bar!
Programme one:
In this case, the SA account is typically used to log on, as long as Windows authentication is changed, and the database is attached.
Scenario Two:
Use the sa login SQL Server2008 to attach the database, append the database as read-only,
Then click the database--"Properties"--"options"--"state", found "database read-only" This is true, changed to False, if you can modify,
So congratulations, your character is good! I made the same mistake when I modified it:
In this case, locate your data file and log file, right-click on "Properties"--"safe",
Add a "Network Service" account, and then give the account full control of the permissions.
Use sa login again, attach the database, hehe ... You will find that life is so beautiful!!!