PowerDesigner生成数据库建表sql脚本-Mysql Tutorial-php.cn

Home

Database

Mysql Tutorial

PowerDesigner生成数据库建表sql脚本

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Jun 07, 2016 pm 03:06 PM

powerdesignersqldatabasegenerateScript

一、生成sql server 2000或oracle建表sql脚本
　　
　　1、新建一个物理模型，通过database菜单下的change current dbms可查看当前所用的DBMS是什么类型的，比如sql server 2000 或oracle 10g，当前选择sql server 2000。
　　
　　2、在新建的dbms为sql server 2000的物理模型中添加表及关系，通过database菜单下的generate database可将当前DBMS的表结构及关系导出成sql语句。
　　
　　3、若想将sql server 2000的表结构及关系变成oracl 10g的表结构及关系，可通过Tools菜单下的generate physical data model，再选择DBMS为oracle10g，就可生成oracl10g的表结构及关系。
　　
　　4、若想将oracl10g中的表结构及关系导出成sql语句，执行database菜单下的generate database可将当前DBMS的表结构及关系导出成sql语句。
　　
　　
　　注意：oracle10g生成的sql语句可能表名及字段名存在用引号括起的情况，不用担心，通过简单的设置即可解决。
　　
　　
　　
　　
　　二、PowerDesigner生成数据库建表sql脚本时出现双引号解决方法（测试通过的软件版本为PowerDesigner V15.1.0.2850）
　　
　　 PowerDesigner生成数据库建表SQL脚本时，尤其是Oracle数据库时，表名一般会带引号。其实加引号是PL/SQL的规范，数据库会严格按照“”中的名称建表，如果没有“”，会按照 ORACLE默认的设置建表（DBA STUDIO里面），默认是全部大写，这样，在ORACLE数据库里的字段就如“Column_1”。如果你把引号去掉，ORACLE自动默认为全部大写，即“COLUMN_1”，所以这段SQL在PL/SQL中执行的时候是没有任何问题的，如果不加引号，在PL/SQL会自动识别为大写。如果加了引号，sql或者hql查询“Column_1='XXX'”时，就会报错：ORA-00904: "COLUMN_1": 无效的标识符，除非写为“‘Column_1’='XXX'”。
　　
　　这个问题是生成脚本格式的问题，因此，我们可以尝试在DBMS配置文件中修改相应的格式设置来解决这个问题。选择“DBMS Properties”，选择Script->Sql->Format，有一项CaseSensitivityUsingQuote，它的comment为“Determines if the case sensitivity for identifiers is managed using double quotes”，表示是否适用双引号来规定标识符的大小写，可以看到右边的values默认值为“YES”,改为“No”，点击【应用】按钮。

Statement

The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Explain the role of InnoDB redo logs and undo logs.Apr 15, 2025 am 12:16 AM

InnoDB uses redologs and undologs to ensure data consistency and reliability. 1.redologs record data page modification to ensure crash recovery and transaction persistence. 2.undologs records the original data value and supports transaction rollback and MVCC.

What are the key metrics to look for in an EXPLAIN output (type, key, rows, Extra)?Apr 15, 2025 am 12:15 AM

Key metrics for EXPLAIN commands include type, key, rows, and Extra. 1) The type reflects the access type of the query. The higher the value, the higher the efficiency, such as const is better than ALL. 2) The key displays the index used, and NULL indicates no index. 3) rows estimates the number of scanned rows, affecting query performance. 4) Extra provides additional information, such as Usingfilesort prompts that it needs to be optimized.

What is the Using temporary status in EXPLAIN and how to avoid it?Apr 15, 2025 am 12:14 AM

Usingtemporary indicates that the need to create temporary tables in MySQL queries, which are commonly found in ORDERBY using DISTINCT, GROUPBY, or non-indexed columns. You can avoid the occurrence of indexes and rewrite queries and improve query performance. Specifically, when Usingtemporary appears in EXPLAIN output, it means that MySQL needs to create temporary tables to handle queries. This usually occurs when: 1) deduplication or grouping when using DISTINCT or GROUPBY; 2) sort when ORDERBY contains non-index columns; 3) use complex subquery or join operations. Optimization methods include: 1) ORDERBY and GROUPB

Describe the different SQL transaction isolation levels (Read Uncommitted, Read Committed, Repeatable Read, Serializable) and their implications in MySQL/InnoDB.Apr 15, 2025 am 12:11 AM

MySQL/InnoDB supports four transaction isolation levels: ReadUncommitted, ReadCommitted, RepeatableRead and Serializable. 1.ReadUncommitted allows reading of uncommitted data, which may cause dirty reading. 2. ReadCommitted avoids dirty reading, but non-repeatable reading may occur. 3.RepeatableRead is the default level, avoiding dirty reading and non-repeatable reading, but phantom reading may occur. 4. Serializable avoids all concurrency problems but reduces concurrency. Choosing the appropriate isolation level requires balancing data consistency and performance requirements.

MySQL vs. Other Databases: Comparing the OptionsApr 15, 2025 am 12:08 AM

MySQL is suitable for web applications and content management systems and is popular for its open source, high performance and ease of use. 1) Compared with PostgreSQL, MySQL performs better in simple queries and high concurrent read operations. 2) Compared with Oracle, MySQL is more popular among small and medium-sized enterprises because of its open source and low cost. 3) Compared with Microsoft SQL Server, MySQL is more suitable for cross-platform applications. 4) Unlike MongoDB, MySQL is more suitable for structured data and transaction processing.

How does MySQL index cardinality affect query performance?Apr 14, 2025 am 12:18 AM

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.

MySQL: Resources and Tutorials for New UsersApr 14, 2025 am 12:16 AM

The MySQL learning path includes basic knowledge, core concepts, usage examples, and optimization techniques. 1) Understand basic concepts such as tables, rows, columns, and SQL queries. 2) Learn the definition, working principles and advantages of MySQL. 3) Master basic CRUD operations and advanced usage, such as indexes and stored procedures. 4) Familiar with common error debugging and performance optimization suggestions, such as rational use of indexes and optimization queries. Through these steps, you will have a full grasp of the use and optimization of MySQL.

Real-World MySQL: Examples and Use CasesApr 14, 2025 am 12:15 AM

MySQL's real-world applications include basic database design and complex query optimization. 1) Basic usage: used to store and manage user data, such as inserting, querying, updating and deleting user information. 2) Advanced usage: Handle complex business logic, such as order and inventory management of e-commerce platforms. 3) Performance optimization: Improve performance by rationally using indexes, partition tables and query caches.

See all articles