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 |
|
gsparkman
Starting Member
3 Posts |
 Posted - 2008-07-10 : 07:17:07
|
| Can anyone recommend a strategy for sharing SQL Server data with a client? We do not want to give them access through enterprise manager but we do want them to be able to use their own report writing tools to access our data. Preferably we would like to restrict them to their own database, if possible and read only rights for specific tables and views.If possible we don't want them to see anything else. If you can provide steps, that would be most helpful. Thanks |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-07-10 : 07:25:04
|
| Create views on the db containing only the data they require and only provide users access to this views. |
 |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-10 : 08:25:40
|
quote:
Originally posted by visakh16
Create views on the db containing only the data they require and only provide users access to this views.
Thats what we do for our reporting clients. |
|
|
|
gsparkman
Starting Member
3 Posts |
Posted - 2008-07-11 : 15:54:12
|
But it looks like they still have the ability to see other table structures, view structures etc. Any way to only see "view" structure??quote:
Originally posted by visakh16
Create views on the db containing only the data they require and only provide users access to this views.
|
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-11 : 15:56:34
|
| Did you give View definition permission? |
|
|
|
contrari4n
Starting Member
27 Posts |
Posted - 2008-07-11 : 16:39:40
|
| Apart from security, you should also worry about performance impact of their queries.In a web-based ordering system all it takes is one moron with a long running query, taking a shared table lock, and your customers could find themselves unable to place orders, potentially costing your company thousands in lost revenue.If you could replicate, or log ship, to a reporting database (ideally on a different server) then that would be the best option.Richard Fryarhttp://www.sql-server-pro.comSQL Server Articles and Tips |
|
|
|
|
|
|
Client Access to Your SQL Db for Reporting??