Using NuoDB 3.0 table index statistics

{question}

Is there anything special that I need to be aware of when I upgrade to NuoDB 3.0?

{question}

{answer}

Yes!  NuoDB 3.0 is our strongest release to date and you should definitely review our release notes by clicking here.  In particular, we've devoted significant attention to automating our table statistics.  

Database query optimizers use table index statistics to help determine the most efficient way to perform a query. As new data is added, removed, and modified within a database, table index statistics eventually become outdated, resulting in less-than-optimal, slower, and inefficient queries. Typically, updating table index statistics is a manual process.

NuoDB 3.0 features table index statistics which are automatically refreshed and updated to reflect changes in the database. When an application loads new data or changes existing data, NuoDB’s table index statistics will be automatically kept up-to-date, allowing the query optimizer to produce the best query results.

However, to take advantage of these improvements, customers will need to upgrade all user indexes by disconnecting all applications from the database and issue the alter table rebuild indexes command for each user table.    We've even provided an index migration utility to upgrade automatically. (Right-click and open GitHub General Utilities for NuoDB in a new tab.)

If you need help with this or if you have questions, feel free to reach out to us.

{answer}

Have more questions? Submit a request

Comments