why does incremental DBD proposes existing projections

I have several new developments, using common master data tables with different fact tables.
Each time I run an incremental DBD for new queries about the new fact tables, I get proposals for projections on the MD tables, and most of the time these projections already exist (same encoding, same column list, same order) !
How comes that Vertica DBD is not able to identify existing similar projections structures in the DB ?
From the doc found on Vertica website "- Incremental—Customers can optionally create additional projections that optimize new queries without disturbing the existing physical design" ... Here it is not really "additional"
I always need to check all the projections to avoid duplication !
Thanks for your support


Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file