Note: DataFlux Data Management Server ignores the File storage section of a repository definition. It puts jobs in the default location for the server or in a folder specified in the DMSERVER/JOBS_ROOT_PATH option in dmserver.cfg. DataFlux Data Management Studio 2.6: User Guide
The Data storage section of a repository definition enables you to specify a storage method for the repository database. This database stores metadata for data explorations, profiles, and all objects in the Business Rule Manager (rules, tasks, custom metrics, sources, and fields). The Data storage section has two sets of controls: database file controls and database connection controls. You must use one or the other to specify a metadata storage method.
DataFlux Data Management Studio and DataFlux Data Management Server are installed with repositories that use an SQLite file for the repository database. File-based repositories are simple and reliable. They do not require a DBMS connection, and they may well suffice for testing and training. You can create new repositories in this format, as described in Adding a File-Based Repository for the Client. File-based repositories are not recommended for multi-user access, however, due to locking issues.
Sites usually create DBMS-based repositories for production systems, as described in Adding a DBMS Repository for the Client. To create a DBMS repository, you specify an ODBC DSN connection or a SAS Federation Server connection in the Data storage section of a repository definition. The following database management systems can be used for the Data storage section of a repository. For more information about creating ODBC connections in DataFlux Data Management Studio, see Working with Data Connections. See also Repository Usage Notes for details about some databases.
| Database | ODBC Driver |
|---|---|
| DB2 V8.x, V9.1, V9.5, and V9.7 for Linux, UNIX, and Windows | X |
| DB2 Universal Database (UDB) v7.x for Linux, UNIX, and Windows | X |
| Informix Server 10.0, 11.0, and 11.5 | X |
| Microsoft® SQL Server® 2008 R1, R2 | X |
| Microsoft SQL Server 2005 | X |
| Microsoft SQL Server 2000 Enterprise Edition (64-bit) | X |
| Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) | X |
| Microsoft SQL Server 2000 Service Packs 1, 2, 3, 3a and 4 | X |
| Oracle® 11g R1, R2 (11.1, 11.2) | X |
| Oracle 10g R1, R2 (10.1, 10.2) | X |
| Oracle 9i R1, R2 (9.0.1, 9.2) | X |
| Sybase Adaptive Server 12.0, 12.5x, 15, and 15.5 | X |
| SAS Web Infrastructure Platform Data Server (PostgreSQL) | X |
| Teradata 12.0 and 13.0 | X |
The File storage section of a repository definition is used by DataFlux Data Management Studio only. It specifies a physical path where DataFlux Data Management Studio can store objects that are stored as files, such as data jobs, process jobs, queries, SAS code files (.SAS files), and Entity Resolution Output files (*.SRI files). Any file-based content can be stored in the file storage area of a repository, including your own content such as text files and graphics. You could store documentation files in a project folder, for example.
Note: DataFlux Data Management Server ignores the File storage section of a repository definition. It puts jobs in the default location for the server or in a folder specified in the DMSERVER/JOBS_ROOT_PATH option in dmserver.cfg.
The file storage location can be any physical path that is accessible by DataFlux Data Management Studio. It is possible to specify a location that is remote from the DataFlux Data Management Studio host. However, the client might perform best when the file storage location is local to DataFlux Data Management Studio.
Note: Use a UNC path, not a path with a mapped drive letter, to specify a file storage location that is remote from the DataFlux Data Management Studio host. Example: \\HostName.MyDomain.com\path.
DataFlux Data Management Studio is a Windows application, but it is possible to specify a UNIX location for file storage if this location is accessible to DataFlux Data Management Studio. The following versions of UNIX are supported:
|
Documentation Feedback: yourturn@sas.com
|
Doc ID: dfU_Repositories_DB_Platform.html |