I have data-reader permissions on a production database. I need to write reporting queries. I have discovered a few reusable views will go a long way in standardizing my queries.
I have given the following choices
Replication is a solution that I like but may be too expensive to implement just for me.
Any suggestions on which way I should go with this?
Any other solutions that you can think of?
asked Nov 20 '09 at 09:35 AM in Default
You should really have a development or QA server which holds data representative of the production server, do the development on that and then get the objects you needed added by the DBA.
I would say that's the way to go, rather than developing your reports directly on the production server...
answered Nov 20 '09 at 10:16 AM
Matt Whitfield ♦♦
I think Matt has the best possible answer.
If for whatever you reason you are stuck with the 3 choices you listed, then I would recommend, "A database on the same server + same instance". It has less overhead and requires less resources and administration than the other two options. In particular, it can help you avoid the extra step of setting up linked servers and of maintaining an additional server instance.
answered Nov 20 '09 at 10:38 AM