title

Multidimensional Model Databases (SSAS) | Microsoft Docs

ms.custom

ms.date

06/13/2017

ms.prod

sql-server-2014

ms.reviewer

ms.technology

analysis-services

ms.topic

conceptual

helpviewer_keywords

SQL Server Management Studio [Analysis Services], databases

SQL Server Analysis Services, databases

SSAS, databases

Analysis Services, databases

databases [Analysis Services], designing

Business Intelligence Development Studio, databases [Analysis Services]

databases [Analysis Services]

ms.assetid

78b2f22a-b7bd-4a2b-b6fc-0bff4d2b3168

author

minewiskan

ms.author

owend

manager

craigg

Multidimensional Model Databases (SSAS)

An [!INCLUDEssASnoversion] database is a collection of data sources, data source views, cubes, dimensions, and roles. Optionally, an [!INCLUDEssASnoversion] database can include structures for data mining, and custom assemblies that provide a way for you to add user-defined functions to the database.

Cubes are the fundamental query objects in Analysis Services. When you connect to an Analysis Services database via a client application, you connect to a cube within that database. A database might contain multiple cubes if you are reusing dimensions, assemblies, roles, or mining structures across multiple contexts.

You can create and modify a [!INCLUDEssASnoversion] database programmatically or by using one of these interactive methods:

Deploy an [!INCLUDEssASnoversion] project from [!INCLUDEssBIDevStudioFull] to a designated instance of [!INCLUDEssASnoversion]. This process creates an [!INCLUDEssASnoversion] database, if a database with that name does not already exist within that instance, and instantiates the designed objects within the newly created database. When working with an [!INCLUDEssASnoversion] database in [!INCLUDEssBIDevStudio], changes made to objects in the [!INCLUDEssASnoversion] project take effect only when the project is deployed to an [!INCLUDEssASnoversion] instance.
Create an empty [!INCLUDEssASnoversion] database within an instance of [!INCLUDEssASnoversion], by using either [!INCLUDEssManStudioFull] or [!INCLUDEssBIDevStudioFull], and then connect directly to that database using [!INCLUDEssBIDevStudioFull] and create objects within it (rather than within a project). When working with an [!INCLUDEssASnoversion] database in this manner, changes made to objects take effect in the database to which you are connecting when the changed object is saved.

[!INCLUDEssBIDevStudioFull] uses integration with source control software to support multiple developers working with different objects within an [!INCLUDEssASnoversion] project at the same time. A developer can also interact with an [!INCLUDEssASnoversion] database directly, rather than through an [!INCLUDEssASnoversion] project, but the risk of this is that the objects in an [!INCLUDEssASnoversion] database can become out of sync with the [!INCLUDEssASnoversion] project that was used for its deployment. After deployment, you administer an [!INCLUDEssASnoversion] database by using [!INCLUDEssManStudioFull]. Certain changes can also be made to an [!INCLUDEssASnoversion] database by using [!INCLUDEssManStudioFull], such as to partitions and roles, which can also cause the objects in an [!INCLUDEssASnoversion] database to become out of sync with the [!INCLUDEssASnoversion] project that was used for its deployment.