That is a bit scary and odd... have you reported this to MS? If they are aware of it and it is a limitation of the function, they should document...

Did it work better when run outside of Visual Studio?

I think this depends on the P2V tools and VM host. But this is more of a server question than a SQL question. My advice would have been to not...

First step is to review the error message. Without seeing the EXACT error message (and any associated errors) it is hard to say what the problem is. If I had...

To add to what Jeff said, DBA in the cloud is a VERY similar skill set to DBA on premise. On the back end, it is all the same thing...

Step 1 - check the docs:

https://learn.microsoft.com/en-us/analysis-services/multidimensional-models/supported-data-sources-ssas-multidimensional?view=asallproducts-allversions

things to note:

ODBC data sources are not supported for multidimensional solutions

AND if you want to connect to other databases, you need an "An OLE DB...

I'm still thinking this is either:

A - expected behavior <-- that is there is an error message being sent in the email notification

B - bug in Visual Studio or SSDT...

The ONLY reason I see to use powershell for a backup process would be if you needed to move the file to a location that the SQL agent service didn't...

According to the MS docs, that shouldn't be happening. As a really random thought - is it possible that an error did occur, just not the way you were thinking?...

As a random guess, does the SQL Agent Service account have access to the file you are trying to rename? If I had to guess I would say It is...

My opinion, I would ask them to do basic troubleshooting to validate that the disk is good. Just because other systems are running fine now, doesn't mean they will continue...

If I had to guess, I'd say that the transaction is not committing.

But my first steps when troubleshooting things like this are to check things like profiler or extended events...

The error tells you MOST of what you need to know - the user doesn't have access to log into the database. Your next step will be to log into...

I have a feeling that would fail, but why don't you give it a shot?

But I think the correct syntax for concat is a "+" in SSRS.

So, based on what you have said, your JOIN syntax is filtering out the data.

My next steps then would be to do the SELECT COUNT(*) and have all the joins...