![]() ![]() I immediately connected a Power BI Desktop live connection to this model instance and quickly realized I could make any change in the Visual Studio session and refresh the Desktop to see the automatic results. The ugly one that looks like “model name _ Your Name _ GUID”.Įach time you open an instance of the model in Visual Studio, this temporary instance lives for the life of your session… You probably see where I’m going with this. There is a temporary model that is spun up when developing against a Tabular model. After struggling with this, and doing a couple heavy days of DAX development at a client on their SSAS Tabular model, I had all my windows open and noticed something in SQL Management Studio that should have been apparent to me a while ago… I would then refresh the dataset in Power BI Desktop to see if the new measure or calculation worked in the visuals the way I expected. My existing approach was to add a couple measures in Visual Studio, process my model, and deploy it for each set of changes. I longed for a quick way to see results when using Live Query the same way I got them when importing or using Direct Query on a database. I like it, but I find that I really wanted to develop in the Power BI Desktop since I spend the vast majority of my time using it and deploying solutions with it. It provides a quick and easy way to verify role level security, pivot your data, and confirm outcomes. The current option we have in Visual Studio to visualize our data quickly is the Analyze in Excel feature.Īnalyze in Excel will automatically create a pivot table of your model and expose all your tables and measures for you to test. ![]() One of the challenges with SSAS Tabular model development, for me, has always been the need to fully vet out a new measure or calculation in the intended visuals. I never jumped on the MDX/Multidimensional train because my focus was on database development and internals back then, so by the time I focused more on Business Intelligence, it was an easy choice for me to invest my time where Microsoft seemed to be investing theirs. The level of entry to understanding and implementing is initially low, the compression and speed are outstanding, and the DAX language and relational concepts between a SSAS Tabular model and projects built within the Power BI Desktop are the same. I’m biased towards Tabular for several reasons. I’ve been spending a lot of time lately implementing Power BI solutions using SSAS Tabular models as the back end data source. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |