Connect With Us

Kent Milligan

Kent
Milligan

Kent Milligan is a senior DB2 for i consultant on IBM’s ISV Enablement team for IBM i. Kent spent the first eight years of his IBM career as a member of the DB2 development group in Rochester. He speaks and writes regularly about relational database topics.

Articles
DB2 for i Data Access, Linux Style
DB2 for i Data Access -- Linux Style 
The new IBM Access for Linux ODBC driver not only makes it easy for open-source software to access your DB2 for i databases, but it also delivers improved support for unixODBC, RPM, deb, and more. And it’s free!
Tubocharge IBM i with SQL
Turbocharge IBM i with SQL [Power Pack]
In this SQL Power Pack, four IBM i experts deliver six of our most popular and handy SQL with IBM i articles, plucked from the virtual pages of iProDeveloper.com—unlocked and free to download for a limited time. Act now before they're gone!
DDS to SQL Conversion, Simplified
Simplify DDS to SQL Conversion 
Converting from DDS to SQL just got a little easier. With Technology Refresh 7, IBM has added more support for keyed file objects to its Generate SQL utility. Kent Milligan explains.
Invoke Web Services with SQL
Invoke Web Services with SQL 
With Technology Refresh 6, DB2 for i now supports using SQL to access web services. Kent Milligan gives a simple example to get you started.
Top 6 Mistakes RPGers Make When Switching to SQL
Top 6 Mistakes RPGers Make When Switching to SQL 
Avoid these six blunders by implementing the following SQL best practices and letting DB2 do more of the work for you.
Choose the Right SQL Join Type
A Match Made in SQL  3
SQL's support for multiple join types gives developers more options for merging data sets, but also requires understanding the nuances of each. Kent Milligan shows how the four join types work—and shares some of their pitfalls—so you can get the results you want when combining tables.
Protect Your SQL Routines with Obfuscation 
Many IBM i developers might not know that the source code for their SQL routines is stored in the DB2 for i catalog, leaving this information accessible to clients and other developers. Kent Milligan shares how to use a new DB2 for i technology called obfuscation to protect your intellectual property.
Search Your System with IBM's OmniFind 
It’s easy to index and search IFS and spool file objects with the new IBM OmniFind extension support. Whether you’ve forgotten which spool file has the business data you need or require an application to search and process IFS files, OmniFind is at your disposal.
A Sensible Approach to Multi-Step DB2 for i Query Solutions 
Examine the drawback of temporary tables, then learn how using SQL CTEs can boost DB2 query performance, especially performance of complex SQL queries.
Magic and Myths of SQL ODPs  8
When learning SQL, too many IBM i developers tend to stop after gaining of knowledge of just the language's syntax and become frustrated when their SQL statements or applications don't meet their performance expectations. They usually fall back on DB2's native access because they know better how to apply performance best practices for it. If you're one of these programmers, don't fear. In this article, Kent Milligan will help you deepen your knowledge of SQL performance best practices by focusing on SQL Open Data Paths (ODPs).
Understanding and Exploiting the DB2 Catalog 
The DB2 catalog is one of those sometimes-missed capabilities that can make your job easier. In this article, Kent Milligan takes a closer look at this tool, which gives you a deep set of information about your database objects with the ability to leverage it in multiple ways, including reports and utilities.
Integrating XML with DB2 for i 7.1  1
The DB2 for i 7.1 release includes new features that help developers easily store and process XML as well as generate XML values for new data exchange requirements.
Rev Up XML Searches with IBM OmniFind 
More and more, important businesses data is getting stored in XML. Luckily, IBM offers a free solution to make searching inside of these documents easier.
Auditing and Tracking STRSQL Usage 
The STRSQL (Start SQL Interactive Session) command can bring good news and bad news. The good side of the STRSQL command is that it provides an interface that lets users quickly execute SQL statements. Often STRSQL is used to browse the data in the database and cleanup any data errors that might have been injected by a program bug or user error. The downside? STRSQL can be a bearer of bad news when an auditor reviews your system and wants to see the list of database changes made from the STRSQL interface and who performed them. For most IT departments, STRSQL activity is just a part of running your business--the problem is effectively tracking STRSQL usage. Prior to IBM i 6.1, there were no good solutions. The only real solution was starting a database monitor for all jobs running on the system. This type of database monitor collection will capture all the SQL requests executed from STRSQL. However, this means the monitor will also capture data for every SQL statement running on your system. That's not an acceptable solution for those systems with heavy SQL activity because the DB2 database monitor would generate too much disk activity and consume large amounts of disk storage. DB2 for i 6.1 provides a tailored solution for this problem with the usage of client special registers and database monitor filters. Special registers are not new to SQL--in fact, there's a good chance you already use special registers such as CURRENT DATE or USER. IBM introduced client special registers to enable applications to provide tags (or attributes) to describe the client or application environment that is running SQL statements. In addition, IBM tools such as the database monitor collect the client register values along with the SQL statement text--this makes it very easy to identify which interface or application submitted an SQL statement. Here are the client special registers available in 6.1: CLIENT ACCTNG CLIENT APPLNAME CLIENT PROGRAMID CLIENT USERID CL
Podcast: Define Your Files with SQL Instead of DDS? 
Should you stop defining your physical and logical files with DDS? If so, what are the reasons? DDS has worked brilliantly for decades, so why should you consider fixing something if it isn't broken? In this RPG & DB2 podcast, Skip Marchesani interviews Kent Milligan from IBM Rochester, and tries to get to the bottom of that very subject... Listen to the podcast.
iPro Forums

Get answers to questions, share tips, and engage with the iPro Community in our Forums.

From the Blogs
Application Modernization Redbook Unleashed
Mar 27, 2014
blog

Application Modernization Redbook Unleashed  

The Application Modernization Redbook draft version has been released! Tim Rowe has the details....More
Free-Form RPG Transformation, Part 2
Mar 19, 2014
blog

Free-Form RPG Transformation, Part 2  

Tim Rowe continues his series on ISV tools for free-form RPG with a look at Linoma Software's free-format transformation tool, RPG Toolbox....More

Sponsored Introduction Continue on to (or wait seconds) ×