On the Model page, you can change a couple options related to the processing mode, and on the Data source view page, you can change none of the settings. There are only a few settings you can actually change: Name, DirectQueryMode, and Data Source Impersonation Info. The database shown here is, of course, AdventureWorks Tabular Model SQL 2012.įigure 2: Accessing the database’s properties Figure 2 shows the Properties dialog box, opened to the Database page. You can also access the database properties, which let you configure a number of database settings. By right-clicking this node, you can perform a number of tasks, such as processing, restoring, browsing, and detaching the database. As you can see, there are three primary nodes beneath the database listing: Connections, Tables, and Roles.įigure 1: Viewing a tabular database in Object Explorer Figure 1 shows Object Explorer with all nodes of the AdventureWorks Tabular Model SQL 2012 database expanded. So now that you’ve been forewarned, let’s take a closer look at our database in Object Explorer. That said, for many of the basic administrative operations, SSMS is more than adequate, and it provides an easy way to view the data, which is just as important, if not more. When it comes to the tabular model, Microsoft sees SSDT as the primary tool for most data-definition type operations, the idea being that you redeploy, rather than making changes on the fly. However, as you’ll quickly discover, the options you have in SSMS for managing a database are quite limited compared to what’s available for relational databases-or even SSAS multidimensional databases. In SSMS, you can manage your tabular databases as well as query the data in them. If you find it listed there, you’re good to go. Then, in Object Explorer, expand the Databases node to display the database. Once you get all the pieces in place and the AdventureWorks Tabular Model SQL 2012 database deployed to the SSAS instance, open SSMS and connect to that instance. For details about how to set up the project in SSDT, configure the necessary settings, and deploy the database, see the TechNet article “ SQL Server Samples Readme.” You download the project from the same AdventureWorks CodePlex site where you download the data warehouse. The SSDT project AdventureWorks Tabular Model SQL Server 2012, which you use to deploy the AdventureWorks Tabular Model SQL 2012 tabular database to the SSAS instance. For information about setting up SSAS in tabular mode, see the MSDN topic “ Install Analysis Services in Tabular Mode.” An instance of SSAS 2012 installed in tabular mode.You can download the database from the AdventureWorks CodePlex site. An instance of the SQL Server 2012 database engine with the AdventureWorksDW2012 database installed.If you want to do so as well, you’ll need several components in place: To demonstrate the various concepts in this article, we deployed the AdventureWorks Tabular Model SQL 2012 sample database to a local instance of SSAS in tabular mode. However, before we start looking at SSMS, we need to provide a bit of setup information. Working with a Tabular DatabaseĪfter a tabular database has been deployed to an SSAS tabular instance, you can use SSMS to connect to that instance and its databases. Our plan is for this to be the first of a series of articles about accessing a tabular database deployed to an SSAS instance. You’ll learn about the components that make up a tabular database and the methods available to connect to the database to retrieve its data. We’ll introduce you to the tabular model through the eyes of SQL Server Management Studio (SSMS). What has not garnered nearly as much attention is what to do with a tabular database once it’s been deployed. Since the release of SQL Server 2012, much has been written about how to use SQL Server Data Tools (SSDT) to create a tabular model and deploy it to an instance of SSAS in tabular mode. Together these elements create a database that is fast and efficient and can deliver self-service business intelligence (BI) to a variety of applications, including Excel, PowerPivot, Power View and SQL Server Reporting Services (SSRS). Like a cube, the model also supports measures and key performance indicators (KPIs). Like a database, the tabular model supports tables and their relationships. You can think of the tabular model as a cross between a SQL Server relational database and an SSAS multidimensional cube. When Microsoft released SQL Server 2012, they introduced the SQL Server Analysis Services (SSAS) tabular model, an in-memory database that uses the xVelocity analytics engine and state-of-the-art compression algorithms.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |