Jose Ianuck (3/9/2009)
Hi, all. We created a Database snapshot to work read only, just reports by web application, so what impact does a database snapshot have on application transaction throughput and performance?
DB snapshots are read-only and you cannot do any transactions as you mentioned with application transaction, and till you are planing to use it just for reports, you would create every 15-30 min snapshot ( it depends from number of transactions) and this procedure should happened dropping snapshot then creating again with same name ...so at this time if the user is viewing any data as reports with application, will lose conn or cannot view data properly or some other issue etc!
I prefer that you can create another DB and copying from your production server all the data to that DB, so this DB will better if you use it for reporting! This reporting DB can have the latest data every 20-30 min ( it depends from number of transactions) and no connection with production server to do something bad with performance!
P.S. Why do you want to use snapshot DB for reporting?
SELECT YOUR PROBLEM FROM SSC.com WHERE PROBLEM DESCRIPTION =http://www.sqlservercentral.com/articles/Best+Practices/61537/