Db2 – Can a Z/OS mainframe application or DB2 read a SQL Server database/table directly

You could create a hidden timestamp column in DB2 on the replicated tables. When you run the replication job you can pull just the data that has changed since the last replication. This would lower the quantity of data sent.

For instance, run the SSIS package every minute pulling just the last minutes worth of data.

Or, instead of a timestamp field, you could use an auto incrementing int and keep a small table on the replicated instance that records the last int value replicated. The replication process would grab any new records, and update the small table's value to reflect the last value replicated.

There is no read only privilege on a database in DB2. You will need to grant SELECT privileges on specific tables, preferably via a role to avoid doing this multiple times.

1. Create a new database role, e.g. create role readonly.
2. Grant SELECT privileges on the required tables to that role: grant select on myschema.mytable to role readonly.
3. Create a new user in the operating system, e.g. # mkuser newuser.
4. Grant the role to the user: grant role readonly to user newuser.

Note that the new user will likely need to change the initial password before he or she can connect to the database.