November 9, 2010 at 2:45 pm
Hello SQL experts,
Does anyone have any pointers about how best to provide access to data to third-party vendors? For example, if an application we are developing in consultation with a vendor requires access to data from two different databases, is it better to write views in each database with the requested subset of the data, and grant permissions to the views in both databases, or is it better to create a separate, supplemental database and put the necessary views and other supplemental objects (tables, stored procedures, etc.) in that separate database? This is assuming that the third party doesn't have a pre-created database that we have to install on our systems but rather just wants to run the views to retrieve the data for use in the application.
Thanks in advance for any guidance. Also, let me know if the above needs further clarification.
- webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
November 18, 2010 at 12:01 pm
The way I see it is like this.
I would not want to have any third party vendors to have any access to my database. Therefore I would write a simple service that will provide them with the data they are supposed to get. It is secure and you have full control of what data they get.
-Roy
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply