Table of Contents

Search

  1. About the Data Vault Administrator Guide
  2. Introduction to the Data Vault
  3. Data Vault Service Startup and Shutdown
  4. Data Vault Configuration
  5. Data Vault SSL Setup
  6. Data Vault ODBC Setup
  7. Data Vault Administration
  8. Data Repartitioning
  9. Partial Data Vault Copy
  10. Archived Data Migration
  11. Data Validation
  12. Bulk File Uploader
  13. Data Vault Administration Tool
  14. Data Vault Logs
  15. User Account Privileges
  16. ssasql Command Line Program
  17. Data Vault Audit Log
  18. Appendix A: Sample Configuration Files

Data Vault Administrator Guide

Data Vault Administrator Guide

Client Connections

Client Connections

Clients must connect to the Data Vault to query archived tables registered with the Data Vault repository. Clients can connect to Data Vault using an ODBC-enabled front-end tool. To make a connection possible, a new [CONNECTION
connection-name
] section must be added to the client-side
nucleus.ini
file (where
connection-name
can be any desired name for the connection). The Host and Port values in this section must match those used by the Data Vault Service load balancer, as specified in the
ssa.ini
file. The
connection-name
is subsequently used by the client to connect to the load balancer.
The following table gives an example of the client connections:
ssa.ini (excerpt)
client-side nucleus.ini (excerpt)
[SERVER] Host=ALPHA1 Port=9975 ...
[CONNECTION dvs] Host=ALPHA1 Port=9975 ...
In the above example,
dvs
is the connection name. To connect to a Data Vault repository database called
adm
, the user authorization JOE uses the following command line invocation:
ssasql dvs adm JOE
ODBC client connections also require a new Data Source Name (DSN) that references the information described above.

0 COMMENTS

We’d like to hear from you!