DB2 management, tutorials, scripts, coding, programming and tips for database administrators
IBM now provides an option to configure its Db2 version 12 for z/OS and complementary IBM Db2 Analytics Accelerator (IDAA) to permit concurrent transactional processing of operational data with analytics processing of data in the appliance. This new feature, zero-latency HTAP (hybrid transactional analytical processing) provides a patented replication process that propagates native Db2 table changes to the IDAA data store. This then allows BI queries to act on up-to-date data.
The General Data Protection Regulation (GDPR) went into effect worldwide on May 25, 2018. In response, companies throughout the world increased their data security awareness, appointed data protection officers and updated their privacy policies. IT support staff responded with updated data dictionaries, flagging of personal data, encryption at various points (local and cloud storage, network traffic, etc.) and heightened security procedures. However, more work is needed. In this article we focus on what the DBA must do in the near term in order to anticipate and prevent performance and capacity issues.
IBM's Db2 Version 12 for z/OS has many new features that focus on performance and security measures, particularly for mobile and cloud applications. Advances in cryptographic hardware and query accelerator technologies facilitate rapid development of customer-facing applications and the embedding of big data queries in operational systems.
IBM presents version 12 of its flagship database product Db2 as, "The ultimate enterprise database for business-critical transactions and analytics". What does this mean? In this slideshow we dive into the most critical changes in this version of Db2, including improvements for application enablement, DBA functions, on-line transaction performance and query performance.
What elements comprise current day disaster recovery planning, and how are large mainframe and big data applications recovered?
There has always been a need for some IT users to access data from multiple operational systems across the enterprise. In a process called data integration, companies developed a centralized IT solution that presented data from across the enterprise in a single application. However, with the advent of big data applications, there is now too much data across the enterprise to transport and store in a single place. Data integration had to be re-defined in order to access separate data stores in-place with available access in real-time.
Lockwood Lyon explores the aspects of data modelling that are essential during application development in order to make the application data valuable to an organization.
As many enterprise applications mature, the increases in customers, functions, features and transaction rates require scaling up. Adding memory can sometimes be the cheapest and most convenient option. In this article, we review how features in Db2 for z/OS version 12 can use additional real memory to reduce transaction times and more efficiently use CPU and other resources to meet critical application needs.
Version 12 of IBM's Db2 for z/OS (Db2 12 for z/OS) contains many new features and functions for DBAs and application developers. This latest Db2 version emphasizes performance enhancements across a wide variety of areas, including enhanced on-line transaction performance, improved efficiency for analytical query access paths, removal of some size limitations and exploitation of operating system and storage hardware characteristics.
Is DBaaS a possible strategic direction for your company’s IT infrastructure? In order to determine this, there are several issues you must address. This article lists the most common risks that require mitigation before embarking upon delegating all or most of your database storage and management to an outside firm.
Application and database definitions are now spread among multiple firms across multiple platforms. Business rules are implemented in (potentially) many places, and many support staff skills are not under your control. This raises the complexity of the application and increases the risks of failure during application changes, maintenance or upgrades. This article addresses how to measure and maintain the quality of your application when you take advantage of database as a service (DBaaS).
Providers of database as a service (DBaaS) promise to handle database tasks, including hardware acquisition, database management software installation and configuration, database definition, performance tuning, and backup and recovery. While this service can greatly shorten the time-to-market of a new application, there are certain risks inherent in delegating database management to an outside provider. In this article we address the risks, how should they be mitigated and what questions need to be addressed when choosing a DBaaS provider.