TS ODBC DataServer lets Windows and Linux applications that support ODBC work with live Thoroughbred data. Excel, Word, Crystal Reports, and databases such as Oracle, MySQL and Microsoft SQL Server can all reach your Thoroughbred files, with no custom programming or changes to your application code.
Read-only or read/write
TS ODBC DataServer comes in two versions. The read-only version guarantees that ODBC users cannot change or damage your data. The read/write version lets ODBC applications update Thoroughbred data, protected by the security controls described below.
How it works
The server software runs on your UNIX, Linux or Windows host, and the ODBC driver runs on Windows or Linux workstations. Any data defined in Dictionary-IV Link and Format definitions can be exposed to ODBC applications. Choosing which files to expose is a one-time step with the Expose Utility.
The product ships in single-tier and multiple-tier models. With the TS ODBC Gateway for Windows Server, a Windows Server acting as a terminal server or web server is the ODBC client, so the workstations that connect to it need no ODBC software of their own.
Security
With ad hoc query tools in users’ hands, only authorized people should see and change application data. TS ODBC DataServer enforces security at four levels.
- User connection. Every connection requires an IDOL-IV login. The driver first tries an automatic login using the client’s connect string, the User-ID and password in the DSN, or the workstation login name. If none works, it prompts for an OPENworkshop User-ID or an IDOL-IV Operator Code and password.
- Tables (Links). Link passwords, operator access codes and group access all apply. A group code ending in R gives read-only access; without the R the group can read and write. For example,
[100R,200,300R]gives groups 100 and 300 read-only access, group 200 read/write access, and everyone else none. Links with I/O triggers are treated as read-only. - Columns (Data Names). Data Name security can blank a column on retrieval, protect it from updates, or limit inserts to the default value. Data Names with a password prompt for it, and Data Names with a post-process cannot be updated.
- Rows (records). When OPENworkshop security is active, record-level security limits users to retrieving, updating and inserting only records whose security value matches theirs.
How it fits
DataSafeGuard can maintain a secondary copy of your database that ODBC tools can query without touching the primary server.