Caché System Administration Guide - InterSystems Documentation
Caché System Administration Guide - InterSystems Documentation
Caché System Administration Guide - InterSystems Documentation
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Configuring Data<br />
Menu Item<br />
NLS Settings<br />
Source Control Settings<br />
SQL Settings<br />
Startup Settings<br />
Task Manager Email Settings<br />
Zen Report Settings<br />
<strong>Documentation</strong> Source<br />
Configuring NLS Settings section of this chapter<br />
“Using Studio Source Control Hooks” appendix of Using<br />
<strong>Caché</strong> Studio<br />
Configuration Settings section of the <strong>Caché</strong> SQL<br />
Reference<br />
Startup Settings of <strong>Caché</strong> Additional Configuration<br />
Settings Reference<br />
Configuring Task Manager Email Settings section of<br />
this chapter<br />
Configuring Zen Report Settings section of this chapter<br />
Most configuration changes can be done dynamically and do not require you to restart <strong>Caché</strong>. When<br />
the update does require a restart, the portal notifies you.<br />
This chapter covers the following topics:<br />
• Configuring Data<br />
• Configuring <strong>System</strong> Information<br />
• Configuring Task Manager Email Settings<br />
2.1 Configuring Data<br />
<strong>Caché</strong> stores data — persistent multidimensional arrays (globals) as well as executable code (routines)<br />
— in one or more physical structures called databases. A database consists of one or more physical<br />
files stored in the local operating system. A <strong>Caché</strong> system may (and usually does) have multiple<br />
databases.<br />
Each <strong>Caché</strong> system maintains a database cache — a local, shared memory buffer used to cache data<br />
retrieved from the physical databases. This cache greatly reduces the amount of costly I/O operations<br />
required to access data and provides much of the performance benefits of <strong>Caché</strong>.<br />
<strong>Caché</strong> applications access data by means of a namespace. A namespace provides a logical view of<br />
data (globals and routines) stored in one or more physical databases. A <strong>Caché</strong> system may (and usually<br />
does) have multiple namespaces. <strong>Caché</strong> maps the data visible in a logical namespace to one or more<br />
physical databases. This mapping provides applications with a powerful mechanism for changing an<br />
application’s physical deployment without changing application logic.<br />
<strong>Caché</strong> <strong>System</strong> <strong>Administration</strong> <strong>Guide</strong> 13