Polytechnic University of the Philippines Open University Quezon City Master of Science in Information Technology Project in Advanced Organization of Database Firebird Database Herminiño C. Lagunzad Firebird Database
Download 312.53 Kb.
|
- Navigate this page:
- Manageability Extensions
- Partition Advisor
- Partitioning Key Extensions
- Virtual Column-Based Partitioning
- Overview of Partitioned Indexes
- Local Partitioned Indexes
- Global Partitioned Indexes
- Global Hash Partitioned Indexes
- Global Non-Partitioned Indexes
- Miscellaneous Information about Creating Indexes on Partitioned Tables
- Partitioned Indexes on Composite Partitions
Partitioning ExtensionsIn addition to the basic partitioning strategies, Oracle Database provides partitioning extensions:
Manageability ExtensionsThese extensions significantly enhance the manageability of partitioned tables:
Interval PartitioningInterval partitioning is an extension of range partitioning which instructs the database to automatically create partitions of a specified interval when data inserted into the table exceeds all of the existing range partitions. You must specify at least one range partition. The range partitioning key value determines the high value of the range partitions, which is called the transition point, and the database creates interval partitions for data beyond that transition point. The lower boundary of every interval partition is the non-inclusive upper boundary of the previous range or interval partition. For example, if you create an interval partitioned table with monthly intervals and the transition point at January 1, 2007, then the lower boundary for the January 2007 interval is January 1, 2007. The lower boundary for the July 2007 interval is July 1, 2007, regardless of whether the June 2007 partition was already created. When using interval partitioning, consider the following restrictions:
You can create single-level interval partitioned tables as well as the following composite partitioned tables:
Partition AdvisorThe Partition Advisor is part of the SQL Access Advisor. The Partition Advisor can recommend a partitioning strategy for a table based on a supplied workload of SQL statements which can be supplied by the SQL Cache, a SQL Tuning set, or be defined by the user. Partitioning Key ExtensionsThese extensions extend the flexibility in defining partitioning keys:
Reference PartitioningReference partitioning allows the partitioning of two tables related to one another by referential constraints. The partitioning key is resolved through an existing parent-child relationship, enforced by enabled and active primary key and foreign key constraints. The benefit of this extension is that tables with a parent-child relationship can be logically equi-partitioned by inheriting the partitioning key from the parent table without duplicating the key columns. The logical dependency will also automatically cascade partition maintenance operations, thus making application development easier and less error-prone. An example of reference partitioning is the Orders and OrderItems tables related to each other by a referential constraintorderid_refconstraint. Namely, OrderItems.OrderID references Orders.OrderID. The Orders table is range partitioned on OrderDate. Reference partitioning on orderid_refconstraint for OrderItems leads to creation of the following partitioned table, which is equi-partitioned with respect to the Orders table, as shown in Figure 2-4 and Figure 2-5. Figure 2-4 Before Reference Partitioning Description of "Figure 2-4 Before Reference Partitioning" Figure 2-5 With Reference Partitioning Virtual column-based Partitioning is supported with all basic partitioning strategies, including interval and interval-* composite partitioning. Overview of Partitioned IndexesJust like partitioned tables, partitioned indexes improve manageability, availability, performance, and scalability. They can either be partitioned independently (global indexes) or automatically linked to a table's partitioning method (local indexes). In general, you should use global indexes for OLTP applications and local indexes for data warehousing or DSS applications. Also, whenever possible, you should try to use local indexes because they are easier to manage. When deciding what kind of partitioned index to use, you should consider the following guidelines in order:
Local Partitioned IndexesLocal partitioned indexes are easier to manage than other types of partitioned indexes. They also offer greater availability and are common in DSS environments. The reason for this is equip partitioning: each partition of a local index is associated with exactly one partition of the table. This enables Oracle to automatically keep the index partitions in sync with the table partitions, and makes each table-index pair independent. Any actions that make one partition's data invalid or unavailable only affect a single partition. Local partitioned indexes support more availability when there are partition or sub partition maintenance operations on the table. A type of index called a local non prefixed index is very useful for historical databases. In this type of index, the partitioning is not on the left prefix of the index columns. You cannot explicitly add a partition to a local index. Instead, new partitions are added to local indexes only when you add a partition to the underlying table. Likewise, you cannot explicitly drop a partition from a local index. Instead, local index partitions are dropped only when you drop a partition from the underlying table. A local index can be unique. However, in order for a local index to be unique, the partitioning key of the table must be part of the index's key columns. Figure 2-6 offers a graphical view of local partitioned indexes. Figure 2-6 Local Partitioned Index Global Range Partitioned IndexesGlobal range partitioned indexes are flexible in that the degree of partitioning and the partitioning key are independent from the table's partitioning method. The highest partition of a global index must have a partition bound, all of whose values are MAXVALUE. This ensures that all rows in the underlying table can be represented in the index. Global prefixed indexes can be unique or non unique. You cannot add a partition to a global index because the highest partition always has a partition bound of MAXVALUE. If you wish to add a new highest partition, use the ALTER INDEX SPLIT PARTITION statement. If a global index partition is empty, you can explicitly drop it by issuing theALTER INDEX DROP PARTITION statement. If a global index partition contains data, dropping the partition causes the next highest partition to be marked unusable. You cannot drop the highest partition in a global index. Global Hash Partitioned IndexesGlobal hash partitioned indexes improve performance by spreading out contention when the index is monotonically growing. In other words, most of the index insertions occur only on the right edge of an index. Maintenance of Global Partitioned IndexesBy default, the following operations on partitions on a heap-organized table mark all global indexes as unusable: ADD (HASH) COALESCE (HASH) DROP EXCHANGE MERGE MOVE SPLIT TRUNCATE These indexes can be maintained by appending the clause UPDATE INDEXES to the SQL statements for the operation. The two advantages to maintaining global indexes:
Note: This feature is supported only for heap-organized tables. Figure 2-7 offers a graphical view of global partitioned indexes. Figure 2-7 Global Partitioned Index Figure 2-8 Global Non-Partitioned Index Global indexes can be unique. Local indexes can only be unique if the partitioning key is a part of the index key. Partitioned Indexes on Composite PartitionsHere are a few points to remember when using partitioned indexes on composite partitions:
Based on the problem cited I have seen a lot of lapses in using the firebird database. So in order to solve those problems the researcher has search for the possible solution to be added to the next version that the firebird will release.
Encryption is one of the security measures that an organization or individual may impose in order to protect sensitive and personal data. When most businesses prefer database software that is equipped with the ways to secure files through encryption process, firebird database must also consider incorporating methods such as encryption of files during data transmission specially most of the financial transaction that are being sent via wired or wireless interface. Visual Basic .NET contains a rich collection of objects and classes that are essential in creating various stand alone or web applications today. It is one of the most preferred tools that many programmers prefer in writing business application because of its user friendly integrated development interface and strong community support for technical queries. With this end firebird database must develop methods and procedures for the integration of its component in the Visual Basic .net environment. The increasing number of android operating system being used in various communication devices such as tablets, smart phones and other handheld devices gives an important note that firebird database must consider developing ways to integrate their database structure into the emerging trend of mobile operating system. Various database software available to the market today imposed a more complex password combination for their databases, this is to further protect the data from any unauthorized access. With this it is important to note that enforcing complexity in the password for the firebird database will not only make the firebird more competitive database but more importantly making it hard for anyone to gain an access to important data. Partitioning is a useful tool that firebird database should consider as many database software supports this feature and enables these databases to be more manageable and flexible in supporting business applications as it allows subdivision of tables and indexes that permit database objects to be managed at a much more greater extent.
Having cited some of the important features lacking in the firebird database the researcher propose some of the improvement on the database software by integrating key features that will further upgrade its database structure and functionality. First is on the issue of data encryption in which firebird database is lacking, since most of the client and business organization today is concern on data security it is essential to consider that methods such us data encryption will be put in placed specially if the data in the database involves sensitive files and records. Next thing to consider is the availability of the firebird database to be integrated to one of the possible options accessible in the database software offered in Microsoft Visual Basic .Net since this programming language is a common tool for today for programmers in writing business and other applications. Another recommendation is the further development in the database structure of the firebird database that will enable it to support common mobile operating system being used in the market today (e.g. Symbian, AmigaOS, IOS, and Android) considering that most individual today makes use of their smart phones to perform different activities such as running any mobile application, browsing the web and ordering services and goods using telecommunication technology. Another important feature that the firebird database software should consider to develop is to strictly impose a more complex password for their databases that further aims to restrict unauthorized access data in the database. And lastly, Firebird database must also adopt the process of partitioning method which is an important strategy to further control the database objects in which modification in the database and application will have a small effect in the changes to be done in its structure and objects and thus promoting a more flexible database structure in which time and expensive application alteration is avoided. Reference: http://redmondmag.com/articles/2013/08/14/password-complexity.aspx http://arstechnica.com/security/2013/06/password-complexity-rules-more-annoying-less-effective-than-length-ones/ http://en.wikipedia.org/wiki/Comparison_of_relational_database_management_systems#ac_7 http://db-engines.com/en/system/Firebird%3BMySQL%3BSQLite http://blog.alertsec.com/2011/05/why-data-encryption-is-important/ http://searchsecurity.techtarget.com/definition/encryption http://www.ico.org.uk/news/blog/2013/why-encryption-is-important-to-data-security http://smartdatacollective.com/onlinetech/135726/encrypting-data-data-breach-prevention http://www.net-security.org/article.php?id=1232&p=6 http://www.techrepublic.com/blog/it-security/the-importance-of-being-encrypted/ http://www.windowsdevcenter.com/pub/a/windows/2005/08/22/whatisVisualStudio.html?page=1 http://www.visionmobile.com/blog/2007/11/the-significance-of-googles-android/ http://giampaolosgura.blogspot.com/2013/03/android-tablet-review.html http://arstechnica.com/security/2013/06/password-complexity-rules-more-annoying-less-effective-than-length-ones/ http://redmondmag.com/articles/2013/08/14/password-complexity.aspx http://docs.oracle.com/cd/B28359_01/server.111/b32024/partition.htm Directory: uploads uploads -> 587 Return function, r i(X) r i(0) r i(1) r i(2) r i(3) 1 0 2 4 6 Thermal Station, I 2 0 1 5 6 3 0 3 5 6 10 uploads -> Department of science and humanities department of mathematics part-a questions and answers uploads -> The Case Against the nypd’s Quota-Driven ‘Broken Windows’ Policing What Is It? uploads -> For want of a nail uploads -> Ownership Models There are two different types of ownership models uploads -> Police Militarization uploads -> City of rising star regular meting thursday, july 14, 2016 uploads -> Township of winfield uploads -> Stop Militarizing Law Enforcement Act of 2014 uploads -> The Black Panther Party’s Ten-Point Program What We Want Now! Download 312.53 Kb. Share with your friends:
|
