I'm not clear if there's a way to duplicate the results of a query without re-running it.
I generate a calendar table from a data source's start and end dates and finding the Table.Max and Table.Min takes a long time with 10+ million rows.
I'd like get a copy of the calendar table to reference data tables further down the star schema, but when I choose "Duplicate" on the query it generates the full query code. Is there a way to just copy the finished rows of the calendar table to a new table?
In more detail, the original calendar table references the Purchase Order tables. Purchase Orders in turn relate 1:many to voucher payments. However, we have vouchers created that don't require a PO. So any filter applied to lookup tables that hit the PO data table first screen out the non-PO values.
An alternative to a second calendar table might be a USERELATIONSHIP statement for each of the lookup tables to go against the Voucher table instead of the PO table - if that's true, which one would have the least performance impact?
I generate a calendar table from a data source's start and end dates and finding the Table.Max and Table.Min takes a long time with 10+ million rows.
Code:
MaxDate = Record.Field(Table.Max(ChangedType, SourceDate), SourceDate),
MinDate = Record.Field(Table.Min(ChangedType, SourceDate), SourceDate),
I'd like get a copy of the calendar table to reference data tables further down the star schema, but when I choose "Duplicate" on the query it generates the full query code. Is there a way to just copy the finished rows of the calendar table to a new table?
In more detail, the original calendar table references the Purchase Order tables. Purchase Orders in turn relate 1:many to voucher payments. However, we have vouchers created that don't require a PO. So any filter applied to lookup tables that hit the PO data table first screen out the non-PO values.
An alternative to a second calendar table might be a USERELATIONSHIP statement for each of the lookup tables to go against the Voucher table instead of the PO table - if that's true, which one would have the least performance impact?