DB2 - Database




DB2 Database

IBM Db2 Database is a relational database that delivers advanced data management and analytics capabilities for your transactional workloads. This operational database is designed to deliver high performance, actionable insights, data availability and reliability, and it is supported across Linux, Unix and Windows operating systems. The Db2 database software includes advanced features such as in-memory technology (IBM BLU Acceleration®), advanced management and development tools, storage optimization, workload management, actionable compression and continuous data availability (IBM pureScale®).

Database a family of relational database products offered by IBM. DB2 provides an open database environment that runs on a wide variety of computing platforms. A DB2 database can grow from a small single-user application to a large multi-user system. Using SQL, users can obtain data simultaneously from DB2 and other databases. DB2 includes a range of application development and management tools.

IBM Db2 is one of the largest and most sophisticated enterprise DBMS packages ever created. Db2 is a product of IBM, the company that invented SQL. This topic is the third step in a five topic sequence showing a complete installation, and then utilization, of Db2 for Developers from the very beginning. Please see Install Db2 topic for basic info on Db2.

What is DB2 Database?

The name DB2, or IBM Database 2, was first given to the Database Management System or DBMS in 1983 when IBM released DB2 on its MVS mainframe platform. Initially DB2 was developed for specific platform of IBM. In 1990, it was developed as a Universal Database (UDB) DB2 Server, which can run on any authoritative operating systems such as Linux, UNIX, and Windows.

CreateNavigationProperties − A logical (true/false) that sets whether to generate navigation properties on the returned values (default is true).

NavigationPropertyNameGenerator − A function that is used for the creation of names for navigation properties.

CommandTimeout − A duration which controls how long the server-side query is allowed to run before it is canceled. The default value is ten minutes.

Query − A native SQL query used to retrieve data. If the query produces multiple result sets, only the first will be returned.

HierarchicalNavigation − A logical (true/false) that sets whether to view the tables grouped by their schema names (default is false).

ConnectionTimeout − A duration which controls how long to wait before abandoning an attempt to make a connection to the server. The default value is driver-dependent.

BinaryCodePage − A number for the CCSID (Coded Character Set Identifier) to decode Db2 FOR BIT binary data into character strings. Applies to Implementation = "Microsoft". Set 0 to disable conversion (default). Set 1 to convert based on database encoding. Set other CCSID number to convert to application encoding.

PackageCollection − Specifies a string value for package collection (default is "NULLID") to enable use of shared packages required to process SQL statements. Applies to Implementation = "Microsoft".

If your AEM forms DB2 database begins to run slowly, running the following process on a weekly basis can improve its performance. Start DB2 Control Center, (Windows) Select Start > Programs > IBM DB2 > General Administratison Tools > Control Center. (Linux and UNIX) From a command prompt, type the db2jcc command.

In the DB2 Control Center object tree, click All Databases. Click the database you created for AEM forms and click the Tables folder. Select all the database tables in the contents pane, right-click them and select Run Statistics. Go to Statistics > Index Statistics. Select Collect Statistics For All Indexes, select Collect Statistics For Indexes With Extended Detailed Statistics, and then click OK. A message appears when the process is completed. Close the message.

Physical vs. Logical Database Partitioning

If you install database partitions on different hosts, this is referred to as physical partitioning. The separate partitions together make up one database, allowing you to assign the computing power of more than one host to the database of your SAP BW system. As opposed to physical partitioning, “logical partitioning” refers to a scenario where you have several database partition servers running on the same host. This means that the configuration can contain more database partitions than hosts.