文档库 最新最全的文档下载
当前位置:文档库 › 外文翻译--关于数据库死锁的知识

外文翻译--关于数据库死锁的知识

外文翻译--关于数据库死锁的知识
外文翻译--关于数据库死锁的知识

外文翻译

About the database of the knowledge of the deadlock Database itself provides lock management mechanism, but from a hand, database is the client applications "puppet", this is mainly because the client to the server has complete control of the gain of locks ability. The client in enquiries in the request and the way to query processing tend to have direct control, so, if we application design reasonable enough, then appear database is normal phenomenon dead lock.

Below are listed some easy to have locked application examples:

A, the client cancel inquires no roll back after practice.

Most of the application is inquires often happens homework. However, users through the front desk the client application inquires the backend database, sometimes will cancel inquires for any variety of reasons. If the user to open the window after mouth query, because users find reflect crash or slow compelled to cancel the query. But, when the client when cancel inquires, if not add rollback transaction statement, then at this time, because the user has to the server sends the inquiry's request, so, the backend database involved in the table, all have been added L locked. So even if the user cancel after inquires, all in the affairs for the locks within will remain. At this point, if other users need to check on the table or the user to open the window through input inquires to query conditions to improve the system response speed occurs when the jam phenomenon.

Second, the client not to get all the results of my query.

Usually, the user will be sent to the server after queries, foreground application must be done at once extraction all the results do. If the application did not extract all the results trip, it produces a problem. For as long as the application did not withdraw promptly all the results, the lock may stay at table and block other users. Since the application has been submitted to the server will SQ statements, the application must be extracted all results do. If the application does not follow the principle words (such as because at that time and no oversight configuration), can't fundamentally solve congestion.

Three, inquires the execution time too long.

Some inquires a relatively long time will cost. As for the query design is not reasonable or query design to watch and record it is, will make inquires the execution time lengthen. If sometimes need to Update on users record or Delete operation, if the line is involved in it, you will get a lot of lock. These locks whether finally upgrade to watch the lock, can block other inquiries.

So often, don't take long time running decision support search and online transaction processing inquires the mixed together.

When database meet blocked, often need to check the application submitted to the SQL statement itself, and check and connection management, all the results do processing and other relevant application behavior. Usually, the lock for to avoid the conflict in the jam, the author has the following Suggestions.

Suggest a: after the completion of the extraction of all query results do.

Some applications in order to improve the response speed of the user inquires, will have the option of extraction need record. The "smart" looks very reasonable, but, but will cause more waste. Because inquires not timely and fruit extraction of words, the lock cannot be released. When others inquires the data, will be happening.

So, the author suggest in application design, database query for record to the extraction of in time. Through other means, such as adding inquires the conditions, or the way backstage inquires, to improve the efficiency of the inquires. At the same time, in the application level set reasonable cache, and can also be very significantly improved query efficiency.

Suggest two: in the transaction execution don't let the user input content.

Although in the affairs of the process with sex, can let the user participation, in order to improve the interactivity. But, we don't recommend the database administrator tend to do so. Because if the user in affairs during the exec ution of the input and number, will extend the affairs of the execution time. Although people smarter, but the response speed still don't have a computer so fast. So, during the implementation of the user participation to let the process, will extend the a ffairs of waiting time. So unless there is a special needs, not in the application's execution process, reminds the user input parameters. Some affairs of the executive must parameters, best provide beforehand. If can through the variables in the parameters such as need to go in.

Suggest three: make affairs as far as possible the brief.

The author thinks that, database administrator should put some problem is simplified. When a need to many SQL statements to complete, might as well take the task decomposition. At the same time, it breaks down into some brief business affairs.

If the database a product information table, its record number two million. Now in a management needs, the one-time change one of the one million five hundred thousand record. If through a change affairs, the time is long. If it involves cascade update it, is time the meeting is longer.

In view of this situation, we can learn affairs brief words. If the product information, may have a product type field. So in the update data, can we not one-time updates. But through the product category fields to control, to record the iteration points. So every category of update firm consumption of time may be greatly reduces. So although operation, will need more steps. But, can effectively avoid to go to the occurrence of congestion, and improve the performance of the database. Suggest four: child inquires the and list box, had better not use at the same time.

Sometimes in the application of design, through the list box can really improve user input speed and accuracy, but, if foreground application does not have buffer mechanism, you often can cause congestion.

As in a order management system, may need frequent input sales representatives. In order to user input convenience, sales representative often design into a list box. Every time need to input, foreground application from the background of all sales representative inquires information (if the application is not involved in the cache). On one hand, the son of nature, would be speed query slow; Second, the list box have growth time operation of the inquiry. The two parties face touch together, may cause

the application of improving the running time process query. And the other user queries, such as the system administrator need to maintain customer information, and cause congestion.

So, in the application design, the child inquires the best less. And the child inquires the list box and use at the same time, more need to ban. If you can't avoid it, should be in application realize caching mechanism. That way, the applications need to sales representative information, will from application cache made, not every time to check the database.

At the same time, can be in the list box design "to search" function. When there is a change to the user information, such as the system administrator to join a new sales representatives. In no again before inquires, because of their application is achieved in the cache data, so not just updated content. At this time, users will need to run to inquires the function, let the foreground application from a database query information again. This kind of design, can increase the list box and the son of the execution time inquires, effectively avoid congestion.

Suggest five: in the set when cancel inquires back issues.

Foreground application is designed, should allow users to a temporary change in idea, cancel the query. Such as user inquires the all product information, may feel response time is long, hard to bear. At this time, they will think of cancel inquires the. In this case, the application design need to design a cancel inquires the button. The user can in the process of inquires click this button cancel inquires at any time. Meanwhile, in the button affair, need to pay attention to join a rollback command. Let the database server can prompt to records or table to unlock.

At the same time to the best lock or query timeout mechanism. This is largely because, sometimes also can cost a lot inquires user host to a large number of resources, and cause client crash. At this time, to be able to lock the inquires the or overtime mechanisms, namely in inquires after overtime, database server of related objects for automatic unlock. This is also the database administrator need to program developers negotiation of a problem.

In addition, explicit database connection to take control in the concurrent users, is expected to full load next use application to bear ability test, use the link, each inquires to set use inquires and lock exceeds the overtime, these methods can effectively avoid the lock conflict obstruction. When database administrators found that blocking the symptoms, can from these aspect, looking for solutions.

From the above analysis can see, SQL Server database lock is a double-edged sword. The security database data consistency at the same time, they will give the database caused some negative effect. How do these negative influence to the least, is our database administrators task. In application design, follow the advice above, can effectively solve the problems for the lock blockages, improve the performance of the database. Visible, to basically solve congestion problem, need database management personnel and program developers work together.

中文

关于数据库死锁的知识

数据库本身提供了锁管理机制,但是从一方面,数据库客户端应用程序的“傀儡”,这主要是由于客户端到服务器的完全控制获得的锁的能力。客户机在请求在查询的查询处理的方法,往往有直接的控制,所以,如果我们的应用程序设计的不够合理,那么出现的数据库死锁现象就很正常了。

下面列举一些容易出现锁死的应用程序例子:

一、客户端取消查询后没有回滚实务。

大多数应用程序查询通常发生的作业。然而,用户通过前台客户端应用程序的后端数据库查询,有时候会取消询问因为各种原因。如果用户打开窗户口查询之后,因为用户发现反映缓慢崩溃或被迫取消查询。但是,当客户端当取消问道,如果不添加回滚事务声明,然后在这个时候,因为用户只有服务器发送了查询请求,因此,后端数据库中涉及的表,所有已添加L锁。因此,即使用户取消查询之后,所有的事务的锁在将继续。在这一点上,如果其他用户需要检查表或用户打开窗口来输入查询的查询条件,提高系统的响应速度时发生堵塞现象。

二、客户端没有及时取得所有查询的结果.

通常,用户将被发送到服务器的查询后,前台应用程序必须立刻进行提取所有的结果。如果应用程序没有旅行中提取所有的结果,它就会产生问题。只要应用程序没有及时提取所有的结果,锁可能呆在桌子和阻止其他用户。由于应用程序已被提交至服务器将平方语句,应用程序必须提取所有结果。如果应用程序没有遵循原则词(比如因为在那个时候,没有监督配置),不能从根本上解决拥堵。

三、查询执行时间过长。

一些查询将成本的一个相对较长的时间。至于查询设计不合理或查询设计观察和记录,将使查询的执行时间延长。如果有时需要更新用户记录或删除操作,如果队伍参与着它,你会得到很多的锁。这些锁升级看是否最后锁可以阻止其他的查询。

所以通常,不要把长时间运行决策支持搜索和在线事务处理,询问混合在一起。

当数据库满足封锁,通常需要检查应用程序提交的SQL语句本身,并检查和连接管理,所有的结果进行处理和其他相关的应用程序行为。通常,为了避免冲突的拥塞在锁上,作者提出以下的建议。

建议一:完成后提取所有查询结果。

一些应用程序为了提高用户查询的响应速度,将有权选择提取需要记录。“智能”看起来很合理,但是,却会导致更大的浪费。因为没有及时的话查询结果提取、锁不能被释放。当别人查询数据,将发生阻塞的。

因此,笔者建议在应用程序设计、数据库查询记录来提取时间。通过其他手段,如添加查询条件,或后台的查询时,提高查询效率。同时,在应用程序级别设置合理的缓存,也可以是非常显著提高查询效率。

建议二:在事务执行时不要让用户输入内容。

尽管在事务的过程性,能让用户参与,为了提高交互性。但是,我们并不推荐使用数据库管理员倾向于这么做。因为如果用户在事务执行期间输入参数,并将

扩展事务的执行时间。尽管人们变得更聪明,但是响应速度仍然没有电脑,那么快。因此,在实现用户的参与让这个过程中,将扩展事务的等待时间。所以除非有特殊的需求,而不是在应用程序的执行过程中,让用户输入参数。一些事务的执行必须参数,最好事先提供。如果能够通过中的变量参数如需要进去。

建议三:使事务尽可能的简短。

数据库管理员应该放一些问题简单化。当一个需要很多的SQL语句完成,不妨把任务分解。同时,它分解成一些简短的业务事务。

如果数据库产品信息表,它记录编号二百万。现在在一个管理需求,一次性修改其中一个十亿零五十万年的纪录。如果通过改变事务的时间较长。如果涉及到级联更新它,时间会更长。

鉴于这种情况,我们可以学习事务简短的话。如果产品信息,可能有一个产品类型字段。所以在更新数据,我们能不能一次性更新。但通过产品类别字段来控制,来记录迭代点。所以每一类更新公司的消费时间可能会极大地降低。所以,虽然操作,将需要更多的步骤。但是,通常,可以有效地避免拥塞的发生,提高数据库的性能。

建议四:子查询与列表框,最好不要同时使用。

?有时在应用程序设计,通过列表框真的可以改善用户输入的速度和准确性,但是,如果前台应用程序没有缓冲机制,你往往会引起交通拥堵。

在一个订单管理系统,可能需要经常输入销售代表。为了方便用户输入,销售代表经常设计成一个列表框。每次需要输入,前台应用程序从背景的查询将销售代表信息(如果应用程序没有涉及缓存)。一方面,自然的孩子,将查询速度缓慢;第二,列表框有成长时间运行的查询。这两方面联系在一起,可能导致应用程序提高运行的时间过程查询。和其他的用户查询,例如系统管理员需要维护客户信息,充血。

所以,在应用程序设计、孩子提问最好的少。和孩子提问列表框和同时使用,更需要禁止。如果你无法避免,应该在应用程序实现缓存机制。这样,应用程序需要的销售代表的信息,将从应用程序缓存中创造出来的,而不是每次检查数据库。同时,可以在列表框设计“搜索”功能。当有一个变化给用户的信息,如系统管理员加入一个新的销售代表。在没有之前再提问,因为他们的应用程序就能实现缓存数据,所以不仅仅是更新的内容。此时,用户将需要运行查询功能,让前台应用程序从一个数据库查询信息。这种设计,可以增加列表框和儿子的执行时间的查询时,有效地避免拥挤。

建议五:在取消查询时设置回退事务。

?前台应用程序设计,应该允许用户临时改变主意,取消查询。如果用户查询所有产品的信息,可能会觉得响应时间长,难以忍受。在这段时间,他们会想到取消,问。在这种情况下,应用程序设计需要设计一个cancel按钮,问。用户可以查询过程点击该按钮取消浏览。同时,在按钮事件,需要注意加入一个回滚命令。让数据库服务器可以提示来记录或表来解锁。

在同一时间或最好的锁定超时机制查询。这很大程度上是因为,有时需要花费很多的要求用户主机大量的资源,并导致客户端崩溃。这时,就可以锁定超时工作或查询机制,即在后来的要求加班,数据库服务器相关的对象自动解锁。这也是数据库管理员需要规划发展问题的谈判。

此外,显式连接到并发用户控制数据库,负载预计将使用此应用程序来承受能力测试,使用了链接,每个查询和加班锁定设置使用查询加班,等等,该方法可以有

效地避免阻塞锁冲突。当数据库管理员发现,阻断这些症状,能从这些方面,寻找解决方案。

从上面的分析可以看到,SQL Server数据库锁是一把双刃剑。安全数据库数据一致性的同时,也将给数据库也产生了一些负面影响。如何把这些消极影响降到最低,是我们的数据库管理员的任务。在应用程序设计,遵循上面的建议,可以有效地解决这个问题锁堵塞,提高数据库的性能。可见,要从根本上解决拥堵问题,需要数据库管理人员和项目开发人员一起工作。

外文翻译-数据库管理系统—剖析

Database Management System Source:Database and Network Journal Author:David Anderson You know that a data is a collection of logically related data elements that may be structured in various ways to meet the multiple processing and retrieval needs of orga nizations and individuals. There’s nothing new about data base-early ones were chiseled in stone, penned on scrolls, and written on index cards. But now database are commonly recorded on magnetically media, and computer programs are required to perform the necessary storage and retrieval operations. The system software package that handles the difficult tasks associated with created, accessing, and maintaining database records is in a DBMS package establish an interface between the database itself and the users of the database. (These users may be applications programmers, managers and others with information needs, and various OS programmers.) A DBMS can organize, process, and present selected data elements from the database. This capability enables decision makers to search. Probe, and query data contents in order to extract answers to nonrecurring and unplanned questions that aren’t available in regular reports. These questions might initially be vague and/or poorly defined, but people can “browse” through the database until they have the needed information. In short, the DBMS will “manage” the stored data items and assemble the needed items from the common database in response to the queries of those who aren’t programmers. In a file-oriented system, users needing special information may communicate their needs to a programmers, who, when time permits, will information. The availability of a DBMS, however, offers users a much faster alternative communications patch (see figure). Special, direct, and other file processing approaches ate used to organize and structure data in single files. But a DBMS is able to integrate data elements from several files to answer specific user inquiries fir information. This means that the DBMS is able to structure and tie together the logically related data from several large files. Logical structures. Identifying these logical relationships is a job of the data administrator. A data definition language is used for this purpose. The DBMS may

SQL数据库外文翻译--数据库的工作

Working with Databases This chapter describes how to use SQL statements in embedded applications to control databases. There are three database statements that set up and open databases for access: SET DATABASE declares a database handle, associates the handle with an actual database file, and optionally assigns operational parameters for the database. SET NAMES optionally specifies the character set a client application uses for CHAR, VARCHAR, and text Blob data. The server uses this information to transli terate from a database?s default character set to the client?s character set on SELECT operations, and to transliterate from a client application?s character set to the database character set on INSERT and UPDATE operations. g CONNECT opens a database, allocates system resources for it, and optionally assigns operational parameters for the database.All databases must be closed before a program ends. A database can be closed by using DISCONNECT, or by appending the RELEASE option to the final COMMIT or ROLLBACK in a program. Declaring a database Before a database can be opened and used in a program, it must first be declared with SET DATABASE to: CHAPTER 3 WORKING WITH DATABASES. Establish a database handle. Associate the database handle with a database file stored on a local or remote node.A database handle is a unique, abbreviated alias for an actual database name. Database handles are used in subsequent CONNECT, COMMIT RELEASE, and ROLLBACK RELEASE statements to specify which databases they should affect. Except in dynamic SQL (DSQL) applications, database handles can also be used inside transaction blocks to qualify, or differentiate, table names when two or more open databases contain identically named tables. Each database handle must be unique among all variables used in a program. Database handles cannot duplicate host-language reserved words, and cannot be InterBase reserved words.The following statement illustrates a simple database declaration:

关于现代工业机械手外文文献翻译@中英文翻译@外文翻译

附录 About Modenr Industrial Manipulayor Robot is a type of mechantronics equipment which synthesizes the last research achievement of engine and precision engine, micro-electronics and computer, automation control and drive, sensor and message dispose and artificial intelligence and so on. With the development of economic and the demand for automation control, robot technology is developed quickly and all types of the robots products are come into being. The practicality use of robot not only solves the problems which are difficult to operate for human being, but also advances the industrial automation program. Modern industrial robots are true marvels of engineering. A robot the size of a person can easily carry a load over one hundred pounds and move it very quickly with a repeatability of 0.006inches. Furthermore these robots can do that 24hours a day for years on end with no failures whatsoever. Though they are reprogrammable, in many applications they are programmed once and then repeat that exact same task for years. At present, the research and development of robot involves several kinds of technology and the robot system configuration is so complex that the cost at large is high which to a certain extent limit the robot abroad use. To development economic practicality and high reliability robot system will be value to robot social application and economy development. With he rapid progress with the control economy and expanding of the modern cities, the let of sewage is increasing quickly; with the development of modern technology and the enhancement of consciousness about environment reserve, more and more people realized

管理信息系统外文翻译

管理信息系统外文翻译-标准化文件发布号:(9456-EUATWK-MWUB-WUNN-INNUL-DDQTY-KII

英文文献翻译 二〇年月日

科技文章摘译 Definition of a Management Information System There is no consensus of the definition of the term "management information system". Some writers prefer alternative terminology such as "information processing system", "information and decision system", "organizational information system", or simply "information system" to refer to the computer-based information processing system which supports the operations, management, and decision-making functions of an organization. This text uses “MIS” because it is descriptive and generally understood; it also frequently uses “information system” instead of “MIS” to refer to an organizational information system. A definition of a management information system, as the term is generally understood, is an integrated, user-machine system for providing information to support operations, management, and decision-making functions in an organization. The system utilizes computer hardware and software; manual procedures; models for analysis planning, control and decision making; and a database. The fact that it is an integrated system does not mean that it is a single, monolithic structure; rather, it means that the parts fit into an overall design. The elements of the definition are highlighted below. 1 Computer-based user-machine system Conceptually, management information can exist without computer, but it is the power of the computer which makes MIS feasible. The question is not whether computers should be used in management information system, but the extent to which information use should be computerized. The concept of a user-machine system implies that some tasks are best performed by humans, while others are best done by machine. The user of an MIS is any person responsible for entering input data, instructing the system, or utilizing the information output of the system. For many problems, the user and the computer form a combined system with results obtained through a set of interactions between the computer and the user. User-machine interaction is facilitated by operation in which the user’s input-output device (usually a visual display terminal) is connected to the computer. The computer can be a personal computer serving only one user or a large computer that

企业数据建模外文翻译文献

企业数据建模外文翻译文献 (文档含中英文对照即英文原文和中文翻译) 翻译: 信息系统开发和数据库开发 在许多组织中,数据库开发是从企业数据建模开始的,企业数据建模确定了组织数据库的范围和一般内容。这一步骤通常发生在一个组织进行信息系统规划的过程中,它的目的是为组织数据创建一个整体的描述或解释,而不是设计一个特定的数据库。一个特定的数据库为一个或多个信息系统提供数据,而企业数据模型(可能包含许多数据库)描述了由组织维护的数据的范围。在企业数据建模时,你审查当前的系统,分析需要支持的业务领域的本质,描述需要进一步抽象的数据,并且规划一个或多个数据库开发项目。图1显示松谷家具公司的企业数据模型的一个部分。 1.1 信息系统体系结构 如图1所示,高级的数据模型仅仅是总体信息系统体系结构(ISA)一个部分或一个组

织信息系统的蓝图。在信息系统规划期间,你可以建立一个企业数据模型作为整个信息系统体系结构的一部分。根据Zachman(1987)、Sowa和Zachman(1992)的观点,一个信息系统体系结构由以下6个关键部分组成: 数据(如图1所示,但是也有其他的表示方法)。 操纵数据的处理(着系可以用数据流图、带方法的对象模型或者其他符号表示)。 网络,它在组织内并在组织与它的主要业务伙伴之间传输数据(它可以通过网络连接和拓扑图来显示)。 人,人执行处理并且是数据和信息的来源和接收者(人在过程模型中显示为数据的发送者和接收者)。 执行过程的事件和时间点(它们可以用状态转换图和其他的方式来显示)。 事件的原因和数据处理的规则(经常以文本形式显示,但是也存在一些用于规划的图表工具,如决策表)。 1.2 信息工程 信息系统的规划者按照信息系统规划的特定方法开发出信息系统的体系结构。信息工程是一种正式的和流行的方法。信息工程是一种面向数据的创建和维护信息系统的方法。因为信息工程是面向数据的,所以当你开始理解数据库是怎样被标识和定义时,信息工程的一种简洁的解释是非常有帮助的。信息工程遵循自顶向下规划的方法,其中,特定的信息系统从对信息需求的广泛理解中推导出来(例如,我们需要关于顾客、产品、供应商、销售员和加工中心的数据),而不是合并许多详尽的信息请求(如一个订单输入屏幕或按照地域报告的销售汇总)。自顶向下规划可使开发人员更全面地规划信息系统,提供一种考虑系统组件集成的方法,增进对信息系统与业务目标的关系的理解,加深对信息系统在整个组织中的影响的理解。 信息工程包括四个步骤:规划、分析、设计和实现。信息工程的规划阶段产生信息系统体系结构,包括企业数据模型。 1.3 信息系统规划 信息系统规划的目标是使信息技术与组织的业务策略紧密结合,这种结合对于从信息系统和技术的投资中获取最大利益是非常重要的。正如表1所描述的那样,信息工程方法的规划阶段包括3个步骤,我们在后续的3个小节中讨论它们。 1.确定关键性的规划因素

数据库外文参考文献及翻译.

数据库外文参考文献及翻译 数据库外文参考文献及翻译数据库管理系统——实施数据完整性一个数据库,只有用户对它特别有信心的时候。这就是为什么服务器必须实施数据完整性规则和商业政策的原因。执行SQL Server的数据完整性的数据库本身,保证了复杂的业务政策得以遵循,以及强制性数据元素之间的关系得到遵守。因为SQL Server的客户机/服务器体系结构允许你使用各种不同的前端应用程序去操纵和从服务器上呈现同样的数据,这把一切必要的完整性约束,安全权限,业务规则编码成每个应用,是非常繁琐的。如果企业的所有政策都在前端应用程序中被编码,那么各种应用程序都将随着每一次业务的政策的改变而改变。即使您试图把业务规则编码为每个客户端应用程序,其应用程序失常的危险性也将依然存在。大多数应用程序都是不能完全信任的,只有当服务器可以作为最后仲裁者,并且服务器不能为一个很差的书面或恶意程序去破坏其完整性而提供一个后门。SQL Server使用了先进的数据完整性功能,如存储过程,声明引用完整性(DRI),数据类型,限制,规则,默认和触发器来执行数据的完整性。所有这些功能在数据库里都有各自的用途;通过这些完整性功能的结合,可以实现您的数据库的灵活性和易于管理,而且还安全。声明数据完整性声明数据完整原文请找腾讯3249114六,维-论'文.网 https://www.wendangku.net/doc/328395453.html, 定义一个表时指定构成的主键的列。这就是所谓的主键约束。SQL Server使用主键约束以保证所有值的唯一性在指定的列从未侵犯。通过确保这个表有一个主键来实现这个表的实体完整性。有时,在一个表中一个以上的列(或列的组合)可以唯一标志一行,例如,雇员表可能有员工编号( emp_id )列和社会安全号码( soc_sec_num )列,两者的值都被认为是唯一的。这种列经常被称为替代键或候选键。这些项也必须是唯一的。虽然一个表只能有一个主键,但是它可以有多个候选键。 SQL Server的支持多个候选键概念进入唯一性约束。当一列或列的组合被声明是唯一的, SQL Server 会阻止任何行因为违反这个唯一性而进行的添加或更新操作。在没有故指的或者合适的键存在时,指定一个任意的唯一的数字作为主键,往往是最有效的。例如,企业普遍使用的客户号码或账户号码作为唯一识别码或主键。通过允许一个表中的一个列拥有身份属性,SQL Server可以更容易有效地产生唯一数字。您使用的身份属性可以确保每个列中的值是唯一的,并且值将从你指定的起点开始,以你指定的数量进行递增(或递减)。(拥有特定属性的列通常也有一个主键或唯一约束,但这不是必需的。)第二种类型的数据完整性是参照完整性。 SQL Server实现了表和外键约束之间的逻辑关系。外键是一个表中的列或列的组合,连接着另一个表的主键(或着也可能是替代键)。这两个表之间的逻辑关系是关系模型的基础;参照完整性意味着这种关系是从来没有被违反的。例如,一个包括出版商表和标题表的简单的select例子。在标题表中,列title_id (标题编号)是主键。在出版商表,列pub_id (出版者ID )是主键。 titles表还包括一个pub_id列,这不是主键,因为出版商可以发布多个标题。相反, pub_id是一个外键,它对应着出版商表的主键。如果你在定义表的时候声明了这个关系, SQL Server由双方执行它。首先,它确保标题不能进入titles表,或在titles表中现有的pub_id无法被修改,除非有效的出版商ID作为新pub_id出现在出版商表中。其次,它确保在不考虑titles表中对应值的情况下,出版商表中的pub_id的值不做任何改变。以下两种方法可

人工智能专业外文翻译-机器人

译文资料: 机器人 首先我介绍一下机器人产生的背景,机器人技术的发展,它应该说是一个科学技术发展共同的一个综合性的结果,同时,为社会经济发展产生了一个重大影响的一门科学技术,它的发展归功于在第二次世界大战中各国加强了经济的投入,就加强了本国的经济的发展。另一方面它也是生产力发展的需求的必然结果,也是人类自身发展的必然结果,那么随着人类的发展,人们在不断探讨自然过程中,在认识和改造自然过程中,需要能够解放人的一种奴隶。那么这种奴隶就是代替人们去能够从事复杂和繁重的体力劳动,实现人们对不可达世界的认识和改造,这也是人们在科技发展过程中的一个客观需要。 机器人有三个发展阶段,那么也就是说,我们习惯于把机器人分成三类,一种是第一代机器人,那么也叫示教再现型机器人,它是通过一个计算机,来控制一个多自由度的一个机械,通过示教存储程序和信息,工作时把信息读取出来,然后发出指令,这样的话机器人可以重复的根据人当时示教的结果,再现出这种动作,比方说汽车的点焊机器人,它只要把这个点焊的过程示教完以后,它总是重复这样一种工作,它对于外界的环境没有感知,这个力操作力的大小,这个工件存在不存在,焊的好与坏,它并不知道,那么实际上这种从第一代机器人,也就存在它这种缺陷,因此,在20世纪70年代后期,人们开始研究第二代机器人,叫带感觉的机器人,这种带感觉的机器人是类似人在某种功能的感觉,比如说力觉、触觉、滑觉、视觉、听觉和人进行相类比,有了各种各样的感觉,比方说在机器人抓一个物体的时候,它实际上力的大小能感觉出来,它能够通过视觉,能够去感受和识别它的形状、大小、颜色。抓一个鸡蛋,它能通过一个触觉,知道它的力的大小和滑动的情况。第三代机器人,也是我们机器人学中一个理想的所追求的最高级的阶段,叫智能机器人,那么只要告诉它做什么,不用告诉它怎么去做,它就能完成运动,感知思维和人机通讯的这种功能和机能,那么这个目前的发展还是相对的只是在局部有这种智能的概念和含义,但真正完整意义的这种智能机器人实际上并没有存在,而只是随着我们不断的科学技术的发展,智能的概念越来越丰富,它内涵越来越宽。 下面我简单介绍一下我国机器人发展的基本概况。由于我们国家存在很多其

企业人力资源管理系统分析与设计 外文翻译

Enterprise Human Resources Management System Design And Implementation Abstract: Human resource management system is the core content of modern enterprise management. With the rapid development of the computer information technology and unprecedented prevalence of electronic commerce mode,the competition between enterprises is turning from visible economic markets to the network. Developing the human resource management system supported by computer technology,network technology and information technology can not only improve the skill of human resource management and the efficiency of the enterprises but also make human resource management modern and decision sciencefic,Modern human resource management uses B/S mode to avoid C/S modes short coming of difficult in maintdning and reusing.According to the functional requirements of the actual project,this article specificly state the analysis of system,the general desigin of the system,the detail design of system and the practice of the system. The development of the system is the practice of MVC design ideas, maing using the Jsp+Servlet+JavaBean form of development.Jsp is the practice of MVC design ideas’view,in charge of receiving/responding the request of the customer.Servlet mainly responsible for the core business control of the whole system is the practice of the vontroller of MVC design idea to take charge of the statistics and rules of the whole system. In the practice of the system, somr open-source projrcts,such as the Ajax technique,JfreChart statements,fileupload technology,has been used. Using the modern human resource management theropy and analysising the actual situation, comparing the current situation of human resource management system, a huaman resource contents of management system basied on the Internet/Intranet has been designed. The main management,attendance management training more efficient statistics. Keywords:human resource management; B/S mode; Open-source projects; MVC mode. 摘要 人力资源管理系统是现代企业管理的核心内容。随着计算机信息技术的高速发展,电子商务模式的空前盛行,企业之间的竞争也从有形的经济市场转向了网络。开发以计算机技术、网络技术、信息技术支持的现代人力资源管理系统,既能提高企业人力资源管理的技术含量和企业的办事效率,也能使人力资源管理能够进入现代化、决策科学化的进程。现代人力资源管理系统采用了B/S模式,可以避免C/S模式的重用性差、维护难度高的缺点和

外文文献翻译 An Introduction to Database Management System

英文翻译 数据库管理系统的介绍 Raghu Ramakrishnan 数据库(database,有时被拼作data base)又称为电子数据库,是专门组织起来的一组数据或信息,其目的是为了便于计算机快速查询及检索。数据库的结构是专门设计的,在各种数据处理操作命令的支持下,可以简化数据的存储、检索、修改和删除。数据库可以存储在磁盘、磁带、光盘或其他辅助存储设备上。 数据库由一个或一套文件组成,其中的信息可以分解为记录,每一条记录又包含一个或多个字段(或称为域)。字段是数据存取的基本单位。数据库用于描述实体,其中的一个字段通常表示与实体的某一属性相关的信息。通过关键字以及各种分类(排序)命令,用户可以对多条记录的字段进行查询,重新整理,分组或选择,以实体对某一类数据的检索,也可以生成报表。 所有数据库(除最简单的)中都有复杂的数据关系及其链接。处理与创建,访问以及维护数据库记录有关的复杂任务的系统软件包叫做数据库管理系统(DBMS)。DBMS软件包中的程序在数据库与其用户间建立接口。(这些用户可以是应用程序员,管理员及其他需要信息的人员和各种操作系统程序)DBMS可组织、处理和表示从数据库中选出的数据元。该功能使决策者能搜索、探查和查询数据库的内容,从而对正规报告中没有的,不再出现的且无法预料的问题做出回答。这些问题最初可能是模糊的并且(或者)是定义不恰当的,但是人们可以浏览数据库直到获得所需的信息。简言之,DBMS将“管理”存储的数据项和从公共数据库中汇集所需的数据项用以回答非程序员的询问。 DBMS由3个主要部分组成:(1)存储子系统,用来存储和检索文件中的数据;(2)建模和操作子系统,提供组织数据以及添加、删除、维护、更新数据的方法;(3)用户和DBMS之间的接口。在提高数据库管理系统的价值和有效性方面正在展现以下一些重要发展趋势: 1.管理人员需要最新的信息以做出有效的决策。 2.客户需要越来越复杂的信息服务以及更多的有关其订单,发票和账号的当前信息。

数据库设计外文翻译

外文翻译: 索引 原文来源:Thomas Kyte.Expert Oracle Database Architecture .2nd Edition. 译文正文: 什么情况下使用B*树索引? 我并不盲目地相信“法则”(任何法则都有例外),对于什么时候该用B*索引,我没有经验可以告诉你。为了证明为什么这个方面我无法提供任何经验,下面给出两种等效作法:?使用B*树索引,如果你想通过索引的方式去获得表中所占比例很小的那些行。 ?使用B *树索引,如果你要处理的表和索引许多可以代替表中使用的行。 这些规则似乎提供相互矛盾的意见,但在现实中,他们不是这样的,他们只是涉及两个极为不同的情况。有两种方式使用上述意见给予索引: ?作为获取表中某些行的手段。你将读取索引去获得表中的某一行。在这里你想获得表中所占比例很小的行。 ?作为获取查询结果的手段。这个索引包含足够信息来回复整个查询,我们将不用去查询全表。这个索引将作为该表的一个瘦版本。 还有其他方式—例如,我们使用索引去检索表的所有行,包括那些没有建索引的列。这似乎违背了刚提出的两个规则。这种方式获得将是一个真正的交互式应用程序。该应用中,其中你将获取其中的某些行,并展示它们,等等。你想获取的是针对初始响应时间的查询优化,而不是针对整个查询吞吐量的。 在第一种情况(也就是你想通过索引获得表中一小部分的行)预示着如果你有一个表T (使用与早些时候使用过的相一致的表T),然后你获得一个像这样查询的执行计划: ops$tkyte%ORA11GR2> set autotrace traceonly explain ops$tkyte%ORA11GR2> select owner, status 2 from t 3 where owner = USER; Execution Plan ---------------------------------------------------------- Plan hash value: 1049179052 ------------------------------------------------------------------ | Id | Operation | Name | Rows | Bytes | ------------------------------------------------------------------ | 0 | SELECT STATEMENT | | 2120 | 23320 | | 1 | TABLE ACCESS BY INDEX ROWID |T | 2120 | 23320 | | *2 | INDEX RANGE SCAN | DESC_T_IDX | 8 | | ------------------------------------------------------------------ Predicate Information (identified by operation id): --------------------------------------------------- 2 - access(SYS_OP_DESCEND("OWNER")=SYS_OP_DESCEND(USER@!)) filter(SYS_OP_UNDESCEND(SYS_OP_DESCEND("OWNER"))=USER@!) 你应该访问到该表的一小部分。这个问题在这里看是INDEX (RANGE SCAN) 紧跟在

餐饮管理系统外文翻译文献

餐饮管理系统外文翻译文献(文档含中英文对照即英文原文和中文翻译) 英文: 1、China food industry development prospects analysis The catering industry in China as the tertiary industry is a traditional service industries, experienced reforming and opening starts, quantitative expansion, scale chain development and brand promotion strategy of 4phase, made make a spurt of progress in the development of. At present, the country has4 millions catering outlets. 2005/2006annual Chinese top 100 catering enterprises with total assets of about thirty-two billion yuan, total profit of about six billion yuan, employees about eight hundred thousand people, respectively, over the same period last year increased40.38%,28.84% and33.33% higher than that of the whole society, the catering industry average growth level. China's reform and opening up has gone through ups and downs in the30year, in the30 years of reforming and opening of China's catering industry along with the tide of reform has undergone three leap type development. In the past 30 years, China has experienced from fast food restaurants grabs beach China market to SARS impact, then to food safety ( tonyred event, apple events ), Chinese food and beverage industry in the impact, achieve sales growth.

大学毕业设计仓库管理系统数据库计算机外文参考文献原文及翻译

河北工程大学毕业论文(设计)英文参考文献原文复印件及译文 数据仓库 数据仓库为商务运作提供结构与工具,以便系统地组织、理解和使用数据进行决策。大量组织机构已经发现,在当今这个充满竞争、快速发展的世界,数据仓库是一个有价值的工具。在过去的几年中,许多公司已花费数百万美元,建立企业范围的数据仓库。许多人感到,随着工业竞争的加剧,数据仓库成了必备的最新营销武器——通过更多地了解客户需求而保住客户的途 径。“那么”,你可能会充满神秘地问,“到底什么是数据仓库?” 数据仓库已被多种方式定义,使得很难严格地定义它。宽松地讲,数据仓库是一个数据库,它与组织机构的操作数据库分别维护。数据仓库系统允许将各种应用系统集成在一起,为统一的历史数据分析提供坚实的平台,对信息处理提供支持。 按照W. H. Inmon,一位数据仓库系统构造方面的领头建筑师的说法,“数 (1) 视图。 (2)

般文件和联机事务处理记录,集成在一起。使用数据清理和数据集成技术,确保命名约定、编码结构、属性度量的一致性等。 (3)时变的:数据存储从历史的角度(例如,过去5-10 年)提供信息。数据仓库中的关键结构,隐式或显式地包含时间元素。 (4) 非易失的:数据仓库总是物理地分离存放数据;这些数据源于操作环境下的应用数据。由于这种分离,数据仓库不需要事务处理、恢复和并行控制机制。通常,它只需要两种数据访问:数据的初始化装入和数据访问。 概言之,数据仓库是一种语义上一致的数据存储,它充当决策支持数据模型的物理实现,并存放企业决策所需信息。数据仓库也常常被看作一种体系结构,通过将异种数据源中的数据集成在一起而构造,支持结构化和启发式查询、分析报告和决策制定。 “好”,你现在问,“那么,什么是建立数据仓库?” 根据上面的讨论,我们把建立数据仓库看作构造和使用数据仓库的过程。数据仓库的构造需要数据集成、数据清理、和数据统一。利用数据仓库常常需要一些决策支持技术。这使得“知识工人”(例如,经理、分析人员和主管)能够使用数据仓库,快捷、方便地得到数据的总体视图,根据数据仓库中的信息做出准确的决策。有些作者使用术语“建立数据仓库”表示构造数据仓库的过程,而用术语“仓库DBMS”表示管理和使用数据仓库。我们将不区分二者。 “组织机构如何使用数据仓库中的信息?”许多组织机构正在使用这些信息支持商务决策活动,包括: (1)、增加顾客关注,包括分析顾客购买模式(如,喜爱买什么、购买时间、预算周期、消费习惯); (2)、根据季度、年、地区的营销情况比较,重新配置产品和管理投资,调整生产策略; (3)、分析运作和查找利润源; (4)、管理顾客关系、进行环境调整、管理合股人的资产开销。 从异种数据库集成的角度看,数据仓库也是十分有用的。许多组织收集了形形色色数据,并由多个异种的、自治的、分布的数据源维护大型数据库。集成这些数据,并提供简便、有效的访问是非常希望的,并且也是一种挑战。数据库工业界和研究界都正朝着实现这一目标竭尽全力。 对于异种数据库的集成,传统的数据库做法是:在多个异种数据库上,建立一个包装程序和一个集成程序(或仲裁程序)。这方面的例子包括IBM 的数据连接程序和Informix的数据刀。当一个查询提交客户站点,首先使用元数据字典对查询进行转换,将它转换成相应异种站点上的查询。然后,将这些查询

相关文档
相关文档 最新文档