Straight table best practices question

[#1]

I have a table which looks something like this:

MyTable:

LOAD

1 as count,

client_id,

time, // a timestamp

date,

duration, // an interval

request,

status

FROM $(vQVDFile) (qvd);

I want to display this information in a straight table so that the records appear as in a spreadsheet.

Given that we use set analysis to determine the which of the records to display; ie expression=sum({<date={'$(vDateRange)'}>}count)

my questions are this:

1) Is it more efficient to specify the fields as dimensions or as expressions, since either one will work, or does it not matter?

2) If specifying more than one dimension, should I order the dimensions based on the number of possible values one can be, or does it not matter?

Thanks

[rajeshvaswani77 · Accepted solution]

For

1)Your fields have to be dimensions since you are not calculating anything. If you use them as expressions you might miss out some of teh data/

2)No need to order the dimensions, it does not matter.

thanks,

Rajesh Vaswani

[tresesco]

1. I guess it is better to use dimension instead of expression, because while you use expression, it will treat as if the field has been called under Only() function, so there would a call of system function and then the association of qv would work, whereas, dimension would work on association only.

2. If it is a straight table, it should not matter as the association would be same irrespective of ordering.