คืนค่าการตั้งค่าทั้งหมด
คุณแน่ใจว่าต้องการคืนค่าการตั้งค่าทั้งหมด ?
ลำดับตอนที่ #3 : Tu130FinalReportformat29012010.doc
TU130 PROJECT FINAL REPORT
Compare Database Manager System
By
1. Ms. Ploypailin Limrahaphan ID 5222770539
2. Ms. Tunchanok Kandee ID 5222770570
3. Mr. Jitudom Tonmanee ID 5222770620
4. Mr. Sakesan Krongphanich ID 5222770661
Under Supervision of
Dr. Boontawee Suntisriyaraporn
Date submitted
2 February 2010
Abstract
A short message (not more than 1 page) summarizing the important points and the results of the project. Although it comes first logistically, always should be written last. It needs to be written last because it is the essence of your report
Objectives
To compare database system bands. To know how different b/w each band and can choose correct band which match to our spec. We will focus on operation system support, limit, data type, security, and partitioning of the system.
Introduction
To understand this project you should acknowledge about following topics:
-data
-database
-database manager system
Briefly describe.
DATA
Database systems are now available on machines all the way from quite small micros ( even portable PCs ) to the largest mainframes. Needless to say, the facilities provided by any given system are to some extent determined by the size and power of the underlying machine. In particular, system on large machines ( “large systems”) tend to be multi-user, whereas those on smaller machines (“ small systems”) tend to be single-user. A single-user system is a system in whish at most one user can access the database at any given time; a multi-user system is a system in which multiple users can access the database concurrently.(the Book,tomtam)
DATABASE
Often abbreviated DB. A collection of information organized in such a way that a computer program can quickly select desired pieces of data. You can think of a database as an electronic filing system.
Traditional databases are organized by fields, records, and files. A field is a single piece of information; a record is one complete set of fields; and a file is a collection of records. For example, a telephone book is analogous to a file. It contains a list of records, each of which consists of three fields: name, address, and telephone number.
To access information from a database, you need a database management system (DBMS).
(http://www.webopedia.com/TERM/d/database.html)
DATABASE (MANAGER) SYSTEM
A database system is basically a computerized record keeping system; that is , it is a computerized system whose overall purpose is to maintain information and to make that information available on demand.* The information concerned can be anything that is deemed to be of significance to the individual or organization the system is intened to serve—anything, in other words, that is needed to assist in the general process of running the business of that individual or organization.
(the Book, tomtam)
Method
To find out the result we have 3 steps in method.
Step1 Survey which DBMS is tops five popular.
Step2 Study basic knowledge of the system
Step3 Compare
And then annualize in part of discussion
STEP1 Survey
Which database system you normally use? (Select 5 Products)
£ DB2 £ MaxDB £ Microsoft Access
£ MySQL £ Oracle £ Microsoft SQL Server
£ RDM Server £ Omnis Studio £ PolyhedraDBMS
£ Superbase £ Teradata £ Valentina
- - - - -
Results of survey are:
- ORAACAL
- MySQL
- Microsoft SQL Sever
- Microsoft Access
-DB2
STEP2 Basic knowledge
ORACAL?
Oracle is the world’s largest enterprise software company. With 136 offices in 57 countries across Europe, Middle East, and
URL: www.oracle.eu
(http://eskills.eun.org/web/guest/partnership_hide?p_p_id=56_INSTANCE_DQkr&_56_INSTANCE_DQkr_articleId=11315)
MySQL?
MySQL is an open source RDBMS that relies on SQL for processing the data in the database. MySQL provides APIs for the languages C, C++, Eiffel, Java, Perl, PHP and Python. In addition, OLE DB and ODBC providers exist for MySQL data connection in the Microsoft environment. A MySQL .NET Native Provider is also available, which allows native MySQL to .NET access without the need for Object Linking and Embedding Database (OLE DB).
MySQL is most commonly used for Web applications and for embedded applications and has become a popular alternative to proprietary database systems because of its speed and reliability. MySQL can run on UNIX, Windows and
MacOS. MySQL is developed, supported and marketed by
(http://www.webopedia.com/TERM/M/MySQL.html)
Microsoft SQL Server?
The code base for MS SQL Server (prior to version 7.0) originated in Sybase SQL Server, and was Microsoft's entry to the enterprise-level database market, competing against Oracle, IBM, and, later, Sybase. Microsoft, Sybase and Ashton-Tate originally teamed up to create and market the first version named SQL Server 1.0 for OS/2 (about 1989) which was essentially the same as Sybase SQL Server 3.0 on Unix, VMS, etc. Microsoft SQL Server 4.2 was shipped around 1992 (available bundled with Microsoft OS/2 version 1.3). Later Microsoft SQL Server 4.21 for Windows NT was released at the same time as Windows NT 3.1. Microsoft SQL Server v6.0 was the first version designed for NT, and did not include any direction from Sybase.
About the time Windows NT was released, Sybase and Microsoft parted ways and each pursued their own design and marketing schemes. Microsoft negotiated exclusive rights to all versions of SQL Server written for Microsoft operating systems. Later, Sybase changed the name of its product to Adaptive Server Enterprise to avoid confusion with Microsoft SQL Server. Until 1994, Microsoft's SQL Server carried three Sybase copyright notices as an indication of its origin.
Since parting ways, several revisions have been done independently. SQL Server 7.0 was a rewrite from the legacy Sybase code. It was succeeded by SQL Server 2000, which was the first edition to be launched in a variant for the IA-64 architecture.
In the eight years since release of Microsoft's previous SQL Server product (SQL Server 2000), advancements have been made in performance, the client IDE tools, and several complementary systems that are packaged with SQL Server 2005. These include: an ETL tool (SQL Server Integration Services or SSIS), a Reporting Server, an OLAP and data mining server (Analysis Services), and several messaging technologies, specifically Service Broker and Notification Services.
SQL Server Release History | |||
Version | Year | Release Name | Codename |
1.0 | 1989 | SQL Server 1.0 | - |
4.21 | 1993 | SQL Server 4.21 | - |
6.0 | 1995 | SQL Server 6.0 | SQL95 |
6.5 | 1996 | SQL Server 6.5 | Hydra |
7.0 | 1998 | SQL Server 7.0 | Sphinx |
- | 1999 | SQL Server 7.0 | Plato |
8.0 | 2000 | SQL Server 2000 | |
8.0 | 2003 | SQL Server 2000 | |
9.0 | 2005 | SQL Server 2005 | |
10.0 | 2008 | SQL Server 2008 | Katmai |
Microsoft Access?
Microsoft Office Access, previously known as Microsoft Access, is a relational database management system from Microsoft that combines the relational Microsoft Jet Database Engine with a graphical user interface and software development tools. It is a member of the Microsoft Office suite of applications and is included in the Professional and higher versions for Office and also sold separately. It can use to build simple applications. (http://en.wikipedia.org/wiki/Microsoft_Access)
DB2?
DB2 is one of the families of relational database management system (RDBMS but also with native XML(Extensible Markup Language)
support) software products within IBM's broader Information Management Software line. Although there are different "editions" and "versions" of DB2, which run on devices ranging from handhelds to mainframes, most often DB2 refers to the DB2 Enterprise Server Edition, which runs on Unix (AIX), Windows, Linux and z/OS servers. DB2 also powers the different IBM InfoSphere Warehouse editions. Alongside DB2 is another RDBMS: Informix, which was acquired by IBM in 2001.
STEP3
Operating system support
The operating systems the RDBMSes(Relational database management system ) can run on.
Yes | No | Yes | Yes | |
Yes | No | No | No | |
Yes | No | No | No | |
Yes | Yes | Yes | Yes | |
Yes | Yes | Yes | Yes |
Partitioning
Information about what partitioning methods are supported natively.
| Range | Hash | Composite (Range+Hash) | List | Shadow | Native Replication API |
Yes | Yes | Yes | Yes | ? | ? | |
No | No | No | No | No | No | |
Yes | Yes | Yes | Yes | ? | ? | |
Yes | Yes | Yes | Yes | ? | ? | |
Yes | No | No | No | ? | ? |
Data types
Products | Decimal | Date/Time | Other | ||||||
Static | TINYINT (8-bit), SMALLINT (16-bit), MEDIUMINT (24-bit), INT (32-bit), BIGINT (64-bit) | FLOAT (32-bit), DOUBLE (aka REAL) (64-bit) | DECIMAL | CHAR, VARCHAR, TEXT | BLOB | DATETIME, DATE, TIMESTAMP, YEAR | BOOLEAN (aka BOOL) = synonym for TINYINT | ENUM, SET | |
Oracle | Static + Dynamic (through ANYDATA) | NUMBER | BINARY_FLOAT, BINARY_DOUBLE | NUMBER | CHAR, VARCHAR2, CLOB, NCLOB, NVARCHAR2, NCHAR | BLOB, RAW, LONGRAW, BFILE | DATE, TIMESTAMP (with/without TIMEZONE), INTERVAL | N/A | SPATIAL, IMAGE, AUDIO, VIDEO, DICOM, XMLType |
Static | INTEGER8 (8-bit), INTEGER(16-bit), INTEGER (32-bit) | FLOAT32 (32-bit), FLOAT (aka REAL; 64-bit) | N/A | VARCHAR, LARGE VARCHAR (aka CHARACTER LARGE OBJECT) | LARGE BINARY (aka BINARY LARGE OBJECT) | DATETIME | BOOLEAN | N/A | |
Static | TINYINT, SMALLINT, INT, BIGINT | FLOAT, REAL | NUMERIC, DECIMAL, SMALLMONEY, MONEY | CHAR, VARCHAR, TEXT, NCHAR, NVARCHAR, NTEXT | BINARY, VARBINARY, IMAGE, FILESTREAM | DATE, DATETIMEOFFSET, DATETIME2, SMALLDATETIME, DATETIME, TIME | BIT | CURSOR, TIMESTAMP, HIERARCHYID, UNIQUEIDENTIFIER, SQL_VARIANT, XML, TABLE |
In programming, classification of a particular type of information. It is easy for humans to distinguish between different types of data. We can usually tell at a glance whether a number is a percentage, a time, or an amount of money. We do this through special symbols -- %, :, and $ -- that indicate the data's type. Similarly, a computer uses special internal codes to keep track of the different types of data it processes.
Most programming languages require the programmer to declare the data type of every data object, and most database systems require the user to specify the type of each data field. The available data types vary from one programming language to another, and from one database application to another, but the following usually exist in one form or another:
integer : In more common parlance, whole number; a number that has no fractional part.
floating-point : A number with a decimal point. For example, 3 is an integer, but 3.5 is a floating-point number.
character (text,char ): Readable text
Static?
Static typing usually results in compiled code that executes more quickly. When the compiler knows the exact data types that are in use, it can produce optimized machine code. Further, compilers for statically typed languages can find assembler shortcuts more easily. Some dynamically typed languages such as Common Lisp allow optional type declarations for optimization for this very reason.
Dynamic?
Dynamic typing allows constructs that some static type checking would reject as illegal. For example, eval functions, which execute arbitrary data as code, become possible (however, the typing within that evaluated code might remain static). Furthermore, dynamic typing better accommodates transitional code and prototyping, such as allowing a placeholder data structure (mock object) to be transparently used in place of a full-fledged data structure (usually for the purposes of experimentation and testing). Recent enhancements to statically typed languages (e.g. Haskell Generalized algebraic data types) have allowed eval functions to be written in a statically type checked way.
(http://en.wikipedia.org/wiki/Type_system#cite_note-2)
whole number. The following are integers:
0, 1, -125, 144457
In contrast, the following are not integers:
5.34, -1.0, 1.3E4, "string"
The first three are floating-point numbers; the last is a character string.
Integers, floating-point numbers, and character strings constitute the basic data types that most computers support. There are often different sizes of integers available; for example, PCs support short integers, which are 2 bytes, and long integers, which are 4 bytes.
(http://www.webopedia.com/TERM/I/integer.html)
A real number (that is, a number that can contain a fractional part). The following are floating-point numbers:
3.0, -111.5, ½, 3E-5
The last example is a computer shorthand for scientific notation. It means 3*10-5 (or 10 to the negative 5th power multiplied by 3).
The term floating point is derived from the fact that there is no fixed number of digits before and after the decimal point; that is, the decimal point can float. There are also representations in which the number of digits before and after the decimal point is set, called fixed-point representations. In general, floating-point representations are slower and less accurate than fixed-point representations, but they can handle a larger range of numbers.
Note that most floating-point numbers a computer can represent are just approximations. One of the challenges in programming with floating-point values is ensuring that the approximations lead to reasonable results. If the programmer is not careful, small discrepancies in the approximations can snowball to the point where the final results become meaningless.
Because mathematics with floating-point numbers requires a great deal of computing power, many microprocessors come with a chip, called a floating point unit (FPU ), specialized for performing floating-point arithmetic. FPUs are also called math coprocessors and numeric coprocessors. (http://www.webopedia.com/TERM/F/floating_point_number.html)
Limits
Information about data size limits.
Products | Max DB size | Max table size | Max row size | Max columns per row | Max Blob/Clob size | Max CHAR size | Max NUMBER size | Min DATE value | Max DATE value | Max column name size |
512 TB (512 TiB) | 512 TB | 32,677 B | 1012 | 2 GB | 32 KB (32 KiB) | 64 bits | 0001 | 9999 | 128 | |
2 GB | 2 GB | 16 MB | 255 | 64 KB (memo field), 1 GB ("OLE Object" field) | 255 B (text field) | 32 bits | 0100 | |||
524,258 TB (32,767 files * 16 TB max file size) | 524,258 TB | Unlimited | 30000 | 2 GB | 2 GB 6 | 126 bits 2 | 0001 | |||
MySQL 5 | Unlimited | MyISAM storage limits: 256TB; Innodb storage limits: 64TB | 64 KB 3 | 4096 4 | 4 GB (longtext, longblob) | 64 KB (text) | 64 bits | 1000 | ||
Unlimited (4 GB * block size per tablespace) | 4 GB * block size (with BIGFILE tablespace) | 8KB | 1000 | Unlimited | 4000 B | 126 bits | -4712 |
Access Control
Information about access control functionalities (work in progress).
ProductS | Native network encryption | Brute-force protection | Password complexity rules 2 | Patch access 3 | Run unprivileged | Audit | Resource limit | Separation of duties | Security Certification | |
Yes | ? | Yes (LDAP, Kerberos, ...) | Yes | ? | Yes | Yes | Yes | Yes | Yes (EAL4+ 6) | |
Yes (SSL with 4.0) | No | No | No | partial (no security page)[16] | Yes | ? | ? | ? 8 | No | |
Yes | ? | Yes (Microsoft Active Directory) | Yes | Yes | Yes | Yes (From 2008) | Yes | Yes | Yes (EAL1+ 1) | |
Yes | Yes | Yes | Yes | ? | ? | Yes | Yes | ? | Yes (EAL4+ 1) |
***(between administrator, operator, backup, ... like RBAC)
Result and Discussion
Report the result of the project and discuss the significant of the results.
Conclusion
Summarizing the key findings of the report. Explain the limitation and address the major issues of the project.
Recommendations (Optional)
Suggest future actions that may help solve the problems or improve the result of the report.
References
List the sources referred to in the report. Make sure all the references are listed in the right format.
Appendices
Appendices contain information that is too complicated or too much detail to include in the report. If you conduct a survey, include a sample of your survey sheet here.
Different Computer type different operation system
Workload
This is optional. If all the members in your group have done equivalent amount of work, then this is not necessary. However, should one or more members have not participated much in the project, you may report the percentage of the workload. See example below.
Name | Student ID | Percentage of Workload |
Ms. Ploypailin Limrahaphan | 5222770539 | |
Ms. Tunchanok Kandee | 5222770570 | |
Mr. Jitudom Tonmanee | 5222770620 | |
Mr. Sakesan Krongphanich | 5222770661 |
ความคิดเห็น