If join sources use multiple timelines (per key specified in TIMESTAMP BY OVER clause), join predicate must include condition matching key specified in TIMESTAMP BY OVER clause of both sources. Please add '{0}' to the join predicate.
If an event fails to be written to the output, you have a couple of options. 'Drop' which drops the event that caused the ...
If any of the input sources use TIMESTAMP BY OVER clause, all other input sources must have TIMESTAMP BY OVER clause specifying ...
If events arrive that are outside of the times you chose above, you have a couple of options. Drop deletes the events, and ...
If join sources are partitioned, join predicate must include condition matching partition keys of both sources. Please add ...
If join sources use multiple timelines (per key specified in TIMESTAMP BY OVER clause), join predicate must include condition ...
If TIMESTAMP BY OVER clause is used with partitioned streams, 'PartitionId' must be used as partition key. Please use "PARTITION ...
In an ALTER TABLE REBUILD or ALTER INDEX REBUILD statement, when a partition is specified in a DATA_COMPRESSION clause, PARTITION=ALL ...
Input source with name '{0}' is defined both in the configuration and the 'CREATE TABLE' statement. Please use a single definition. ...
Input source with name '{0}' is used both with and without TIMESTAMP BY clause. Please either remove TIMESTAMP BY clause ...