Studio

Which ODBC sources can function as a Studio Repository?

The following databases have been certified to function as a repository for Studio metadata: Microsoft SQL Server, Microsoft Access, and Oracle 8i or later.

What is the recommended ODBC data source type for a Studio Repository?

We recommend that a Studio Repository be defined as a System DSN.

Is a Studio Repository intended for concurrent usage?

No, a Studio Repository is intended to be used by a single user in a single session, not by multiple simultaneous users or by multiple simultaneous sessions.

If a Studio Repository is put into concurrent use, it is possible that conflicting operations may occur that can result in repository damage.

How then do I obtain exclusive access to a Studio Repository?

If you are using Microsoft Access for your Studio Repository, you can obtain exclusive access to the Access database in one of two ways.

The first way is at the ODBC level through the ODBC Data Source Administrator panel: select the Repository’s DSN, Configure->Options, and then check the Exclusive box.

The second way is directly through the Access application: having opened the Repository’s database, enter Tools->Options->Advanced and click the Exclusive radio button in the Default Open Mode section.

If you are using Microsoft SQL Server for your Studio Repository, you can obtain exclusive access through the Enterprise Manager: select the database that you wish to restrict, then right-click Properties->Options and finally click the Restrict Access check-box followed by the Single User radio button.

Why do ODBC CHAR data types contain an extra byte when used in FORMATs?

The ODBC char type adds another byte for a null terminator as required by the ODBC API.  If you don’t want that, use an ORACLE CHAR, TEXT, or an IMAGE X in your FORMAT for fixed character type definitions that don’t require null terminators.