Tags » Partitioning

Postgres - Partitioning Tables

Currently we are working on a project which contains a very large Postgres table (Postgres 9.2) with something like 60 million rows. Most queries on this table have become really very slow. 719 more words


Enabling/Disabling Database Options in Enterprise Edition

This is a pure licensing post, but it is really important for DBAs to know how to do it in a correct way, and I hope it will be useful for all of you. 686 more words

Database Options

App makes it easier and faster for surveyors, architects and designers to specify glass thickness

With smartphone and tablet use by construction professionals growing year on year, the Optima Glass Thickness Calculator App continues to make it easier and faster for surveyors, architects and designers to specify glass thickness in partitioning systems. 133 more words

Partitioned views over table partitioning

Today, we’re going to be looking at a kind of poor-mans’s-partitioning, using a view to union records from multiple tables. We’ll also take a look at when you would want this type of solution, some benefits and drawbacks, as well as ways to make things go faster. 1,690 more words


Partition Pruning - a case study .

Partition pruning if achieved can provide very good performance enhancement for sql query .
However sometimes we may think that the pruning happens automatically and will be taken care by Oracle optimizer . 636 more words


Integrating jOOQ with PostgreSQL: Partitioning


jOOQ is a great framework when you want to work with SQL in Java without having too much ORM in your way. At the same time, it can be integrated into many environments as it is offering you support for many database-specific features. 1,395 more words


Reloading fact tables with zero downtime

If you’re working with data warehousing or reporting, you’ll recognize this problem as a recurring headache whenever you’re designing an ETL process for fact tables: If you want to completely reload all the rows of a fact table, you would typically start by emptying (or truncating) the fact table, and then load new data into it. 1,058 more words