The Database Sample Clauses

The Database. ▪ If you are using an external database, the database must be initialized successfully before you can run Foglight. ▪ If you are using the embedded database, the initialization is performed when you start the Management Server. 2 Start the Management Server: The Management Server can be run in standalone mode, in High Availability (HA) mode (with an external database), or as a Windows® service. See “Starting and stopping the Foglight Management Server” in the Installation and Setup Guide and “Running the Foglight Management Server” in the Command-Line Reference Guide.
The Database. In our database we have information for the different medical reports in a sample of automobile claims. We also have information about the judicial verdict for each of them. In this sense, we can estimate the deviations between preliminary and final BI compensation amount. Our database has 197 automobile BI claim records from an important Spanish insurance company. The common characteristic of all of these claim records is that the compensation amount was determined by judicial verdict. Notice that this kind of claim is not very frequent within the Spanish insurance companies because it is quite normal to reach an agreement between the parties. The insurer paid the compensation amount between the second semester of 2001 and the first semester of 2003. We collected the information for each record taking into account four observations in the life of the claim:
The Database accessed from the main page for “Riga Registers” on this website) The searchable database provides personal and residential details of just over 20,000 individual Jews. It allows users to identify kinship relationships within the framework of a particular document array and, additionally, to track the destinies of the people throughout the period under examination, until the beginning of World War II in Latvia (i.e. until 1941). Sample of one person from data base: Family name Maiden name First name FatherMotherDate of birth or age in Place of birthPlace of origin or citizenshipResidenceOccupationGender Family StatusDate of registration Date of struck offPlace of struck offReference MARKUSE JOSSELOWITSCH Hanna Sorach 18921506 Daugav- pils Jel- gavaDag- das 4-10 House wife F Married1922281219231502 Un- known2942-1-3211 The systematization of data by surnames provides an option to identify individuals with the same surname. Off course, this is not the factor to define kinships accurately; indeed, it provides a solid base for a further study. Under the systematization by addresses, there is an option to define the number of persons who simultaneously resided at this particular address. Usually relatives, representatives of one family, occupied a particular apartment. Beyond the identification of kinship relationships, the database provides an opportunity to track the history of a particular family. It should be mentioned that, as in the case ofany source of information, these registers were the subject of critical approach. There is some inaccuracies, most often related to the date and place of birth, especially in the registers for the 1920’s. These records were frequently compiled on the basis of oral information. As regards surnames, there were some inaccuracies arising from misspellings or the use of a form of a surname adjusted to the rules of Latvian language, etc. The mistakes in dates of birth were sometimes caused by confusions in use of both old and new calendars (Julian and Gregorian). The completeness of the records of house-registers may vary. Sometimes there is only one name recorded in the name cell, while in other registers all names of a particular individual are given. Riga residents moved frequently within the limits of the city. The residence at one address during a significant period of time (1920 – 1941) is rather an exception than a rule.Where house-registers have not been completely preserved, other sources of information can be used i...
The Database. This study reports the preliminary results of a subset of existing buildings extracted from the full database of 2245 RC buildings for which cost data are available. Due to the significant effort needed to collect and analyze the actual repair cost at component level, the subset is limited to 63 RC buildings, which represent about the 3% of the population. Further research effort is needed to have a significant statistical sample to derive proper statistics representative of the population. The frequency distributions of the buildings as function of the construction age, number of storeys and usability rating are reported in Figure 1a,b,c and Figure 1d,e,f for the full L’Aquila database and the subset of buildings object of this study, respectively. 900800No. of buildings [-]7006005004003002001000900800No. of buildings [-]7006005004003002001000
The Database. While the database engine was moved from OpenVMS/RDB to WinNT/SQLSERVER in 1998, the underlying schema for the logbook entries has not changed since its inception in 1991. The schema can divided into two parts, the first is a fixed set of four tables that are used to manage user text entries. These are the tables that ENTRY_DISPLAY operates on. The rest of the database contains numeric tables that hold analyzed data, diagnostic configuration information, and shot summary data. These numeric tables are not accessed with this interface; instead they are accessed using the general IDL database interface [2], or any ODBC compliant database client. Using the same database for all of this information has the advantage that joins can be performed between these numeric tables and the entries table. For example, a user can find the entries that were entered since some run pertaining to shots with some particular plasma parameters and diagnostic configuration. The four tables that are accessed directly by ENTRY_DISPLAY are:
The Database. Seller owns outright and has good title to the Database free and clear of any Lien. This Agreement and such other conveyancing documents as shall have been executed and delivered to the Buyer will convey good title to the Database, free and clear of any Liens. The Assets transferred pursuant hereto constitute all of the assets necessary and appropriate for the conduct of the Business as of the date hereof in substantially the same manner as the Business has heretofore been conducted.
The Database. The case study was undertaken for the campaign of card re-activation in September 2014. A CC database containing more than 3 million customers, and with data corresponding to operations made between 2008 and 2013, was used to develop the case study. The database includes general information and reproduces the behaviour of the customers.Some of the fields in the data base from CC are represented in Table 1.a and Table 1.b.
The Database. 5.2 Subject to clause 5.3 and the terms of the Assignation, title to the Business and all the Assets will pass on the Effective Date.
The Database. The second element of the CAMCES tool is the underlying database. The database consists of three major parts: