Excellent one !

Hi , I don't think so. Vertica is for BI and DWH and not for OLTP Bind variable are not suited for Vertica. Oracle use binds in order to keep the shared pool from exploding. Even in Oracle when you are using it for BI and DWH it's better NOT to use binds ( as long as the number of queries will be re...

If you are using updates a lot then I can tell you that we are suffering from performance issue on our updates ( part of it is our fault as we took Oracle code and use it in Vertica) and we are getting 4 updates/sec on a simple dimension . From my experiences Updates are not performing well in Verti...

Julie wrote:FYI ..


Basically, insert statements suck in Vertica

If you still want to use inserts, we found that separating the inserts on different nodes so that they run in parallel helped with performance.

This is interesting as Updates also sucks ....

Hi , ** your query isn't valid ( where needs to be before the group by ) First try to partition base on the pay_date column or function on this column so it will create daily or monthly partitions and as a result Vertica will use partition pruning and won't scan the entire table . Second create a pr...

As jpcavanaugh wrote you can control the amount of ram wos is using by changing the wosdata resource pool.
You can also change the time of the moveout process so it will move the data from wos to ros more frequently.

Hello, I'd recommend following the upgrade paths as indicated in the docs! In your case, most likely: Vertica 5.0 to 6.0 Vertica 6.0 to 6.1 Each step can be completed in less than 15 minutes each... You may be used to the old back up methods. From the docs: With Release 5.1, Vertica introduced new ...