oltp database design

Tags: performance selection memcached style HTTP under Good information fetch numberWhen you design a database, a field belongs to one table, but it appears in the other or more tables at the same time, and is exactly the same as the meaning of the table it belongs to, then this field is a redundant field. --These are the definitions I gave myself. Is the existence of redundant fields good or bad ( Redunda

3 efficient Tags tag system database design solutions, tags design solutions Background Currently, mainstream blog systems and CMS all have a TAG Tag system, which not only enhances the structure of content links, but also allows articles to be distinguished by tags. Compared with the traditional Keyword mode, this Tag mode can independently

underlying technology, my application access to the database and the daily operations are finally out of the low-level phase. After that, the various performance problems of the table and countermeasures are clear up.In recent years, the Microsoft two-bit database "Danale" Howard Yin, Max shen articles, with the help of two experts, and refer to a number of technical books, borrow 51CTO this piece of feng

department2, the domain can be a module, can be a page, or it can be a button on the page3, the permission can be "visible", can be "read-only" or "available" (such as a button can be clicked)is actually the WHO, what, how problemSo the six tables mentioned above can actually design a table:IV, example descriptionHere is an example of a design description. "User, role on page is permission to use"Detailed

Label:Design of questionnaire module of database design 1 2016/07/13 Update The entire internship has come to an end, in fact, the entire Questionnaire module database design, in early June basically has been finalized and realized. This summary is divided into two parts. One, to the previous proposed a few legacy issu

Database Design Skills and database skills 1. Relationship between original documents and entities It can be a one-to-one, one-to-many, and many-to-many relationship. In general, they are a one-to-one relationship: an original document corresponds to only one entity. In special circumstances, they may be one-to-many or many-to-one relationships, that is, one ori

http://kb.cnblogs.com/page/138526/English Original: Important Database Designing rulesBrief introductionBefore you start reading this article, I have to tell you clearly that I am not a master of database design. The 11 points listed below are the personal insights I have learned from my own experience in project practice and reading. I personally think they have

purpose of each field and any aliases that may exist. This is absolutely necessary for the documentation of SQL expressions. 5 Define standard Object naming conventions The naming of various objects in the database must be canonical. 2. Table and field design (Database logic design) Table

Label:OverviewRegardless of which database we use, no matter how we design the database, I would like to follow a principle: data security and performance efficiency of the two main aspects, but about these two aspects of the topic too much, here is not a statement, I just from the database of physical distribution

Link Attribute Tuples Insertion exception: when inserting data, the data cannot be inserted into the database, and the relational database cannot be operated, that is, the insertion exception. Deletion exception: when unnecessary information in a link is deleted, the information that should not be deleted is also deleted, that is, the deletion exception. Update exception: when updating a

Before designing a database1. Test the existing environmentWhen designing a new database, you should not only carefully study the business needs, but also examine the existing system. Most DatabasesProjects are not built from scratch. Normally, there will always be existing systems within the Organization to meet specific needs (there may be no realAutomatically calculated ). Obviously, the existing system is not perfect, otherwise you do not have to

Design tables and fields1. Check for various changesWhen designing a database, I will consider which data fields may change in the future. For example, the last name is like this (noteIt refers to the surname of a westerners, for example, the surname of a female after marriage ). Therefore, when establishing a system to store customer information, I tendStore the Last Name field in a separate data table, an

button on the page 3, the permission can be "visible", can be "read-only" or "Available " ( such as a button can be clicked ) is actually the WHO, what, how problem So the six tables mentioned above can actually design a table: IV, example description Here is an example of a design description. "User, role on page is permission to use" Detailed design: 1,

department 2, the domain can be a module, can be a page, or it can be a button on the page 3, the permission can be "visible", can be "read-only" or "Available " ( such as a button can be clicked ) is actually the WHO, what, how problem So the six tables mentioned above can actually design a table: IV, example description Here is an example of a design description. "User, role on page is permission t

Chapter 1 design database applications Database applications allow users to interact with information stored in the database. The database provides an information structure for different applications to share.Delphi 4 supports relational databases. Relational databases organ