Configure default data modeling and deployment properties
Applies to: SQL Server Analysis Services Azure Analysis Services Fabric/Power BI Premium
This article describes how to configure the default compatibility level, deployment, and workspace database property settings, which can be pre-defined for each new tabular model project you create in SQL Server Data Tools. After a new project is created, these properties can still be changed depending on your particular requirements.
To configure the default compatibility level
In Visual Studio, click Tools > Options.
In the Options dialog box, expand Analysis Services Tabular > New project settings.
Configure the following property settings:
Property Default setting Description Default compatibility level for new projects Depends on projects extension version This setting specifies the default compatibility level to use when creating a new Tabular model project. To learn more, see Compatibility Level for Tabular models in Analysis Services. Default filter direction Single direction Single direction, or one-way, is the traditional many-to-one filter direction between fact and dimensional tables in a relationship. Both directions, or two-way, is a cross-filter that enables the filter context of one relationship to be used as the filter context for another table relationship, with one table common to both relationships. To learn more, see Bi-directional cross filters in tabular models. Compatibility level options All checked Specifies compatibility level options for new Tabular model projects and when deploying to another Analysis Services instance.
To configure the default deployment server property
In Visual Studio, click Tools > Options.
In the Options dialog box, expand Analysis Services Tabular > Deployment.
Configure the following property settings:
Property Default setting Description Default deployment server localhost This setting specifies the default server to use when deploying a model. You can click the down arrow to browse for local network Analysis Services servers you can use or you can type the name of a remote server. Note
Changes to the Default deployment Server property setting will not affect existing projects created prior to the change.
To configure the default Workspace Database property
It's recommended you leave the default Integrated workspace or specify a local Analysis Services server as the workspace server. For workspace databases on a remote server, data cannot be backed up locally and the user interface may experience latency during queries. To learn more, see Workspace database.
In Visual Studio, click Tools > Options.
In the Options dialog box, expand Analysis Services Tabular > Workspace Database.
Configure the following property settings:
Property Default setting Description Integrated workspace Selected Specifies new model projects use an Analysis Services instance built into Visual Studio. Workspace server localhost All available instances of Analysis Services running on the local computer are included in the listbox.
For workspace databases on a remote server, data cannot be backed up locally and the user interface may experience latency during queries.Workspace database retention after the model is closed Keep workspace databases on disk, but unload from memory Specifies how a workspace database is retained after a model is closed. A workspace database includes model metadata, the data imported into a model, and impersonation credentials (encrypted). In some cases, the workspace database can be very large and consume a significant amount of memory. By default, workspace databases are removed from memory. When changing this setting, it is important to consider your available memory resources as well as how often you plan to work on the model. This property setting has the following options:
Keep workspaces in memory - Specifies to keep workspaces in memory after a model is closed. This option will consume more memory; however, when opening a model in SQL Server Data Tools, fewer resources are consumed and the workspace will load faster.
Keep workspace databases on disk, but unload from memory - Specifies to keep the workspace database on disk, but no longer in memory after a model is closed. This option will consume less memory; however, when opening a model in SQL Server Data Tools, additional resources are consumed and the model will load more slowly than if the workspace database is kept in memory. Use this option when in-memory resources are limited or when working on a remote workspace database.
Delete workspace - Specifies to delete workspace database from memory and not keep workspace database on disk after the model is closed. This option will consume less memory and storage space; however, when opening a model in SQL Server Data Tools, additional resources are consumed and the model will load more slowly than if the workspace database is kept in memory or on-disk. Use this option when only occasionally working on models.Data backup Keep backup of data on disk Specifies whether or not a backup of the model data is kept in a backup file. This property setting has the following options:
Keep backup of data on disk - Specifies to keep a backup of model data on disk. When the model is saved, the data will also be saved to the backup (ABF) file. Selecting this option can cause slower model save and load times
Do not keep backup of databack on disk - Specifies to not keep a backup of model data on disk. This option will minimize save and model loading time.Ask new project settings for each new project created not checked Specifies no default workspace database type is selected for new projects.
Note
Changes to default model properties will not affect properties for existing models created prior to the change.