没有合适的资源?快使用搜索试试~ 我知道了~
首页TRIPmanager系统管理员指南:数据库管理与设置详解
TRIPmanager系统管理员指南:数据库管理与设置详解
需积分: 11 1 下载量 90 浏览量
更新于2024-07-19
收藏 6.59MB PDF 举报
TRIPmanager参考手册是一份详细的指南,专为管理员管理TRIP系统而设计。版权属于2014年的Tieto Sweden AB,它提供了关于TRIP系统的全面操作和管理教程。这份文档的目的是帮助用户了解系统的各个方面,包括但不限于数据库管理、基础操作、数据模型组织、字段类型以及数据库创建和维护。
在手册的开始部分,作者对TRIP命名约定进行了介绍,确保用户理解系统中的逻辑命名规则。接着,文档分为两大部分:第一部分是数据库管理,涵盖了基础概念如导航TRIPmanager界面、系统基本原理、数据模型构建和组织、字段类型以及对CONTROL数据库的深入理解。
在数据库管理章节中,首先解释了如何在TRIPmanager中进行导航,接着阐述了数据库的基础知识,包括记录的管理和文件结构的设置。创建数据库时,手册指导用户考虑文件位置、通用属性设定(如数据库名称)、物理文件布局,以及如何启用XML功能。描述数据库时,还涉及到保存设计和修改数据库属性的过程,这些属性包括一般设置、文件配置、索引策略以及链接选项。
具体到数据库操作,用户可以学习如何设置数据库的通用属性,例如定义数据存储的位置,以及如何利用交易日志进行数据保护。此外,手册还详细解释了如何针对不同的需求调整数据库,如设置索引以优化查询性能,以及管理数据之间的链接关系。
总结来说,TRIPmanager参考手册是一份实用的手册,适合TRIP系统的管理员和技术人员,他们可以通过这份文档深入了解系统的操作流程,提升数据库管理效率,确保系统的稳定运行。对于任何希望有效利用TRIP系统的人来说,这是一份不可或缺的参考资料。
Part 1 - Database Administration Chapter 1: Fundamentals
Page 16 of 390
RDBMS data table EMPLOYEES
Employee
Title
EmployeeNo
DeptNo
Fred Jones
Clerk
1268
20
Ben Smith
Salesman
7582
10
Ed Wedge
Salesman
7654
10
× RDBMS data table DEPARTMENT
DeptNo
DeptName
10
Sales
20
Administration
Table 1–3 Sample relational database tables
Using an SQL (Structured Query Language) statement to extract all employees in the
Sales department, the tables are joined using the field ‘DeptNo’:
SELECT Employee
FROM EMPLOYEES, DEPARTMENT
WHERE DEPARTMENT.DeptName=“Sales”
AND EMPLOYEES.DeptNo=DEPARTMENT.DeptNo;
When designing such a data model, considerable effort is typically expended in
constructing the various tables to ensure that data does not become redundant. This
process is referred to as data normalization.
Also, much thought must be given to constructing the index for these tables so that, for
instance, the join between the two ‘DeptNo’ columns can be performed as rapidly as
possible. Without this extra effort, searches will complete extremely slowly.
Full Text Database Management Systems
In contrast to other database models, the full text model calls for complete indexing of all
possible database content. This frees database designers to spend more time on user
interface issues such as form design and appearance, rather than on maximizing data
model efficiency. As a result, full text applications tend to focus on large bodies of often
natural language text, including books, documents and log files, rather than on small,
discreet units of information which are more suited to relational database management
systems.
Part 1 - Database Administration Chapter 1: Fundamentals
Page 17 of 390
Indexing the Data
The fragment index is a hitherto unique feature of the TRIP database system which
provides significant performance increases when searching for truncated terms. For
instance, in the following table, the fragment index is used to locate terms, which in turn
are used to locate content within the database itself. The example the CCL order:
Find $DRE$
finds any term in the database which contains ‘dre’, in this case, ‘dream’ and ‘dreams’.
As full text systems maintain a complete index, vocabulary listings are also a common
feature. For example:
Display $DRE$
will return a list of all terms in the index which contain ‘dre’.
Database Content
Word
Index
Table
Fragment
Index
I dream of falling; surrounded
by colours,
DREAM
DRE
I am swept by their
confidence,
Into the dreams of childhood,
DREAMS
DRE
Past the fondness of life.
Emotions flaking as dead
skin,
I see with the eyes of the
innocent.
Table 1–4 Sample full-text database table
Data Organisation
TRIP is a database system which has been specifically designed and implemented to
handle the large amounts of variable length data, which is typical of free text
applications. Free text is used here to mean natural language text, as found in books,
letters, reports, log files, etc.
It is the unpredictable length of the data strings encountered in such applications which
accounts for the main technical difficulties in designing and implementing a system to
handle such data efficiently. Most conventional DBM (database management) systems
deal mainly with fixed length blocks of data, and possess a very limited capacity for
manipulating variable length text data. These field length fluctuations influence both the
file structures and data access methods adopted during TRIP system design, and it is
here that TRIP shows itself uniquely well placed for building this type of application.
The choice of data which TRIP has been implemented to handle most efficiently
determines, to some extent, the contents of typical fields within the system. Free text
documents are, for example, normally broken into chapters, sections and paragraphs.
Paragraphs are further subdivided into sentences, and sentences into words. In terms of
fields, the most natural choice might be the collection of paragraphs into sections or
chapters. Thus fields in TRIP which contain textual data might typically contain a
number of paragraphs.
Part 1 - Database Administration Chapter 1: Fundamentals
Page 18 of 390
Within TRIP, the record level of organisation can be equated to a document, and the
database may correspond to a collection of related documents.
Meta-record structures are also available, in which the head record contains information
common to a number of sub-entities. A meta-record can be used to describe a collection
of articles in a periodical, the head record containing such information as journal title,
publisher, etc. and each part containing specifics regarding individual articles such as
author, text and references cited.
A database might alternatively consist of a number of product descriptions. Each
product would have its own record within the database and each record could consist of
fields for the product name, product number, product description and date of
introduction. If this database employed meta-record structure, record parts might then
contain serial number, production run number, alterations from the basic model, etc.
TRIP Field Types
Although TRIP was designed specifically for the efficient manipulation of free text, most
documents have auxiliary information associated with them which are not free text, such
as dates, times, numbers, authors, publishers etc. To accommodate varying data
formats, TRIP supports seven data types, TExt, PHrase, DAte, TIme, NUmber, INteger
and STring, as described below.
TExt stores free text in sentences and paragraphs. There can be any number of paragraphs
within a TExt field, which in turn may have any number of sentences of any length.
The position of every word in the text is noted in the appropriate file when the records
are indexed, including the number of the paragraph within the text field, the number of
the sentence within the paragraph, and the number of the word within the sentence.
PHrase usually contains short text elements, e.g. names, addresses, identifying numbers or
product codes. Each individual phrase constitutes one subfield. There can be any
number of subfields within a PHrase field and phrase fields may contain any number of
characters, however while all words in the entire phrase will be word indexed, unlike in a
TExt field, the whole phrase index will only use the first 255 (normalised) chars
Note:
In this context, ‘normalising’ means first replacing all blank equivalents with blanks,
then removing all leading and trailing blanks, as well as compressing all sequences of
blanks to just a single blank.
Example (where ‘◦’ represents a blank or space character):
The phrase "◦◦◦Tarzan,◦◦Jane◦and◦◦◦◦◦Cheeta◦like◦◦◦bananas!!!◦◦◦◦" will be normalized
to "TARZAN◦JANE◦AND◦CHEETA◦LIKE◦BANANAS").
When records which contain PHrase fields are indexed, the phrase along with all
subfield contents (as well as each individual word) is noted in a TRIP index file along
with its position (the number of the subfield within the field and the number of the word
within the subfield).
Note:
A phrase field can be any length but the index term for the complete phrase will be
maximum 255 chars (normalized as described above). However, each single word of a
phrase of any size will be indexed. The limit of 255 chars in the index only affects the
whole phrase.
Part 1 - Database Administration Chapter 1: Fundamentals
Page 19 of 390
NUmber holds single precision numeric information, both integers and real numbers, each
number in a subfield of its own. Real numbers must keep within the limits of -1.7E+37
and 1.7E+37.
The accuracy of NUmber is seven digits. At indexing the position of each value is noted
(the number of its subfield within its field).
INteger is used for integers only, and is indexed in the same way as NUmber. The allowable
range is between -2,147,483,647 and +2,147,483,647.
For greater accuracy, use the data type INteger whenever possible.
DAte stores dates, primarily of the form year-month-day
(e.g. 1985-04-20 or 85.04.20). A year only (1985 or 85) or a year and month only (1985-
04 or 85-04) may also be used when entering data or searching. It is indexed in the
same way as NUmber.
This is the standard date form, but other date forms are available. See the ‘Date Form’
section in Chapter Ten of the TRIPclassic User Guide entitled ‘User Administration’ for
more information.
Part 1 - Database Administration Chapter 1: Fundamentals
Page 20 of 390
TIme holds the time of day, expressed in 24-hour nomenclature of hours, minutes, and
seconds (e.g. 11:04:02 or 11.04.02). The hour only, or the hour and minute only may
also be given when entering data or searching. It is indexed in the same manner as
NUmber.
STring contains a string of characters of any kind, i.e. images, video, voice etc. Data of type
STring cannot be indexed.
The field type determines some aspects of the manner in which the system accesses
data held within a field, as well as its indexing. It also determines to some extent the
information that can be entered into that field. For instance, in DAte and TIme fields
there is an implicit validation employed that ensures that the data entered can be
interpreted as a date or time.
TExt data is organized into paragraphs and sentences. PHrase, DAte, TIme, NUmber
and INteger data types may be divided into an unlimited number of subfields, which can
then be used for range searching within the database. STring fields are stored within the
database, but are not indexed, and so cannot be retrieved using TRIP’s query language,
CCL.
The CONTROL Database
A database system needs some method of tracking all of its parts or components, which
in TRIP include users, user groups, databases, clusters, thesauri, reports, data entry
forms, search forms, procedures and macros. This is done by way of the system data
dictionary, a database known as CONTROL which contains definitions of the data
structures currently within the system. Each definition within CONTROL occupies a
separate dictionary entry.
The contents of the CONTROL database are illustrated schematically below.
C O N T R O L D A T A B A S E
System Manager
Output
Formats
Search
Forms
Data Entry
Forms
Databases
Database
Administrator
Individual
Users
User
Profile
Group
Procedures
User Manager
User Groups
User
Procedures
Public
Procedures
Public Group
Clusters
Thesauri
Figure 1–2 The CONTROL database
剩余389页未读,继续阅读
Liu_Dag
- 粉丝: 37
- 资源: 26
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- WPF渲染层字符绘制原理探究及源代码解析
- 海康精简版监控软件:iVMS4200Lite版发布
- 自动化脚本在lspci-TV的应用介绍
- Chrome 81版本稳定版及匹配的chromedriver下载
- 深入解析Python推荐引擎与自然语言处理
- MATLAB数学建模算法程序包及案例数据
- Springboot人力资源管理系统:设计与功能
- STM32F4系列微控制器开发全面参考指南
- Python实现人脸识别的机器学习流程
- 基于STM32F103C8T6的HLW8032电量采集与解析方案
- Node.js高效MySQL驱动程序:mysqljs/mysql特性和配置
- 基于Python和大数据技术的电影推荐系统设计与实现
- 为ripro主题添加Live2D看板娘的后端资源教程
- 2022版PowerToys Everything插件升级,稳定运行无报错
- Map简易斗地主游戏实现方法介绍
- SJTU ICS Lab6 实验报告解析
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功