Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Sign up nowGet Fabric certified for FREE! Don't miss your chance! Learn more
From what I have read, the PBI Storage engine represents TimeStamp values as a Double. Which means that it does not do any optimized storage (RLE, HashTable, value compression).
We are creating fairly large FactTables, that are index'ed by a Timestamp (We do IOT work, and this is network telementry that has a timestamp and a few other values).
We don't need granularity more than an hour, but by my calculations, even if you go into Seconds since 1900, there is plenty room in a 64 bit integer to store all the days.
No, we don't want to create our own version of TimeStamp. Sounds like a simple feature to test if the value is aligned to a minute or a second, the storage engine could optimize the storage for the value using an 64bit integer.
This is a feature request. Is this a good place to add it?
Solved! Go to Solution.
If this is important to you please consider voting for an existing idea or raising a new one at https://ideas.fabric.microsoft.com/?forum=2d80fd4a-16cb-4189-896b-e0dac5e08b41
If this is important to you please consider voting for an existing idea or raising a new one at https://ideas.fabric.microsoft.com/?forum=2d80fd4a-16cb-4189-896b-e0dac5e08b41
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 62 | |
| 62 | |
| 42 | |
| 21 | |
| 18 |
| User | Count |
|---|---|
| 120 | |
| 105 | |
| 38 | |
| 29 | |
| 28 |