Dear all,
I have a situation where, a PBI dataset has recently started to kill one of our production SQL DBs on refresh, it will lock out all other users indefinitely until the PBI account has its access manually revoked.
We have cloned the production database and want to now crash this so we can determine why this problem occurs. Specifically why PBI will not timeout properly and instead locks out others users indefinitely.
I can identify the query that is casuing the problem as if I refresh the PBIX file in the desktop pointed at the cloned databse it will time out. This doesn't however kill the SQL server. So it is some issue with the Service.
Also, because the desktop PBIX file will timeout on refresh I can't publish the new one pointing at the cloned server.
So how can I change the server that the Service dataset is pointing to (from the production DB to the cloned DB), and then enable refresh to try and crash this cloned DB. Crashing the production database to determine what is going on is obviously not an option as it is one of the organisations important day to day systems.
I know I can fix the problem, but I don't want to do that, but rather identify how PBI is crashing our DBs so we can either stop it happening or switch to a different BI system owing to the introduced risks. from PBI.
We need to recreate this error if we are to enable Power BI through our organisation as we don't want to enable a service that will crash databases.
Thanks you very much for your help.
