Software Development |
Integration and Application Infrastructure |
Integrating Data and Content |
Collaboration and Human Interaction |
Intelligent Management |
|||
Content Management Information Integration Go to official IBM DB2 site About DB2DB2 is IBM's flagship relational database management system. It has a long history and was what some consider to be the first database product to use SQL. According to Michael Stonebraker, when IBM chose to make SQL the standard for database query languages by announcing its inclusion into DB2.The name DB2 was first given to the Database Management System or DBMS in 1982 where IBM released SQL/DS and DB2 on its mainframe platform. Prior to this the product was named System Relational, or System R, which launched in 1978. DB2 has its roots back to the beginning of the seventies where Dr. E.F. Codd, working for IBM, described the theory of relational databases and in June of 1970 published the model for data manipulation. To apply the model Codd needed a relational database language which he named Structured English QUEry Language or SEQUEL. SEQUEL was already a trademarked name, so IBM renamed the acronym to SQL, short for Structured Query Language. The acronym SQL still stands to this day. Historically, it is interesting to note that when Informix acquired Illustra and made their database engine an object-relational database by introducing their Universal Server, both Oracle and IBM followed suit by changing their database engines to be capable of object-relational extensions. Moreover, in 2001 IBM bought Informix and in the following years incorporated Informix technology into the DB2 product suite. Technically, today, DB2 can be considered to be an object-relational database. Even though DB2 started out on the mainframe it migrated down through UNIX and Windows servers and finally became available on Linux and on PDAs. This process was mainly undertaken though the 1990's. DB2's precursors are IBM DL/1 and IBM IMS, both initially hierarchical and then network (or codasyl) databases. DB2 is also embedded in the operating system of IBM iSeries (formerly the AS/400). DB2 is available in several "editions". Such as the Workgroup, Workgroup Unlimited and Enterprise Server Edition. The top of line edition is called DB2 UDB Data Warehouse Enterprise Edition, or DWE for short. This edition is intended for mixed workload (OLTP and business intelligence) or business intelligence (BI) implementations. DWE includes several BI features such as ETL, data mining, OLAP acceleration and in-line analytics. Currently, there is a dogfight going on between DB2 and Oracle for the number 1 position in the market. On May 3, 2004 IBM's head of database development and sales, Janet Perna, claimed their main competitors were Oracle in the context of advanced transaction handling, and Teradata in the context of decision-making systems (e.g. data warehousing). IBM and DB2 are frequently at or near the top of the TPC-C (OLTP) and TPC-H (data warehousing) industry benchmarks published on the transaction processing council's website. DB2, like Oracle, can be administered from either the command-line or a GUI. The command-line interface requires more knowledge of the product, but can be more easily scripted and automated. The GUI is a multi-platform java client that contains a variety of wizards ideal for novice users. DB2 has API's for .NET CLI, Java, Python, Perl, PHP, C++, C, REXX, PL/1, Cobol, Fortran, and many other programming languages. DB2 also supports integration into the Eclipse and Visual Studio .NET integrated development environments. A Real-time Intrusion Prevention System for Commercial Enterprise DatabasesGo to article by ULF T. MATTSSON Modern intrusion detection systems are comprised of three basically different approaches, host based, network based, and a third relatively recent addition called procedural based detection. The first two have been extremely popular in the commercial market for a number of years now because they are relatively simple to use, understand and maintain. However, they fall prey to a number of shortcomings such as scaling with increased traffic requirements, use of complex and false positive prone signature databases, and their inability to detect novel intrusive attempts. This intrusion detection systems represent a great leap forward over current security technologies by addressing these and other concerns. This paper presents an overview of our work in creating a true database intrusion detection system. Based on many years of Database Security Research, the proposed solution detects a wide range of specific and general forms of misuse, provides detailed reports, and has a low false-alarm rate. Traditional database security mechanisms are very limited in defending successful data attacks. Authorized but malicious transactions can make a database useless by impairing its integrity and availability. The proposed solution offers the ability to detect misuse and subversion through the direct monitoring of database operations inside the database host, providing an important complement to host-based and network-based surveillance. Suites of the proposed solution may be deployed throughout a network, and their alarms managed, correlated, and acted on by remote or local subscribing security services, thus helping to address issues of decentralized management. | |||||||