I deleted that line and ran it again. This time I got this error. “formatString”: “dddd\\, mmmm d\\, yyyy”, I typed Ctrl G and entered the line number to fix the first error which was on this line The JSON DDL request failed with the following error: Unrecognized JSON property: variations. I then executed the script, and got my first error I also changed the database name to “SampleAS” from the GUID that it was assigned. 1400 is for Azure AS, SQL Server 2, so I edited the script to change the value 1200. The first thing you will need to fix is the compatibility level. Open up the XMLA file you created in Analysis Sr. Give the file a name as you will be using it after connecting to your analysis Services instance. Right click on the Database with the GUID name and select Script->Script Database As->Create To-> File. Once the connections are changed, you will need to create an XMLA script and edit it. I changed the Provider to SQL Server, and fixed the connection. Once you click ok, you can edit the connection to something that will work.Īll of my Power BI tables were connecting to views in SQL Server, which is a best practice as this allows you to select only the fields you need and provides you with the ability to sort your data as it is read in, which can improve the compression. Click on the ellipse button next to the connection string, and you will get this error message. Right click on the connection and select properties. The first step is to fix the connections, then edit some JSON. TL DR This model is not usable and you will have to do some tweaks to it to make it work. Now I can look at my Power BI model in SQL Sever Analysis Services from within Management Studio. This command returns the address I need to access Power BI model from Analysis Services, 127.0.0.1:51328 Using this number I went to the command prompt and typed This command will bring you to the Details table in Task Manager and will highlight which version and PID to connect in Analysis Services on your computer. Right click on the instance of Microsoft SQL Server Analysis Services running within Power BI Desktop and select Go to Details. You see by the picture here, that there are 19 processes running with one Power BI file loaded. Open up the Task Manager and take a look at the Power BI Desktop in the Processes tab by clicking on the arrow at the right-hand side so that you see all of the processes running. Power BI is running a version of Analysis Services tabular and once you figure out what version is running you can connect to it. Connect to your Power BI Model in Analysis Services After your Power BI desktop file is clean, leave it running as you are going to need to have it running for the next step. Make sure your Power BI Model does not include commands such as SELECTEDVALUE, GENERATESERIES as well as all of the automatically generated date hierarchies. If you have any new DAX commands, take them out of your Power BI Model which means you will not have to manually edit the JSON file to remove them when the new commands are flagged as errors. I was upgrading to AS on SQL Server 2016, there were some commands that I had to manual edit out of the JSON file. Unless you are upgrading to analysis services on SQL Server 2019, chances are you are going to have to review your DAX code and make some modifications as DAX on the other versions of SQL Server are not the same as Power BI. Preparing your Power BI model to Upgrade to Tabular I am writing this blog to save you some time as I learned a few tricks which I wish I would have known about before upgrading. I also blew my schedule as the upgrade process went from a 20 minute process to something that took over 2 hours. I know I needed to upgrade after that and I was really sorely disappointed. If you were looking to upgrade a Power BI model to Analysis Services Tabular, hopefully you decided to do it before March 1, 2019, that was the day Microsoft decided to remove the tool from Azure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |