New answers tagged

1

How they allow a quick query over different time intervals (minutes, hours, days, months, years...)? The trick is not to do it at runtime at all. If you think this is done by standard SQL "select when needed", you err. Data is generally aggregated when coming in, with the aggregated rows written to separate tables as needed (minute, hour etc.). Charts ...


1

How many rows are being aggregated on each SELECT? This should go without saying - ensure you have an index on the datetime column. Depending on what your query is doing you can also try putting a compound index on your datetime and the column you're aggregating to try to only use the index and avoid reading data blocks off the disk. Please post an ...


8

Why are you not getting minimal logging? I have found the Data Loading Performance Guide, which you reference, to be an extremely valuable resource. However, it is also not 100% comprehensive, and I suspect that the grid is complex enough already that the author did not add a column Table Partitioning to break out differences in behavior depending on ...


0

Maybe, instead of creating the new database, restore the real database to a new database and delete the newest, 12-13 month data. Then in your real database delete that data that isn't contained in your just created archive area. If large deletes are a problem, maybe you can just delete 10K or larger sets by way of script to do it. Your partitioning tasks ...


1

This may be a good candidate for Biml. One approach would be to create a reusable template that would migrate data for a single table in small date ranges with a For Each container. The Biml would loop through your table collection to create identical packages for each qualifying table. Andy Leonard has an intro in his Stairway Series.


0

As with everything else, there are many ways how you can accomplish your high availability deployment. Here I'll suggest something from my experience (my own HA implementation): It is always better to have multiple pgpool2 instances instead of single one. The reason is obvious: single pgpool2 is single point of failure. Since pgpool has introduced watchdog ...



Top 50 recent answers are included