The Office ACE provider is used to import from text files, Excel files, and Access files. Just like for any data provider, you need to install the provider on both the client side (machine with BIDS) and on the server side (both the machine running the...

With a new storage engine comes new processing options. Here are some fast facts about processing tabular models, in Q&A format. What are my processing options? The following table shows the available processing options for each object. ...

By default, when you open the .bim file after closing it, the data comes back. Did you ever wonder where this data comes from? It depends on a number of factors. Let’s explore. Before we begin, I want you to keep a very important point in mind. The metadata...

We have this Data Backup property on the .bim file that by default is turned off. You may wonder why this property exists. Let us explore what it is this property does, and why it (and backups in general) are useful in the tabular designer. The Data Backup...

In my DirectQuery 101 post, I promised an example of configuring a model with DirectQuery only partitions. Here it is. Imagine for a moment that AdventureWorks has turned into a fast moving mega-conglomerate, with transactions written to FactInternetSales...

Managing tabular models is pretty much like managing multidimensional models. We have a full array of tools available for you to use. Here is a summary. SSMS SSMS has the backup , restore , attach , detach , delete , and synchronize features that you...

The astute user may notice that the Analysis Services tasks included with Integration Services in BIDS are unchanged for Denali. That is true. The good news is that you can use Integration Services with tabular models. Because the underlying structure...

DirectQuery is to tabular modeling what ROLAP is to multidimensional modeling. It’s a way to get query results from your model in real time without processing data into the model first. You can get started with DirectQuery by perusing some of our...

This is a follow up to part 1 – dealing with large row sets in the tabular designer . In this post I will show how to import just a subset of your table data to get started, add partitions while you go, and then process the whole model at deployment time...