We restore the DB every night to a separate box and they can query the hell out of it.
No way I'm letting people query the actual DB..have seen to many ugly queries in the past bringing down the system performance wise.. From: [email protected] [mailto:[email protected]] On Behalf Of Damien Solodow Sent: Thursday, November 12, 2015 9:03 PM To: [email protected] Subject: RE: [mssms] Replicate the SCCM database Replication is too much work. :) Grant them access to the database by assigning them the following roles to it in SQL: db_datareader, db_denydatawriter They'll be able to run queries against it, but won't be able to make any changes/edits. DAMIEN SOLODOW Senior Systems Engineer 317.447.6033 (office) 317.447.6014 (fax) HARRISON COLLEGE From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of HELMS, DAVID C Sent: Thursday, November 12, 2015 2:59 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] Replicate the SCCM database I've got requests from other areas in my company where they want to connect to the SCCM database to run queries from. My thought is to copy the database to another server and allow others access to it if they want the information. I've always been hesitant about giving anyone access and wanted to get opinions from our expects on this? If copying the database is the best solution, what method is recommended? I am not a SQL guy, so need some advice. Thanks, David
