Hi @michellepace,
From a granularity (and performance) standpoint it’s considered a best practice to split date and time, so option 2. Include a Date- and separate Time dimension table in your model.
You can find an example here in the M code showcase.
Cost of datetime values.
I hope this is helpful