When designing DB2 databases a frequently heard request is for a column that contains sequentially generated numbers. For example, each row has a counter associated with it. When a new row is inserted, the counter should be incremented by one for the new row. This way, each new DB2 row has a unique “row number” associated with it. Until recently such a design was difficult to deliver.Without sequence objects or identity columns an application program can implement similar functionality, but usually not in a manner that performs adequately as database...
Sunday, 24 September 2006
Friday, 15 September 2006
The Path to an Executable DB2 Program
Posted on 11:41 by Unknown
Here is another Q+A exchange that I thought might be useful to share with everyone here on the blog:QUESTION: Could you please explain the difference between a package and a plan, the process of precompilation, compilation and running a COBOL DB2 program as well as a COBOL CICS DB2 program?ANSWER: Well, I'll hit the highlights in response to your question but if you really want an in-depth answer then you should read the DB2 manuals (or a book like DB2 Developer's Guide).What is a plan? A plan is an executable module containing the access path...
Wednesday, 6 September 2006
Help for SAP Shops Using DB2 for z/OS
Posted on 14:01 by Unknown
Just a quick blog post today to alert folks to a relatively new blog focusing entirely on SAP usage with DB2 for z/OS. According to the blogger, Omer Brandis:Whether you have already implemented SAP on DB2 for z/OS, or are just seriously considering it, this is the blog for you. This blog will deal with real issues from the point of view of a true real-world professional, discussing the good, bad, and ugly of SAP on DB2 for z/OS.Recent posts have covered offsite recovery, reorganizing SAP OFFICE, and hidden REORG jobs. If you use SAP and DB2 on...
Friday, 1 September 2006
The Two Biggest DB2 Performance Things
Posted on 09:00 by Unknown
DB2 performance is one of those perennial topics that people just can't seem to get enough of. I guess that is because the performance of applications is one of the bigger issues that end users complain about. And DBAs can be heroes if they can resolve performance problems quickly. It alos could be that performance problems are so ubiquitous because people keep on making the same design and coding mistakes...With all of that in mind, let's take a look at what I think are the two biggest things you need to get control of to keep DB2 and SQL performance...
Subscribe to:
Posts (Atom)
