Splunk DB Connect 2: Is it valid to select a column that is manipulated during the DB query as your rising column?

[JWBailey]

Is it valid to select a column that is manipulated during the DB query as your rising column?

I am working with a SQL DB, and don't have a valid rising column directly in my DB. But I could do some manipulation within the SQL query to create a new column that would work. Is this possible? Or does the rising column need to already exist in the DB for Splunk to use?

For example, pretend my timestamp is not stored in a single column, but each part is in a separate column:
Year = ####
Month = ##
Day = ##
Hour = ##
Minute = ##
Second = ##

Individually none of these would work for a rising column, but if I could merge all of the text into a single field (YYYYMMDDHHMMSS), make sure it is a numeric value, that could be a valid rising column.

Thanks for all the assistance.

[woodcock]

If you use SQL to create the field, then yes, that should work just fine.