Read-only Linked Server?
-
We have a linked server setup that uses an ODBC DSN to connect to our Progress database that resides on a Unix system.
Anyone got any ideas on how to make this connection read-only?
Thanks
Phill
--------------------
Colt 45 - the original point and click interface
-
Couldn't you restrict the access on the Progress account that the linked server uses?
Steven
-
We probably could but the Progress Server doesn't use security, and we don't have control over it either.
We have to manage a read-only connection from our end.
Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface
--------------------
Colt 45 - the original point and click interface -
The only other (painfull) suggestion would be to manage all the code that uses the linked server eg tie it down into stored procedures etc, and ensure it only does selects.
Maybe you would also have to consider using openrowset rather than linked servers to ensure noone else uses the connection.
Personally I'd try and see if there is any way to tie down the security at the other end.
Steven
-
Unfortunately we've just wasted three months trying to tie down things at the other end. Let's just say that negotiations were not very fruitful
Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface
--------------------
Colt 45 - the original point and click interface -
If you can create stored procedures in the Progress database, I think you can configure the linked server to be read-only.
There are two parameters in the sp_serveroption procedure that might accomplish this:
data access
Enables and disables a linked server for distributed query access.
rpc out
Enables RPC to the given server.
If you disable dist. queries but enable RPC, then the users would only be able to execute your SP's. I haven't tested this - it's just a idea...
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply