Any .Net app can have direct access to remote data of whatever flavor -
Oracle, SQL Server, MySQL, DB2 on i, DB2 on whatever else. It just uses
ODBC or .Net data providers.
These can be set up for read-only, too, in the connection configuration
- there is good reason to block this - and probably NOT to use ODBC DSNs
(data source names), since the latter can be modified by whomever has
access to the PC where they live.
Another idea is to provide stored procedures on IBM i that give only the
data required. And this would be read-only almost by definition.
At the risk of being over-critical - data duplication just to have a
single RDBMS to get it from seems like lazy programming and designing.
Not necessarily in that order.
On 10/5/2012 10:39 AM, Chris Bipes wrote:
But with the IBM iSeries Access OBDC drivers on the .NET application server, you can pull the data directly off of the iSeries. No copying of your data to a less secure server. But not being a .NET programmer, can you attach to a remote DB server or does the DB server have to run on the same box as the application server? (Really a bad idea if being opened to the internet.)