Where can you get technical articles that provide an in-depth discussion about a DB2 database solution? How about tutorials to guide users through an unfamiliar feature? The answer is IBM developerWorks. And yes, there are plenty of articles there!
Every month I'll be casting your attention to various technical papers for the DB2 database product. The list will include articles, tutorials and information roadmaps - all extremely useful resources whether you're maintaining a database, planning to use a new feature or developing an application. I'll also bring you interesting podcasts and webcasts about DB2 software to keep you current and up-to-date.
Learn a little or learn a lot - here's you're starting point.
Today's list includes all recent publications on developerWorks.
Since the DB2 Control Center tools have been deprecated in DB2 9.7, users have been encouraged to adopt IBM Data Studio and IBM InfoSphere Optim tools for managing DB2 databases. IBM Data Studio 3.1 was released in October/2011 with several enhancements over previous versions that make it an excellent replacement for Control Center. This article aims to help DB2 users who are familiar with Control Center tools to quickly transition to IBM Data Studio.
Transactional logic that works across heterogeneous databases needs to use global transactions. The IBM Data Server Provider for .NET supports the distributed transaction model from the System.Transactions namespace, which has the capability to create and manage global transactions. The code examples in this article show how to use the IBM Data Server Provider for .NET to create and manage global transactions on the IBM data servers.
The pureXML capabilities of IBM DB2 allow you to store XML natively in a database without modification, while Adobe Flex applications can read XML directly and populate Flex user interfaces. In this three-part article series, you will create a microblogging application that takes advantage of pureXML, Web services, and Adobe Flex; and even allows you to publish your microblogging updates on Twitter.
When executing SQL statements you can run them either using System or SQL Naming. The System Naming conventions follow the traditional methods used on IBM i systems such as library support. The SQL Naming mode on the other hand is defined in the SQL Standard and used by all other databases. When asking what is the difference between SQL and System Naming, you will normally get the answer, schema and object are either separated with a slash or a period. However there are many more differences especially with regard to the access authority and ownership of database objects created either using SQL or System Naming. This article will show the differences between SQL and System Naming primarily focusing on how the ownerships and access authorities vary when creating DB2 for i database objects (such as tables, stored procedures or triggers) with the two naming conventions.
Security administrators are responsible for, among other things, protecting a database against unauthorized access or misuse by authorized database users (for example, inappropriate access to sensitive information within a database). A common requirement to mitigate such risks is ensuring that users are allowed to connect to the database only from a list of trusted hosts -- which are known to be secure. This article gives a practical example of how such a requirement can be put in practice by making use of the trusted context feature of DB2 for Linux, UNIX, and Windows.
Learn some considerations that new software as a service (SaaS) vendors need to take into account when developing applications or modifying existing ones to enable them for multi-tenancy on the cloud. The article discusses the considerations only from a database perspective -- specifically, from an IBM DB2 perspective. Six cases or methods are described.