oltp database design

information, see Oracle Installation documentation and random documentation. 3.2 Database Design Principles* ConventionsWe agree that 26 English letters (case sensitive) and 10 natural numbers 0-9 are used, and underscores (_) are added, which are 63 characters in total. No other characters are allowed (except comments ).* Database SIDThe

not be greater than the number of hard disk controllers. For OLTP applications, the data access volume is small. Generally, the size of 32 kb or 64 kB entries can be selected, while the DSS application accesses a large amount of data, you can consider the size of a 64KB, 128KB, or 256KB shard. Design and Development of Oracle database applications After the Orac

span each hard disk controller, and vertical bars span the entire hard disk set. The number of members in the set should not be greater than the number of hard disk controllers. For OLTP applications, the data access volume is small. Generally, the size of 32 kb or 64 kB entries can be selected, while the DSS application accesses a large amount of data, you can consider the size of a 64KB, 128KB, or 256KB shard. Application

= Redis.sdiff ("Tag.ruby", "Tag:web") A collection of Ruby and Web-owned books. Inter_list = Redis.sunion ("Tag.ruby", "Tag:web") It's not easy enough. From the above 2 examples can be seen in some scenarios, relational database is not very appropriate, you may be able to design a system to meet the needs, but always feel strange, there is a kind of rote feeling. In particular, login system This example,

Change to a single record of historical data: Common Database Design (2) -- change to a single record of historical data problems 1. Overview There is a type of data stored in the historical customer operation data, such as the bidding documents, the refining scheme list, the price change of the product price, and the change list. Such historical data includes a mainstream water meter that controls the fl

[Test] database system principle (II)-detailed explanation (database design and ER Model), database system principle er Everything has a lifecycle. Of course, the database system is no exception! The database

Design method of database table structure When we design a database storage mode, we need to analyze the data pattern carefully and not put all the data together in a single brain. In that case, the availability of the system, efficiency, scalability will have a serious impact. Of course, the system you designed is ve

Typically, there are two ways to judge whether a database is designed to be a comparison specification. One is to see if you have a large number of narrow tables, and the second is whether the number of wide tables is enough. If these two conditions are met, it can be explained that the standard level of the database is still relatively high. This, of course, is a two-a-kind indicator. In order to meet the

support staff is usually high. Are skilled personnel available? Do you need to add new recruits? Do you need to hire a consultant at a high price? · Hardware overhead-evaluates hardware requirements based on speed and storage capacity needs. For OLTP databases, concurrency, on-board Ram, dedicated hardware devices (RAID matrix), and network bandwidth are all important factors. The storage space design and

Abstract: The database is the foundation of the system. If you need to change the fields of the database frequently, or even modify the table and table relationship, I believe that no one will be able to cope with it several times! Because of the changes in the database structure, not only the changes in the database

The design paradigm (paradigm, database design paradigm, and database design paradigm) is a set of relational patterns at a certain level. Database construction must follow certain rules. In relational databases, this rule is a pa

level of privilege :4.1 in combination with the user's "role permission Level" + "corporate Identity" + "department identification" + "employee identification", go to the employee information sheet to find the appropriate employee, as follows: role Permission LevelValue:1. Company leaders: Find Employee Information sheet. Company Identity = = The user. Corporate identity > All Users;2. Department Leaders:Find Employee Information sheet. Companyidentity = = The user. Company logo Employee Inform

The ORACLE tutorial is: several methods to optimize the design of Oracle database tables. Preface Most Oracle Database performance problems are caused by unreasonable Database design. Only a small number of problems are rooted in the unreasonable configuration of memory modu

Label:I. Interface designRegardless of the student, teacher landing interface is unified, according to the user name entered to determine what kind of interface to enter.After the student login interface:Teacher interface: After the teacher login to the course name interface, select the course to get the second picture.Two. Class diagram designThree. Database designCourses: Course number , classes, teacher number, time, teacher, capacity, prerequisite

smaller units. In the database design, start the top-level step by identifying the relationship between the object and the data, and then gradually add details, such as the information about the object and the link you want to save (as an attribute) and all constraints on entities, relationships, and attributes. 128. Transaction: an action or a series of actions executed by users and applications to access

http://blog.csdn.net/taijianyu/article/details/5945490One: Nullable columns should be avoided in the table;Two: The table should not have duplicate values or columns;Three: The records in the table should have a unique identifierIn the database table design, the database administrator should develop a good habit, with an ID number to uniquely identify the row rec

the system, then, these structures are gradually subdivided into smaller units. In the database design, start the top-level step by identifying the relationship between the object and the data, and then gradually add details, such as the information about the object and the link you want to save (as an attribute) and all constraints on entities, relationships, and attributes. 128. Transaction: an action or

1. Access Method: This step includes storing and retrieving records from files.2. Alias (alias): Another name of an attribute. In SQL, you can replace the table name with an alias.3. Alternate keys (backup key, ER/link model): no candidate key is selected as the master key in the entity/table.4. anomalies (exception) See Update exception (update anomalies)5. Application Design Program Design): a stage in th