This article discusses creating read-only databases to improve performance throughput. This can be especially handy in a web environment where many users want to view information.
Cool! Didn't know that marking database read-only gets me some performance gains.
What if I make just one filegroup read only? Would that give me the same benefit for the tables, residing in that filegroup? In other words, can SQL Server disable locking on just a single file group? I am guessing it should be able to... However, how would it then handle a scenario where a table resides in a readonly filegroup, but one of its indexes is in readwrite filegroup? Would it still try to place latches on the index pages, even though the table and hence the index can't change?
"if you go one step farther and actually make the database files read-only you can back up the database without shutting SQL Server down while the files are in use"
I tried to copy the files while they are in use. I got this message Cannot Copy <DB>: It is being used by another person or program.
I guess we can expect a production database to be pretty busy.
Article: SQL Server and Read-Only Databases
Posted - 07/03/2000 : 10:32:09
