[GetCatalogExtendedContentData] procedure killing server
Hello there, Im running on-premise PowerBI Report Server on MS-SQL Server and after some time the reports on server become unavailable to users. My monitoring shows that this is caused by resource wait type ASYNC_NETWORK_IO (orange line) and associated stored procedure [dbo].[GetCatalogExtendedContentData]: I assume this procedure is called by server itself, but user action such as report refresh might be calling it. From query I understand what it does, but since values in database are hashed I don't know the purpose of it. Can anyone describe me when and how is this procedure called, so I can find the problematic report / user action causing the problem? Or if there is any documentation regarding these SP, I would welcome it as well.
Report Export to Excel based on Schedule (Email,Shared Path)
Hi , we are using SQL enterprise edition,with which PowerBI Report server onpremise Aug2018 version we are deploying dashboards and reports. here the way how SSRS reports output is scheduled to shared path or email (data driven,event driven etc) options. simmilar option we are expecting for PowerBI tabular visuals to export to Excel or PDF based on a schedule. 1.Are there any third party tool which serve the need 2.Any near future plan of Microsoft to have this onpremise for PowerBI dashboards also we have checked Christianstevens Product but it requires cloud Account of AzureAD or Office 365 any other tools please suggest.SQL Server 2012 v SQL Server 2016 for PBIRS
We're evaluating the implementation of the Power BI Report Server in order to use it as an on-prem solution for our users across the group. We already have SQL servers in place and majority of the users will only need to consume reports. According to the minimum requirements here, SQL Server 2012 is included in the list but I've been advised that you should have a minimum of SQL Server 2016. I've also seen this elsewhere in my research. Can anyone help shed some light on this? Are there any other issues to keep in mind with implementing the report server with SQL Server 2012? We have other applications that are not compatible with later versions of SQL and would be replaced as part of a larger project with a time horizon of 2-3 years.
