Database Reference
In-Depth Information
on appropriate buttons. One notable difference is the Data source drop-
down box. If we had defined multiple data sources, we could import objects
into the same DSV using multiple sources. In order to include objects from
multiple data sources into a single DSV, the primary data source must be
SQL Server; as you can see from the previous screenshot, the dialog clearly
identifies the primary data source.
3. Be aware that generally it is not recommended to use the same DSV to com-
bine data from multiple sources. Importing data from multiple data sources
will result in the use of the OPENQUERY syntax for getting data from non-
primary data sources, which could be less optimal than having a single data
source or a separate DSV for each data source. However, you can only
define relationships among objects found in the same DSV; hence, each DSV
would have to have separate measure groups. You will learn more about
measure groups in Chapter 3 , Creating Analysis Services Cubes .
4. If you proceed with adding the remaining tables and views found in the Ad-
venture Works DW 2012 sample database, you'll find that the DSV becomes
somewhat cluttered and difficult to read. Clearly, a DSV for a real-world ap-
plication with dozens or even hundreds of tables will be even more complic-
ated to decipher. Fortunately you can right-click on any blank area within a
DSV and choose the Zoom option to have the DSV fit the available screen
space.
5. You also have an option to find a particular table; this option brings up the
list of tables. Once you click on the desired table in the list and click on Ok ,
SSDT will focus on that table on the DSV. Alternatively, you can achieve the
same by clicking on the table of interest in the Tables list on the leftmost
pane in SSDT, as shown in the following screenshot:
Search WWH ::




Custom Search