Streaming Dataset limitations

[kmas]

Hi all,

I'm creating a data flow between a remote equipment and Power BI (JSON format).

I create streaming dataset option in Power BI  where I define the different fields of these data.

I also switch ON the "Historic data analysis".

Can someone clarify me the data memory limitations for my current scenario? 

I've seen this official info:   

• 75 max columns
• 75 max tables
• 10,000 max rows per single POST rows request
• 1,000,000 rows added per hour per dataset
• 5 max pending POST rows requests per dataset
• 120 POST rows requests per minute per dataset
• If table has 250,000 or more rows, 120 POST rows requests per hour per dataset
• 200,000 max rows stored per table in FIFO dataset
• 5,000,000 max rows stored per table in ‘none retention policy’ dataset
• 4,000 characters per value for string column in POST rows operation

However, I'm not sure if my current configuration is "none retention policy" or not.

In addition, can someone explain to me the differences between "historic data analysis" enabled or disabled in terms of rows limitations?

Thanks in advance 

[Anonymous · Accepted solution]

Hi @kmas,

>>However, I'm not sure if my current configuration is "none retention policy" or not.

AFAIK, FIFO mode is for live steam dataset, otherwise I think they will use the ‘non retention policy’ mode to store dataset.

>>In addition, can someone explain to me the differences between "historic data analysis" enabled or disabled in terms of rows limitations?

As document said, streaming dataset itself not cache/store data, so you can only create particular live tiles and can't do any customize on it.

Historic data analysis feature is for customize. If you turn on it, pushed records will caching to dataset so you cna use these history data to create other visualizations

Real-time streaming in Power BI

Regards,

Xiaoxin Sheng

[kmas]

Thank you very much for the clarification!