Your SlideShare is downloading. ×
ids.ppt
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

ids.ppt

668
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
668
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • The release of IBM IDS 9.30 demonstrates IBM’s commitment to continue to support and enhance the IDS server. The major contents of this release are: A set of features designed to make IDS even easier to administer and use. This includes a new version of ISA, the Server Administrator tool, Server Studio JE, a Java-based tool for table editing and other application development tasks, and improvements to the UNIX install process. Performance enhancements including support for IBM Informix MaxConnect product which can be used to offload processing from the server so that large user populations can be supported. The Dynamic Log Management feature reduces server hangs caused by long transaction that run out of log space Enhancements to Enterprise Replication for improved performance and increased functionality. Application Development – enhancements to SQL statements, and support for running the EXPLAIN command without executing the SQL statement. Extensibility – improvements to the DataBlade API, and inclusion of a no-cost Spatial DataBlade
  • The UNIX bundle installer simplifies the installation of IDS by allowing you to select which components you wish to install, and then installing them in the correct order. It will create a demo server if requested. It supports a silent install, so that no interaction is required once you have responded to the initial set of questions. Note that the bundle installer must be run by root and the informix group and user must have been defined before the script is run.
  • A new version of the IBM Informix Server Administrator tool is included with IDS 9.30. Enhancements include: Server Setup which greatly simplifies the installation and configuration of a database server, and includes recommendations for the settings for servers that are to be used in different types of environment, such as demo or production. It even implements rules for ONCONFIG settings that have dependencies on other settings. Remote monitoring of all your IDS from one central location, using a browser HDR compatibility checking. HDR requires that both computers (hardware, operating system, and Informix database server version) in an HDR pair be identical and ISA will verify that: Both database servers have transaction logging activated, ISA can contact the candidate secondary server over the network, the ONCONFIG values are identical on the primary and secondary database servers, and the dbspaces and chunks are identical. Displaying the maximum number of simultaneous sessions Editing the SQLHOSTS file
  • Server Studio JE (Java Edition 2.0) is an operating system platform-independent, enterprise-level, visual Integrated Development & Management Environment (IDME) designed to provide - an open architecture - tools deployment platform that serves as the common foundation for integration of current and future development, deployment and management toos across the entire family of Informix database servers. Server Studio JE allows developers to leverage Informix's latest database server technologies and deliver high quality critical line-of-business solutions in record time, while DBAs can effectively manage them with unprecedented ease. It features an easy-to-use graphical interface and includes 3 data management tools in the base product: Database Object Explorer: Is the integrated command and control center and allows you to navigate to all connected database servers. It allows you to examine and understand the structure of the database and examine the properties of any supported object. You can also create, delete and edit supported objects. SQL Editor: Enables you to write, edit and execute both SQL and SPL statements. Table Editor: Supports the creation and editing of tables. It provides access to all table attributes including columns, data types, table and index fragmentation definitions, referential integrity constraints and primary and foreign keys. SSJE is included at no cost with IDS. You will be able to purchase add-on modules directly from AGS Ltd, such as Query Execution Plan Analyzer, SPL Debugger, Object Dependencies Analyzer, etc.
  • The release of IBM IDS 9.30 demonstrates IBM’s commitment to continue to support and enhance the IDS server. The major contents of this release are: A set of features designed to make IDS even easier to administer and use. This includes a new version of ISA, the Server Administrator tool, Server Studio JE, a Java-based tool for table editing and other application development tasks, and improvements to the UNIX install process. Performance enhancements including support for IBM Informix MaxConnect product which can be used to offload processing from the server so that large user populations can be supported. The Dynamic Log Management feature reduces server hangs caused by long transaction that run out of log space Enhancements to Enterprise Replication for improved performance and increased functionality. Application Development – enhancements to SQL statements, and support for running the EXPLAIN command without executing the SQL statement. Extensibility – improvements to the DataBlade API, and inclusion of a no-cost Spatial DataBlade
  • IDS 9.30 supports IBM Informix MaxConnect, a “connection multiplexor”. MaxConnect sits between the database and the clients, and basically concentrates the clients into a more efficient connection that impose a lighter load on the server. Typically, 100 clients are multiplexed into one connection. MaxConnect can run on a middle tier, as shown here, on the same system as the database server, or alongside an application server. Normally, the workload involved in dealing with a number of clients absorbs a lot of the power of the database, leading to high resource utilization and longer response times as more clients sign on. MaxConnect takes over much of this load, which means that database utilization is reduced and response times don’t degrade, even when tens of thousands of users connect. MaxConnect doesn’t necessitate any changes in the client or server software, so it is straightforward to implement, and given that it can be used instead of expensive and disruptive hardware upgrades, it is a very cost-effective solution for high volume, transactional environments. IDS 9.30 will be certified with Baan's high-performance BAAN IVC Level 1 andLevel 2 drivers in the second half of 2001. The addition of the IBM InformixMaxConnect product strengthens IT infrastructure investment, especially forIDS/Baan BAAN customers, by providing reliable connectivity for thousands ofconcurrent database users while maintaining superior performance.
  • Note to Presenter: Backup material is provided for this slide. Dynamic Logging In earlier releases, if the system ran out of log space while processing a long transaction, it would hang. New log files could only be added when the server was in quiescent mode and were added at the beginning of the log list. They could not be accessed until the root dbspace had been archived. In IDS 9.30 a log file can be added on the fly such that it is the next log to be used after the current one, and no archiving is required. The OnConfig parameter DYNAMIC_LOGS allows you to specify whether you want the system to allocate the log automatically, or whether you want it to issue an event alarm and pause the server so that you can allocate the log manually. (For compatibility with existing behavior, you can also set the option to indicate that you don’t want dynamic allocation at all, but it’s unlikely that this option would be chosen.)
  • There is a new onconfig parameter DYNAMIC_LOGS which is used to control the automatic allocation. It is “hidden” – ie, does not appear in the default onconfig file, and the default value is 2, which means that the system will automatically allocate logs if necessary. If you don’t want the default you can add the parameter to the onconfig file. When the system is about to switch from one log file to the next, it checks to see if the next available log file contains information for the oldest active transaction. If it does, it means that the file cannot be overwritten. In this case If the DYNAMIC_LOGs parameter is set to 2 (or is omitted, which means it defaults to 2), the server will add a log automatically or If DYNAMIC_LOGS is set to 1 the server will send an alarm and will stop and will wait until you have added another log file manually. If you have set DYNAMIC_LOGs to 0, the system will behave as it does today.
  • The server always allocates logs in dbspaces, as opposed to file system space such as /tmp. When deciding where to add a log file, the server will favor certain classes of dbspaces over others, according to the criteria shown on this slide. As a rule the server tries to avoid completely filling rootdbs, so it will only allocate files there after all other critical dbspaces (ie those containing logical or physical logs) are full. It cannot allocate log files in BLOB spaces, SmartBLOBspaces or temporary dbspaces. The newly allocated log will always be inserted in the log list directly after the current log file.
  • The server calculates the size of the file it is adding by calculating the midpoint between the size of the smallest and largest active files. The actual size will depend on the amount of contiguous space available but will never be less than 200K.
  • The DBA can now add logs manually without placing the system into quiescent mode. By default logs will be added at the end of the log list, as they were in previous versions, but the new –i parameter allows the DBA to specify that the log be inserted into the log list immediately after the current active log. If the onconfig parameter DYNAMIC_LOGS has been set to 1, the system will not automatically allocate log files, but instead will issue an event alarm and pause the server, to allow the DBA to allocate a log file manually.
  • The release of IBM IDS 9.30 demonstrates IBM’s commitment to continue to support and enhance the IDS server. The major contents of this release are: A set of features designed to make IDS even easier to administer and use. This includes a new version of ISA, the Server Administrator tool, Server Studio JE, a Java-based tool for table editing and other application development tasks, and improvements to the UNIX install process. Performance enhancements including support for IBM Informix MaxConnect product which can be used to offload processing from the server so that large user populations can be supported. The Dynamic Log Management feature reduces server hangs caused by long transaction that run out of log space Enhancements to Enterprise Replication for improved performance and increased functionality. Application Development – enhancements to SQL statements, and support for running the EXPLAIN command without executing the SQL statement. Extensibility – improvements to the DataBlade API, and inclusion of a no-cost Spatial DataBlade
  • Note to Presenter: Backup material is provided for this slide. Significant performance improvements have been made in ER. In the past, multiple parallel replicates had to be defined for a table to get any parallelism on the target. This is no longer necessary. Now the DataSync can generally process ER transactions concurrently in parallel. By placing the stable queue in a smart blob, we reduce the complexity of the queued transaction. Instead of having multiple rows to save the transaction within the stable queue, we now only require a single row. Additionally, it is possible to set up the stable queue so that it is not logged. This reduces the log consumption that is encountered in earlier releases. It is now possible to send only the changed rows for updates. This reduces the amount of data that has to be transmitted and the resources needed to process that data. 9.30 supports the replication of the smart lob types Blobs and Clobs in addition to the current support of Byte and Text large object types. We also support the situation where the source and the target instance has a dissimilar large object types. For instance, the source might be a blob space blob while the target is a smart blob Blob. Callback routines (streamwrite/streamdread) have been added to provide support for UDT replications The sequence of values generated by a serial or serial8 column will be unique on a given server within the enterprise. Thus collisions are avoided. Prior to 9.30, the adding or dropping of CRCOLS to a table required a slow alter. We can now perform this with an in place alter. Replication groups have been replaced by replsets which are logical collections of replicates. This allows replicates to be managed either individually or as part of a set.
  • We ‘buddy bunch’ the DataSync transactions and use buffered logging. By this, we mean that the transmission of the ACK for a DataSync transaction is deferred until we force the logical logs to be flushed. This is necessary to avoid loss of data in the event of a system crash. If we did not coordinate the ACK transmission with the flush of the logical log buffers, then the source system would immediately delete the transaction. If the target were to then crash before the committed transaction had been flushed to disk, the transaction would be lost on the target. However, the source would have received the ACK for that transaction and thus would not resend it when reconnect occurred. By deferring the ACK until the logs are flushed, this problem is avoided. If the target system crashes before the logs are flushed, the source will attempt to resend those transactions when the two servers reconnect. Target parallelism is self regulated by the CDRM_Monitor thread. This routine maintains statistical information about the DataSync. If it appears that we running into an increasing number of collisions, then the degree of parallelism will be throttled. If it appears that there are very few collisions, then the degree of parallelism will be increased. If it appears that the replay position is lagging and a DDRBLOCK state might occur, then the DataSync threads will be blocked so that log consumption will be reduced. Best of all, this feature requires no configuration at all.
  • The common use of serial columns for primary keys creates a major problem for ER sites that want to use update anywhere. We can not guarantee that the number generated for a new insert will be unique on two servers that are in update anywhere mode. This will generally result in collisions with inserts between the two instances, resulting in possible loss of data. This feature simply allows the sequence of values generated by a serial or serial8 column to be unique on a given server within the enterprise. Thus collisions are avoided. Normally with a serial column, the ‘next serial value’ is updated when an insert with a value is done. This will still occur if the insert is not being done by a DataSync thread. However, inserts and updates done by the DataSync thread does not cause the ‘next serial value’ to be updated. This feature is only functional if the table is defined to be a participant in a replicate.
  • Prior to 9.30, the adding or dropping of CRCOLS to a table required a slow alter. With 9.3, we can now perform this with an in place alter.
  • For many reasons, we are not able to support the pre-9.30 replicate group. However, we are able to support the replicate set (replset) which is a superset of the older replicate group. Replsets provide all of the administrative functionality of the replicate group, but has several additional features. For instance, replsets do not have to have the same source/target instances. One type of replset, the exclusive replset, is required to ensure that time based replication does not break referential integrity. While replsets have some functionality of the replicate group, they are not compatible with the replicate group and can not be used until all servers have been migrated to 9.30. Also all replicate groups must be removed from the enterprise prior to migrating to 9.30.
  • Groups were a physical entity. That means that all of the rows within a transaction for member replicates were packaged within a single physical replicate/group buffer. The group functioned as a sort of ‘super replicate’. That meant that replication was done at the group level, not at the replicate level. The replicate lost its identity once it joined a group. It had to have the same set of targets as other members within the group and had to have the same state. For instance, you could not suspend a single member within a group. You could only suspend the entire group. This is not true with the replset. The individual members with the replset retain their identity. They also can have different attributes. They can have different targets. Some can be time-based while others are not. Some can be suspended while others are active. Although replicates could be defined as ‘parallel’, we could only support referential constraints within the context of parallel groups. Therefore, groups were a requirement for pre-9.30 DataSync parallelism. With 9.30 this is handled by other means. Finally since the pre-9.30 group was a physical entity, a replicate could exist in only one group. This is not true with replsets. A replicate can participate in multiple replsets.
  • The release of IBM IDS 9.30 demonstrates IBM’s commitment to continue to support and enhance the IDS server. The major contents of this release are: A set of features designed to make IDS even easier to administer and use. This includes a new version of ISA, the Server Administrator tool, Server Studio JE, a Java-based tool for table editing and other application development tasks, and improvements to the UNIX install process. Performance enhancements including support for IBM Informix MaxConnect product which can be used to offload processing from the server so that large user populations can be supported. The Dynamic Log Management feature reduces server hangs caused by long transaction that run out of log space Enhancements to Enterprise Replication for improved performance and increased functionality. Application Development – enhancements to SQL statements, and support for running the EXPLAIN command without executing the SQL statement. Extensibility – improvements to the DataBlade API, and inclusion of a no-cost Spatial DataBlade
  • You can now EXPLAIN a query without having to execute it – this means you don’t have to run long complex queries to see their access paths. A new environment variable allows you to set the default lock mode for tables created during a session. The FROM word is now optional in the DELETE TABLE statement. New functionality has been added to the REVOKE statement so that a DBA can revoke privileges that were granted by another user. IDS supports XA transactions in a tightly coupled mode, which allows you to use Microsoft Transaction Server (MTS/XA) as a transaction manager. A new onstat option allows you to display the amount of memory used by an SQL statement.
  • The release of IBM IDS 9.30 demonstrates IBM’s commitment to continue to support and enhance the IDS server. The major contents of this release are: A set of features designed to make IDS even easier to administer and use. This includes a new version of ISA, the Server Administrator tool, Server Studio JE, a Java-based tool for table editing and other application development tasks, and improvements to the UNIX install process. Performance enhancements including support for IBM Informix MaxConnect product which can be used to offload processing from the server so that large user populations can be supported. The Dynamic Log Management feature reduces server hangs caused by long transaction that run out of log space Enhancements to Enterprise Replication for improved performance and increased functionality. Application Development – enhancements to SQL statements, and support for running the EXPLAIN command without executing the SQL statement. Extensibility – improvements to the DataBlade API, and inclusion of a no-cost Spatial DataBlade
  • Several changes have been made to the DataBlade API to improve development productivity. These include providing access to files on the client, new callbacks for handling transaction events, and new memory durations The R-tree access method now supports nearest-neighbor queries which allow you to support applications that require data to be ordered by distance from other data. You can set up R-tree indexes that store bounding-box representations of an object in the index leaf pages, rather than the copy of the object, thus saving space and improving build and maintenance performance. Applications can now use temporary smart LOBs for text, image, or other user-defined datatypes that are only required for the duration of the user sessions. These temporary objects can be stored in either a permanent sbspace or a temporary sbspace and neither the meta data nor the user data are logged if they are stored in a temporary sbspace. Space management for Smart Large Objects is now more efficient. When an sbspace is created, the server will reserve 40% of the total area in the chunk. This space will be used for either user data or metadata depending on what’s needed. J/Foundation supports Version 1.3 of the Java Development Kit (JDK) and internally embeds a Java Virtual Machine (JVM). If the platform supports the HotSpot JVM, J/Foundation embeds Hotspot; otherwise it embeds the classic JVM.
  • IDS remains the best choice for customers needing to develop and deliver high-performance Geographically aware applications. The IBM Informix Spatial DataBlade module 8.11, with the R-tree index, enterprise replication, parallel UDRs, and nearest neighbor function, provides the fastest, most robust access to spatial data in the industry. The powerful, patented indexing technology in IDS makes the performance of the resulting products the best in the industry, and is acknowledged by industry leading vendors such as ESRI. New for IDS 9.30 is the nearest-neighbor function, which automatically sorts data, ordered by distance, from any other data.   An example of useful applications would be to quickly identify the three nearest stores to any location, or in the wireless telco arena, the nearest taxicab to a cell phone user. The Informix Spatial DataBlade module 8.11 is a no-cost DataBlade for IBM Informix Dynamic Server 9.30.  This bundle includes the DataBlade itself, a data loader, a java-based data visualization tool, and worldwide sample spatial data. It enables the efficient storage, rapid retrieval, and powerful manipulation of spatial data stored right in the database. The R-tree index enables extremely fast access to spatial data which can be accessed directly through standard SQL, or through third party visualization software. It works seamlessly with industry-leading ESRI GIS client software. Enterprise Replication of spatial data ensures consistency of data across a heterogeneous network of IBM Informix servers. Parallelizable User Defined Functions ensures increased performance of spatial queries. Nearest Neighbor automatically sorts data, ordered by distance, from any other data. This is a huge benefit for the Location-based Services market.
  • IDS Futures Development has begun on the next release of IDS. This release is still in the requirements finalization phase and is targeted to ship in the second half of 2002. Key goals for this release include: Remove scalability limits in the server IBM will include better support for very large disk drives, increase the varchar maximum size to 32k, and improve page use when using varchar and lvarchar data types. Much improved support for multi-rep types is also planned for this release. Simplification of the management of the system Including improvement in the management of dbspaces and the ability to deal with chunks in a more transparent fashion. Improvements in HDR and SmartBlobs functionality is also planned. The removal of the 2GB chunk limit for 64bit systems will also simplify management of the system. The intent is to hide the chunk level interface from the DBA if they do not want to manage at this level. Integrated support for other IBM products Future versions of IBM IDS will include tighter integration and support for other IBM products, including both the WebSphere and Visual Age family of products. At the same time we remain committed to being an open systems vendor and giving customers a choice of tools and application servers by continuing to test and certify with other vendors products. One key way we will meet this goal is by continuing to enhance the key client side API's including ODBC, OLE-DB and JDBC. Additional Features IBM is continuing to evaluate an extensive list of additional features including: new security functions, distributed transactions for UDTs, SQL enhancements, multi-nationalization and others.
  • IDS 9.30 Delivers break-through performance Provides high availability Simplifies administration Provides a base for addressing new business opportunities IDS 9.30 is not just about extensibility. While extensibility is an important capability that enables customers to develop innovative applications to address new business challenges, IDS 9.30 is an evolutionary path for all IDS customers, both 7.x and 9.x, who want to take advantage of the many new OLTP features, including dynamic lock management, dynamic log management, shared statement cacheing, long identifiers, parallel recovery, improvements in enterprise replication, etc etc.
  • Transcript

    • 1. What’s New in 9.30 for 9.x Users Don Pugeau IBM Software Group Data Management Solutions [email_address]
    • 2. Overview
      • Administration and Usability
      • Performance
      • Enterprise Replication
      • Application Development
      • Extensibility
    • 3. Usability – UNIX Bundle Installer
      • Simplifies installation of components
      • Installs components in correct order
      • Creates a demo server if needed
      • Supports role separation
      • Also supports ‘silent’ install
      0) All Products listed below (except JDBC 1.50) 1) Informix Dynamic Server 9.30 2) Informix IConnect 3) Informix JDBC version 1.50 (should not be installed with JDBC 2.20) 4) Informix JDBC version 2.20 5) Informix System Administrator 6) Configure a Demo IDS Server (requires IDS) Enter the number of the products to install, separated by spaces (i.e. "1 2 4"):
    • 4. Usability – ISA 1.40
      • Server Setup
      • Remote monitoring
      • HDR compatibility
      • Connection counts
      • SQLHOSTS edit
    • 5. Usability – Server Studio JE
      • Database Object Explorer
      • SQL Editor
      • Table Editor
      • Other tools are available from AGS, including a stored procedure debugger.
    • 6. Overview
      • Administration and Usability
      • Performance
      • Enterprise Replication
      • Application Development
      • Extensibility
    • 7. Performance - MaxConnect
      • Multiplex database connections
      • NO CHANGE required for existing applications
      • Increase scalability
      • Reduce response times
      SQL Clients MaxConnect IDS
    • 8. Performance – Dynamic Logging
      • Eliminates server hangs due to long transactions
      • New onconfig parameter DYNAMIC_LOGS
        • Server can automatically insert and use a new log file
        • DBA can also add new logs without quiescing the system
      • New logs are usable immediately
        • No need to archive rootdbs
      New log
    • 9. Dynamic Log Allocation
      • New “hidden” onconfig parameter DYNAMIC_LOGS
      • Log will be added automatically when
        • The next active log file contains an open transaction
        • DYNAMIC_LOGS is set to 2 (the default)
      • Message will be logged
    • 10. Configuration Parameters
      • DYNAMIC_LOGS
      • Set to 2 (default) - auto-allocate logs, issue event alarm, pause server if necessary
      • Set to 1 – issue event alarm, pause server if necessary
      • Set to 0 – no alarm, no pause
      • Parameter is ‘hidden’ (does not appear in onconfig file)
    • 11. Configuration Parameters
      • LTXHWM
      • Defaults to 80 if DYNAMIC_LOGS is on
      • Otherwise defaults to 50
      • LTXEHWM
      • Defaults to 90 if DYNAMIC_LOGS is on
      • Otherwise defaults to 60
      • Both parameters are hidden!!
    • 12. Placement of Logs
      • - Where last log was added (since oninit)
      • - Mirrored dbspaces with other logical logs
      • - Non-mirrored dbspaces with other logical logs
      • - Physical log dbspace
      • - ROOTDBS
      • - Other mirrored dbspaces
      • - Other non-mirrored dbspaces
    • 13. Sizes of New Logs
      • Size will be the mid-point of the sizes of the smallest and largest active logs
      • Will take less if contiguous space not available
      • Minimum size is always 200k
    • 14. Adding a Log File Manually
      • New onparams option onparams -a [-d <dbspace>] [-s <size>] [-i]
      • -i indicates log to be inserted after the current log
      • Allows DBA to choose size and placement of log file
    • 15. Dropping Log Files
      • Log files can be dropped when the system is online
      • A “never-used” log file will be dropped immediately
        • Space is available for reuse
      • Used log files are marked “Deleted”
        • Will be dropped after level 0 archive of all permanent dbspaces, BLOBspaces and SmartBLOB spaces
      • If system has never been archived, the new drop restriction isn’t necessary, and is not applied.
      R
    • 16. Overview
      • Administration and Usability
      • Performance
      • Enterprise Replication
      • Application Development
      • Extensibility
    • 17. Enterprise Replication
      • Improved Performance
        • DataSync dynamic parallelism
        • Stable queue management improvements
        • Partial update row support
      • Extended Support
        • SBLOB support
        • Opaque data type support
      • Miscellaneous
        • Support for serial primary keys
        • Inplace alter for CRCOLS
        • Replicate Sets
    • 18. Performance Improvements
      • Automatic target apply parallelism
        • Apply in parallel but commit in order
      • Uses buffered logging where possible
        • Decreases log impact
      • Better stable queue management
        • Uses smart blob for stable queue
      • Self regulation
      • No configuration required
    • 19. Support of Serial Column Primary Key
      • In pre-9.3 we could not use a serial column for a primary key because of insert conflicts
      • Major customer request
      • CDR_SERIAL
        • Provides a unique sequence of numbers generated for a serial column of a replicated table
          • CDR_SERIAL 100,1
            • Sequence 1, 101, 201, 301, 401,…
          • CDR_SERIAL 100,2
            • Sequence 2, 102, 202, 302, 402,…
    • 20. In Place Alter of CRCOLS
      • ER uses shadow columns - cdrserver and cdrtime - to facilitate conflict resolution in update anywhere configurations
      • Prior to 9.30, the table alter required to add (or drop) CRCOLS was a slow operation
      • In 9.30, the same uses the in-place alter mechanism
      • No user action required - it’s implicit.
    • 21. Replsets
      • Replicate groups are no longer supported
      • Provide administrative functionality of replicate groups
      • Needed for time-based replicates of tables having referential integrity
    • 22. Contrasting Replsets and Groups
      • Replsets
        • Logical entity
        • Has no state
        • Does not supercede member replicates
        • Not required for DS parallelism
        • Replicate can exist in multiple replsets
        • Member replicates can have dissimilar attributes
      • Groups
        • Physical entity
        • Had state
        • Superceded member replicates
        • Required for DS parallelism
        • Replicate could exist in only one group
        • Member replicates had to have similar attributes
      R
    • 23. Overview
      • Administration and Usability
      • Performance
      • Enterprise Replication
      • Application Development
      • Extensibility
    • 24. Application Development
      • Explain without Execute
      • Configurable default lock mode DEF_LOCK_MODE
      • Statement memory usage
      • REVOKE ..AS USER
      • DELETE TABLE (no FROM)
      • Support for MTS/XA
        • $ onstat -g stm 8
        • Informix Dynamic Server Version 9.30.xx --On-Line-- 1024 Kbytes
        • session 8 ---------------------------------------------------
        • sdblock heapsz statement ('*' = Open cursor)
        • a97b018 10424 * select * from tb
        • a97b110 8368 insert into tb values (?)
        • a97b208 5120 <SPL statement>
    • 25. Overview
      • Administration and Usability
      • Performance
      • Enterprise Replication
      • Application Development
      • Extensibility
    • 26. Extensibility
      • DataBlade API Enhancements
      • R-Tree Enhancements
        • Nearest neighbor queries
        • Bounding-box only R-tree indexes
      • Smart Large Objects
        • Temporary Smart LOBs
        • Space management improvements
      • J/Foundation
        • Supports JDK 1.3
        • Internally embeds the JVM
    • 27. Spatial DataBlade 8.11
      • Provides
        • R-tree indexing
        • Support for ER
        • Nearest neighbor function
      • Includes
        • A data loader
        • A Java-based visualization tool
        • Worldwide sample spatial data
    • 28. What IDS 9.30 Beta Customers Say...
      • “ What I like most about Informix products and particularly IDS 9.3 is the ease-of-administration, efficiency, and its ability to work well with OLTP... The replication technology in IDS 9.3 improved our transaction processing from 400 to 1200 per second .”
      David Link DBA West Interactive
    • 29. What IDS 9.30 Beta Customers Say (cont’d)
      • “ Informix has always had a reputation as a heavy lifter in the database world... The performance related features of Informix IDS are a DBA’s dream .”
      Jon Lusty DBA Berkley Information Systems
    • 30. Product Roadmap
      • Remove scalability limits
      • Further simplification of manageability
      • Integrated support for other IBM products
      • Maintain openness
      • Other features still under evaluation
    • 31. Summary Smart optimization minimizes tuning overhead Easy overrides when necessary Performance for the Real World Business logic in the database Reliable data replication across a global organization
    • 32. IBM Informix Dynamic Server 9.30 IBM Software Group Data Management Solutions