Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Lumbago
Norsk Yak Master
3271 Posts |
 Posted - 2006-06-29 : 04:13:42
|
| As I have stated in several other posts recently my company has a set of reporting databases (datawarehouse and other "normal" databases) that is recreated completely on a daily basis using DTS (soon moving to BULK INSERT). These databases are *only* used for reporting and there are no updates or inserts whatsoever exept for the daily rebuild. What I'm thinking is if we would see any significant performance gains setting these databases to READ_ONLY and if there are any implications I should think of in doing so? Will there be any changes in user permissions or anything else that I need to consider?--Lumbago"Real programmers don't document, if it was hard to write it should be hard to understand" |
|
|
DHeath66
Starting Member
5 Posts |
Posted - 2006-06-29 : 10:03:13
|
| I dont think you would see a performance gain simply becasue you change the rights to READ-ONLY especially when this particular db is not being hit anyways. It would be differnt IF it was having a lot of transactions ran on here that would cause fragmentation and the likes. Also if\when you do change to READ-ONLY the effects you may want to consider are to the accounts that will do the bulk inserts or to anyothers that will make changes and since none are making changes it appears to me that you are in the clear. Just my .02DHEATH |
 |
|
|
|
|
|
READ_ONLY database questions