Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Vote for your favorite vizzies from the Power BI Dataviz World Championship submissions. Vote now!
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
Vote for your favorite vizzies from the Power BI World Championship submissions!
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 58 | |
| 53 | |
| 43 | |
| 17 | |
| 16 |
| User | Count |
|---|---|
| 123 | |
| 108 | |
| 44 | |
| 32 | |
| 24 |