The design of the DB2 purescale is based on the DB2 data sharing with parallel sysplex on the main frame platforms.
IBM launched a new DB2 version release in 2009 in the month of October named DB2 purescale which is the cluster database mainly designed for the non-main frame platforms which is mostly suitable for OLTP transactions that is online transaction processing. Microsoft SQL server and oracle database users find it very familiar for using DB2 because of the exhibition of behavior of concurrency model. Many additional functionalities for users working with oracle database were also introduced in DB2 which included PL/ SQL syntax, commonly used syntaxes of SQL, scripting syntax and oracle database’s datatypes. Because of these features one can easily work with XML in environment of data warehousing. Cobra also came up with support of various XML data partitioning techniques like range partitioning, hash partitioning and multidimensional clustering. IBM came up with a new version called cobra in the month of June in 2009 which is the codename for DB2 9.7 for LUW which introduced new features of temporary tables, compression of data for database indexes and storage of objects which are very large.
Db2 data studio tutorial code#
In late 2007 in the month of October IBM came up with another version of DB2 called viper2 for distributed platforms which is code name for DB2 9.5 which brought many advancements in agile XML development, simplification in management and reliability for critical business operations.
Db2 data studio tutorial 64 Bit#
Along with this, it brought many other advanced features like OLTP i.e Online Transactional Processing related improvements, data ware house and business intelligence for z/OS and many other improvements in self managing, exploitation with 64 bit data capability, self-tuning and enhancements in performance of stored procedures. Viper 2 proved to be the first to provide facility to store the relational data natively in XML format. In between 20, IBM introduced a new platform called viper also called DB2 which can run o z/OS and many other distributed systems. SELECT fixpack_num, service_level FROM TABLE (sysproc.env_get_inst_info()) as informationOfInstance To check the version of DB2 on you LUW machine, you can type the following command on the terminal or console: Given below are the various DB2 versions: VersionĬode language used to create this platform is Cobweb.Ĭode language used to create this platform is Stinger.Ĭode language used to create this platform is Viper.Ĭode language used to create this platform is Viper 2.Ĭode language used to create this platform is Cobra.Ĭode language used to create this platform is PureScale.Ĭode language used to create this platform is Galileo.Ĭode language used to create this platform is Kepler.
Again, in the upper right pane, select the desired stored procedure and in the lower pane select the Source option to display the code.In the upper right pane, click in the last icon of the pictorial path to display the list of options, then select Stored Procedures.In the lower right pane, select the Source option to display the code.In the upper right pane, select the desired Stored Procedure.In the left pane of the screen that is displayed, expand the All Databases group and select the appropriate database to expand its objects tree, then select Application Objects, Stored Procedures.To view the code of a stored procedure, perform any of the following options. The Administer Databases activity option displays database objects using a data approach, so they are classified into two main groups: databases and sets. The three activity options are described below. There are three options in IBM Data Studio called Activities from which you can view the code.
Db2 data studio tutorial how to#
This tutorial will show you how to view the code that is contained in a stored procedure in DB2 using IBM Data Studio.
0 kommentar(er)
