Hi everyone,
I've noticed that Designer's performance significantly decreases, not with the number of records (ie rows), but with the number of columns (ie Fields)
Anyone got suggestions on how to improve performance or is this inherent problem with Designer?
I am dealing with datasets with about 1,000 columns, and reducing the number of columns is not permissible for business reasons.
Also, rotating the table doesn't work, because the dataset has many more rows than columns.
Thanks!
Side note: I think SQL has similar problems. Microsoft SQL has a hard limit of 1024 columns. MySQL limit is 4,000 but InnoDB further imposes limit of 1,017 columns. I am guessing Designer face similar problems, be great if someone can explain the column limits for Alteryx.