Database files, referred to as the XStudio Database, are owned exclusively by XStudio as a default; when XStudio is running, no other application is allowed access to these files. Any attempts to open, copy or delete these files will be denied by the operating system, as they are already opened exclusively by XStudio.
Making the database available to other applications, called "sharing," can be accomplished in two distinct ways. One method is to enable the XStudio Allow Remote Administration property, which causes XStudio to function as a database server. The other method is to use a separate stand-alone database server application, which implements a client/server relationship between XStudio and the database and makes the database available to other utility applications as well.
|
If you set up XStudio to operate using a remote client/server database model, the local database is not used and any settings applicable to the local database, including allowing remote access, are disabled. |
Database Sharing by Allowing Other Applications to Connect to XStudio
The easiest and most convenient method of sharing database information with another application is to enable the Allow Remote Administration property in XStudio. Essentially, XStudio becomes a database server in addition to its other duties.
When XStudio is functioning as a database server, other utility applications designed for use with XStudio can connect to and view or modify the database depending on the utility application. The utility might be run on the same PC or might be connecting from some other PC. Consult the utility application software documentation for details on how to access the database hosted by XStudio.
Database Sharing Using the Client/Server Model
To implement database sharing using the traditional client/server model, you need to install and configure a stand-alone database server application, typically on a PC other than the one running XStudio. Once the database server application is running successfully, you need to modify the XStudio database properties to have XStudio use the remote database server. For additional information on using the client/server model, see the topic on Using a Remote Database.
|
The necessary stand-alone database server software for implementing a centralized database is not included in the XStudio installation package. If you wish to use a centralized database, contact your vendor for information on obtaining the database server software, along with its requirements for use. |
Effects of Database Sharing
Sharing of the XStudio database has minimal effects on the operation of XStudio and users need not change how they do things when working with XStudio. There are some possible side effects of database sharing to be aware of, though.
Performance
Performance of XStudio can be affected when the database is shared, in the following ways:
1.If XStudio is functioning as a database server in addition to its other duties, application response time could be a bit slower if one or more utility applications are connected and performing database-intensive tasks. This occurs because XStudio has to divide its attention between normal operations and serving the database requests of connected client applications.
2.If XStudio is connecting to a remote database server and network (LAN) traffic is extremely high, application response time could be slower as a result of the the high network traffic impeding retrieval of data from the database server.
Changing Data
In most cases modification of data, whether it occurs within XStudio or is a result of a client utility application making changes, is transparent and automatically handled by XStudio. If a Task is updated, for instance, the next time the Task is used in an Action, the new information is used regardless of whether the change was made within XStudio or made with a utility application connecting remotely.
However, if a remote utility application is re-importing the music library, for instance, and XStudio needs to retrieve song title and artist information, the cart may not be found if the import is in progress at the time of the lookup.
