SQL Server Interview Questions : - BI Intelligence
SQL Server Interview Questions : - BI Intelligence
Contents
Explain Business intelligence and ETL? ......................................................................................................... 1 What is data warehouse and data mart and how do they differ?................................................................ 2 What is the difference between OLTP and OLAP system? ........................................................................... 3 What are Facts, Dimension and Measures tables?....................................................................................... 3 What are Cubes? ........................................................................................................................................... 4 What is the difference between star schema and snow flake design? ........................................................ 5 Where does SSIS, SSAS and SSRS fits in? ...................................................................................................... 7 What is a package, control flow and data flow? ........................................................................................... 8
In case you are fresher to SSIS, SSAS and SSRS you can start seeing our step by step videos from http://www.youtube.com/watch?v=I_Ae3suaL-U Do not forget to see our SQL Server interview question videos from www.questpond.com
View data: - Once you have analyzed the data you would like view it. Now again how people want to view data can vary from simple tabular format to complex graphical chart. So in this section we would need good reporting tools to achieve the same.
What is data warehouse and data mart and how do they differ?
Data warehouse is a database which is used to store data for reporting and data analysis. Data in data ware house can come from disparate sources like structured RDBMS, Files or any other source. ETL ( ETL has been explained in the previous question) process fetches data from these sources and loads it in to data warehouse. Data warehouse can be further divided in to data marts. Data warehouse focuses on wide data while data mart focuses on specific processes. Data warehouse are also termed as OLAP systems (OLAP is explained in the next question) . The database designs for these systems do not follow conventional normalization (1st, 2nd or 3rd normal form) design. Most them use denormalized design like star schema and snow flake design. They normally store data in fact and dimension tables.
Source Motive
SQL complexity
So if we change the dimensions and measures in a cube format we would get a better picture. In other words cube is intersection of multiple measures and their dimensions. If you visualize the same in graphical mode below is the image how it will look like.
What is the difference between star schema and snow flake design?
Star schema consists of fact and dimension tables. The fact tables have the measures and dimension tables give more context to the fact tables. In the below figure Star design you can see we have four dimension tables and each one of them are referencing the fact tables for measure values. The references between dimension and fact tables are done using simple foreign key relationships.
Snow flake design is very much similar to star design. The exception is the dimension table. In snow flake dimension tables are normalized as shown in the below figure Snow flake design. The below design is very much similar to the star design shown previously but the products table and vendor tables are separate tables. The relationship is more of a normalized format. So summing in other words Star design is pure denormalized design while snow flake can have normalized dimension tables.
Star Schema Pure denormalized dimension tables. More redundancy due to denormalized format so more maintenance.
Maintenance
Query
Complex Queries due to normalized dimension tables. More joins due to normalization. If you are concerned about integrity and duplication.
Simple queries due to pure denormalized design. Less joins. More than data integrity speed and performance is concern here.