HP Integrity NonStop BladeSystem
HP Integrity NonStop BladeSystem - Vnug.biz HP Integrity NonStop BladeSystem - Vnug.biz
SQL/MX 2.3.1February 2008, H06.13Feature• Improved compilermemory usage• Enhanced DISPLAYUSE OF• Improved errorhandling of IMPORTtool• Plan Versioning• SET TRANSACTIONAUTOBEGIN OFFFunction• Faster compiles, less memoryusage, handles queries with largernumber of joins• Display source and object filenames plus potentially invalidmodules where table modifiedtimestamp > module creation time• Carry on the import task even whendata errors are encountered• Allows a mixed release networkwithout recompiling applications• Allows implicit transaction to beturned offBenefit• Improved performance• Minimized recompiletime, improvedmanageability• Ease production,improved usability• Ease of migration• Improved usability
SQL/MX Release 2.3.2(target November 2008)Feature• Improved Update Statistics• Support partition name forMODIFY command• Support for No-Wait ESPs(Executor Server Process)• Resultset for Stored JavaProcedures (return Resultset toMXCI, ODBC/MX, JDBC/MXT2 & T4)• New optimization rules• QA enhancementsFunction• Additionally shorten the timetaken to Update Stats• Ability to specify partitionname while modifying table• Start all ESPs in no-waitmode, minimize start-up time• Generates a table of dataupon query execution• Enables SQL/MX optimizer toexplore additional plan forqueries with OR-predicates• Proactively improve codequality, diagnostics, etc…Benefit• Improvedperformance• Improved usability• Improvedperformance• Improvedperformance andusability• Improved planquality• Improved stabilityFuture product plans, dates, and functionality are subject to change without notice.
- Page 5 and 6: Introducing:Integrity NonStop Blade
- Page 7 and 8: Performance increases acrossNonStop
- Page 9 and 10: Enhanced manageability saves time a
- Page 11 and 12: 100% NonStop• Always available•
- Page 13 and 14: Complete investment protection• 1
- Page 15 and 16: FromcurrentsystemProcessor Speedup
- Page 17 and 18: NonStop Blades I/O InfrastructureCl
- Page 19 and 20: Storage CLIM Supported DevicesSASSt
- Page 21 and 22: Future direction
- Page 23 and 24: Industry’s first blades for24/7 c
- Page 25 and 26: SOA and the NonStop server— produ
- Page 27 and 28: Traditional toolset: Java EEEnterpr
- Page 29 and 30: Java programming model on NonStop t
- Page 31 and 32: The SASH stack• Category leaders
- Page 33 and 34: Standard programming model,Differen
- Page 35 and 36: In a nutshell, extending Java envir
- Page 37 and 38: Back-Up Slides
- Page 39 and 40: Slide 38SW1Mike,This end section is
- Page 41 and 42: Solution Pipeline• FSI• OPSOL O
- Page 43 and 44: SoftwareRoadmapOverview
- Page 45 and 46: Application programming models- dev
- Page 47 and 48: Platform infrastructure - enableObj
- Page 49 and 50: S-series Software• Maturing virtu
- Page 51 and 52: NonStop Protection of Software Inve
- Page 53 and 54: NonStop SQLEnhancementsLowest Total
- Page 55: NonStop SQL/MX Roadmap2006200720082
SQL/MX 2.3.1February 2008, H06.13Feature• Improved compilermemory usage• Enhanced DISPLAYUSE OF• Improved errorhandling of IMPORTtool• Plan Versioning• SET TRANSACTIONAUTOBEGIN OFFFunction• Faster compiles, less memoryusage, handles queries with largernumber of joins• Display source and object filenames plus potentially invalidmodules where table modifiedtimestamp > module creation time• Carry on the import task even whendata errors are encountered• Allows a mixed release networkwithout recompiling applications• Allows implicit transaction to beturned offBenefit• Improved performance• Minimized recompiletime, improvedmanageability• Ease production,improved usability• Ease of migration• Improved usability
Change language