Critical Dates

September 7, 2016 Call For Presentations is closed
October 21, 2016 Abstracts due to IDUG. IDUG will confirm receipt of your abstract(s) submission(s) via e-mail.
Middle of December 2016 Speakers will be selected and notified via e-mail/telephone.
February 24, 2017 Draft presentation due to IDUG
March 31, 2017 Final presentation due to IDUG

Presentation Requirements

IDUG is soliciting presentation abstracts that explore into details of implementation, migrating to a new release, or maximizing performance from any member of the DB2 product family. In recognition of the complex requirements of today’s database implementations, presentation abstracts relating to migration from Oracle to DB2, upgrading within versions of DB2, and new hardware implementations are also being requested. Presentations may cover details of DB2 tools, Big Data and other ancillary DB2 products.

All presentations must be strongly technical in nature, cannot contain marketing themes, and must support and strengthen the information services community by providing the highest quality education and services designed to promote the effective utilization of the DB2 and its family of products.

Please note that each speaker is being asked to moderate at least one session while at the conference. By filling in all of the moderator slots, this will free up the volunteer committee members to deal with other conference needs. Your participation in this activity is greatly appreciated.

Presentation Topics

The Conference Planning Committee strives to achieve a balanced conference program of business solutions relevant to today’s IT environment and usage of DB2 on one or more platforms (e.g., Windows, Linux, UNIX, z/OS). Presentation topics include:


  • Application Solutions
  • Tips and Tricks
  • Best Practices
  • Tuning
  • Native UDFs and Stored Procedures
  • Triggers
  • Intermediate and Advanced SQL

Programming Topics:

  • Java using ORM
  • C/C++
  • Cobol
  • Dynamic vs Static SQL


  • How DB2 security supports data breach prevention, detection, and resolution
  • How the security landscape has changed
  • New security functions and capabilities
  • Other security tools such as Guardium

Creative methods for:

  • Managing database resources
  • Using ancillary DB2 tools and utilities

System management experience with:

  • Performance or availability
  • Migration from a competitor DBMS to DB2
  • Migration to a new release of DBMS (DB2)
  • Technology changes impacting DB2 - Operating System, Storage, etc.

Database administration experiences with:

  •  Distributed, e-business and web applications
  •  Packaged applications (e.g. SAP)
  •  New releases and features of DBMS (DB2)
  •  Federation and Replication 
  •  Oracle/SQLServer competitive topics
  •  Audit Tools
  •  Different DB format: Row based databases vs. Columnar databases

Business Intelligence/Data Warehousing

  • Business Intelligence Solutions ( e.g., Cognos )
  • Business Objects / Cognos sessions that deliver solutions on DB2 as backend engine
  • Data Warehouse / ETL Solutions ( e.g., Datastage )
  • SAP on BI/DW area
  • Predictive Analytics (e.g., SPSS scoring adapter)

Big Data

  • BigSQL, BigR 
  • Spark (including SparkSQL and SparkR)
  • GreenPlum/Netezza competitive topics
  •  DB2 z/OS, LUW and Appliances
  •  iSAS, D/W Accelerators for z/OS

 Data Architecture experiences with:

  •  New releases and features of DBMS (DB2)
  •  Distributed, e-business and web applications
  •  Data warehousing and Business intelligence applications

Emerging Technology:

  •  XML/SQL
  • Language R for Analytics
  •  Cloud Computing 
  •  SOA
  •  Open Source topics: Hadoop, HiveQL, SPARK, Cloudera/IBM partnership

 Application Development:

  •  .Net
  •  PHP
  •  Ruby On Rails
  •  Java
  •  Mobile application development
  •  Performance, Stress and QA testing methodologies    

IDUG is also soliciting abstracts for the Education Seminars.  The Education Seminars can be for Full Day or Half Day in length.

Submit your presentation abstract

Abstracts can be submitted via the IDUG Web site using the link at the end of this page. If you do have questions, please contact IDUG at: ''. 

Examples are included below to help you through the process. All presentation abstracts must be received by October 21, 2016 to be considered. Presentations received after October 21, 2016 will not be considered. If you have questions or need more information, please contact IDUG at ''. We will be using your user ID for submitting an abstract. If you do not have an user ID, you can register for a free membership.

If you are unable to login or have difficulty submitting an abstract, please contact IDUG at ''.

General Instructions

You may submit an unlimited number of abstracts. IDUG will accept two-part presentations. If you have a two-part presentation to submit, please select "Double Session" in the Call for Presentations Form. It is very important that you provide ALL of the information requested below when submitting your presentation(s) for review. Failure to provide all requested information might impact whether or not the abstract is accepted.

Presentation Title: Titles must be clear, concise, and 150 characters or less.

Abstract: Provide a concise abstract of your presentation, not exceeding 425 characters.

Example: Performance is a key database requirement. Achieving high performance depends on selecting the right hardware for the job, a physical database design suitable for the hardware, appropriate auxiliary database structures, and correct settings for configuration parameters and register settings. This presentation will cover these various stages of performance tuning. If your presentation is selected, this information will be published on the IDUG Web site and in the Final Program distributed to all conference attendees. (Note: Any abstract of more than 425 characters may be edited.) Some presentations may also be selected as repeat sessions.

Speaker Biography: In 650 characters or less, recap your professional and outside experiences as they pertain to your presentation(s).

Presentation Length: Single Session presentations are 60 minutes in length. Double Sessions are 120 minutes in length.  Seminars can be Full Day or Half Day in length.

Presentation Category: Specify the category of your presentation. Although your presentation may apply to many categories, some of the most popular are:

  • Creative methods for managing database resources
  • Experiences with Big Data
  • Managing performance or availability
  • Experience with migration from competitor RDBMS to DB2.
  • Experiences with data warehousing and business intelligence applications
  • Experiences with distributed, e-business and web applications
  • Experiences with packaged applications (e.g. ERP)
  • Experiences with new releases and features of DBMS
  • Information Integration (e.g. federated access, replication, etc.)
  • Emerging technology (e.g. XML, .NET, SOA, Java, Open Source)
  • Complementary tools and utilities solutions
  • Application development and implementation

Audience Experience Level: Select the single, most relevant audience level to which this presentation is geared: Beginner, Intermediate to Advanced Users or All Users. 

Presentation History: Indicate if this is a new or existing presentation. If it is an existing presentation, please indicate where it has been given and if it contains new and/or updated information.

Permissions and Release: Provide permission to electronically post speaker biography, abstract and five key bullet points on the IDUG Web site and to publish this information in any printed or electronic IDUG conference marketing materials. In addition, IDUG may edit speaker’s abstract, and five key bullet points for consistency, style, and grammar as necessary. Also, provide permissions for IDUG to post your presentation on the Conference Web Proceedings and CD ROM, as well as IDUG Insider.