DOCSLIB.ORG

Analysis Services Best Practices

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Analysis Services Best Practices presented by Marco Russo [email protected] sqlbi.com sqlbi.com Who am I Latest conferences BI Expert and Consultant PASS Europe 2009 – Neuss – Germany Problem Solving Complex Project Assistance PASS 2009 – Seattle – USA DataWarehouse Assesments and Development SQL Conference 2010 – Milan – Italy Courses, Trainings and Workshops Teched 2010 – New Orleans – USA Microsoft Business Intelligence Partner Book Writer 24 Hours of PASS 2010 – Online PASS 2010 – Seattle – USA sqlbi.com Agenda DATA SOURCE (RELATIONAL MODELING) Relational Schema Decoupling Layer Dimensional Patterns Slowly Changing Dimensions Junk Dimensions Parent-Child Hierarchies Role Dimensions Drill-through Calculation Dimensions sqlbi.com sqlbi.com 1 CONFIGURATION Source OLTP DB SQLBI Methodology Relational Schema SNOWFLAKE SCHEMA Analysis Services reads data Mirror OLTP from Data Mart A Data Mart is not the Data Staging Area Warehouse ODS Data Warehouse Operational Data Store Data Marts OLAP Cubes Custom Reports Client Tools Other Systems Excel, Proclarity, … Customers Relational Schema Relational Schema STAR SCHEMA STAR VS. SNOWFLAKE SCHEMA Options for dimensions from snowflake schema: Transform into a star schema by using views Transform into a star schema by using DWV queries Join tables in SSAS dimensions Referenced Dimension Ideal solution Use SQL views to generate a star schema The star schema eliminates ambiguity Data Source Decoupling USE VIEWS TO DECOUPLE DIFFERENT LAYERS OF A BI SOLUTION DATA SOURCE (RELATIONAL MODELING) OLTP OLTP Mirror DWH DATA MART CUBES • COPY • SELECT • INTEGRATION • SELECTION • AGGREGATION Views • RENAME • CLEANSING • FILTERS • PRESENTATION Views Views • STANDARDIZAT • JOINS Views• USER ION INTERFACE sqlbi.com sqlbi.com 2 Data Source Decoupling Data Source Decoupling DECOUPLE SSAS MODEL – RDBMS STRUCTURE DEFINE VIEWS FOR SSAS CUBES Model • One view for each dimension • Namespace = cube name (Common for shared dimensions, if necessary) • Convert a snowflake in a star schema for SSAS RELATIONAL DATA SOURCE VIEW CUBES DATA SOURCE • VIEWS • AGGREGATION Columns • STAR SCHEMA • RELATIONSHIPS • PRESENTATION • SNOWFLAKE SCHEMA • NO TABLES • Number of view’s columns = number of attributes of dimension • UNCONVENTIONAL SCHEMA • USER INTERFACE • NO NAMED VIEWS • Column name = attribute name VIEWS • NO CALCULATED COLUMNS • Use a naming convention for attribute keys • Simple calculations or string operations in views • Avoid calculated column in DSV • Default values when necessary • Eliminates NULL (i.e. in case of a LEFT JOIN) Data Source Decoupling SURROGATE KEY, ATTRIBUTE KEY WHY TO USE VIEWS? GROUPING, BANDING Decoupling Stored in DB Textual interface Easy to Database Can be change objects optimized sqlbi.com Surrogate Keys Surrogate Keys WHY YOU SHOULDN’T EXPOSE SURROGATE KEYS PATTERN FOR NOT EXPOSING SURROGATE KEYS IN SSAS Benefits Dimensione Customer • _CustomerKey • Independency from application keys • KeyColumns: ID_Customer (surrogate key) • SCD modeling • NameColumn: (none) • Star schema optimization • AttributeHierarchyVisible: False • AttributeRelationship Drawbacks with Analysis Services • Attribute: Customer • Cardinality: One • MDX query with surrogate keys • Customer • Don’t have a semantic value • KeyColumns: COD_Customer (business key) • NameColumn: CustomerName • Are invalidated if the cube is reprocessed (i.e. nightly one- • AttributeRelationship shot processing) • SCD Type I – all other attributes are related to this one • Impact on custom security and reporting • SCD Type II – evaluate on a case-by-case basis (impact on KeyColumns) sqlbi.com 3 Surrogate Keys Surrogate Keys PATTERN ATTRIBUTE HIERARCHY FOR SCD TYPE I PATTERN ATTRIBUTE HIERARCHY FOR SCD TYPE II Legend Legend Customer AttributeHierarchyVisible = True AttributeHierarchyVisible = True AttributeHierarchyVisible = False AttributeHierarchyVisible = False Address Address Customer City Country _CustomerKey Customer-City City Country Customer Dimension _CustomerKey Customer Dimension Customer- Category Category Category Customer- Area Area Area Hierarchies Hierarchies • Country / City / Customer • Country / City / Customer ( Customer-City ) • Category / Customer • Category / Customer ( Customer-Category ) • Area / Customer • Area / Customer ( Customer-Area ) Attribute Keys Attribute Keys PATTERN FOR CREATING NATURAL HIERARCHIES FROM CUSTOM HIERARCHIES PATTERN FOR PRODUCT DIMENSION Legend Hierarchies AttributeHierarchyVisible = True • Color / Category (CategoryColor ) / Product Use unique key for attribute AttributeHierarchyVisible = False • i.e. Subcategory code if it is unique • Category / Color ( ColorCategory ) / Product • Don’t create one in ETL if it doesn’t exist (use composite key instead) ColorCategory Category _ProductKey Product (surrogate key) If it doesn’t exist, use attribute with composite key CategoryColor Color • Set of keys corresponding to attribute hierarchy • Set AttributeHierarchyVisible = False CategoryColor • KeyColumns: COD_Category, COD_Color Use decoupling views to generate columns for • NameColumn: Category appropriate descriptions ColorCategory • Natural hierarchy: you may reference the parent’s name • KeyColumns:COD_Color, COD_Category • Browsable attribute: use a simple description • i.e. «February 2010» hierarchy - «February» attribute • NameColumn: Color Attribute Keys Grouping PATTERN FOR DATE DIMENSION ATTRIBUTE GROUPING – AUTOMATIC VS. MANUAL Legend AttributeHierarchyVisible = True Automatic grouping AttributeHierarchyVisible = False • DiscretizationMethod Month • EqualAreas (same number of elements) DayYearMonthly MonthYear Quarter • Clusters (Data Mining algorithm) • Automatic QuarterYear • DiscretizationBucketCount Date Year • Number of groups (surrogate key) Week DayYearWeekly WeekYear Manual grouping YearWeekly • Business logic in view for dimension on Data Mart Hierarchies CASE WHEN Weight IS NULL • Year / Quarter (QuarterYear ) / Month (MonthYear ) / Day (DayYearMonthly ) OR Weight<0 THEN 'N/A''N/A''N/A' • Year / Month (MonthYear ) / Day (DayYearMonthly ) WHEN Weight<10 THEN '0'0'0-'0 ---10Kg'10Kg'10Kg'10Kg' Year (YearWeekly ) / Week ( WeekYear ) / Day (DayYearWeekly ) WHEN Weight<20 THEN '10'10'10-'10 ---20Kg'20Kg'20Kg'20Kg' • ELSE '20Kg or more' ENDENDEND sqlbi.com 4 Banding CATEGORIZE A MEASURE ACCORDING TO RANGES OF VALUES SSAS DESIGN FOR SCD TYPE I AND TYPE II Direct relationship Indirect relationship • Range granularity is the same as • Discretization and constant dimension granularity granularity • Impact of range change • Impact of range change • Fact table ETL • Dimension ETL • Dimension ETL • Reprocess Dimension • Reprocess Dimension • Reprocess Cube sqlbi.com Type I SCD Type II SCD ISSUES WITH PROCESS UPDATE SSAS MODELING Process Update Process Dimension • Doesn’t detect duplicate key errors • Process Add instead of Process Update • Process Full would fail according with error handling settings • Attribute relationship: always Rigid • Flexible aggregations are regenerated Existing MDX Queries • Unique Name may change SSAS Dimension Modeling • MDXMissingMemberMode – Ignore (Default) • There is no specific dimension type for SCD • Missing elements are ignored • Surrogate key CustomerKey • Rows/columns disappear without a warning • MDXMissingMemberMode – Error • CustomerSCD attribute – (Primary key attribute) • Need to change the query • Business key CustomerAlternateKey • Some clients require to rebuild the query from scratch • Customer attribute Type II SCD ATTRIBUTE RELATIONSHIP AND HIERARCHIES CONSOLIDATE INDEPENDENT ATTRIBUTES “Standard” Modeling “Ideal” Modeling • Only «visible» attributes • Invisible attribute • CustomerSCD should be “Customer in City” invisible • Composite key City + • Otherwise may be CustomerAlternateKey confusing for end user • Used only in hierarchy • Country-City-Customer Country-City-Customer at hierarchy is not natural Customer level sqlbi.com sqlbi.com 5 Junk Dimension Junk Dimension MODELING PERFORMANCE AND SEMANTIC Junk dimension in relational modeling Reduce aggregation complexity • Fewer dimensions • Ideal solution for performance and consumed space • Same number of attributes, but optimization on AttributeKey more • New attribute requires reprocess of fact table efficient • Unless a valid default exists for existing data • Better performance in both query and process Junk dimension only on cube Usability • Create dimension based on a view • Improves if dimension name is intuitive • Use CROSS JOIN • Use more than one junk dimension if a single name is not good • Set Attribute Key hierarchy to invisibile • Creates also combinations of values that are never used • Carefully choose names • A new attribute always require cube reprocess • Otherwise you might invalidate existing queries by changing them later Parent-Child Hierarchies LIMITATIONS OF STANDARD PARENT-CHILD HIERARCHIES LIMITATIONS MODELING MULTIPLE HIERARCHIES Functional limits • Only one parent-child hierarchy per dimension • Must use the dimension’s Attribute Key • Unique name for a member includes surrogate keys Performance issues • Increase processing time • MDX calculation is more complex (especially SCOPE, autoexists e CurrentMember) • Slower query response (Good up to some thousand members) Alternative sqlbi.com • Parent-child naturalizer in BIDS Helper Parent-Child Hierarchies Parent-Child Hierarchies STANDARD PARENT-CHILD HIERARCHIES IN ANALYSIS SERVICES STANDARD PARENT-CHILD VS MULTIPLE HIERARCHIES Pros A multiple hierarchy IS NOT a parent-child with just some more nodes • Internal
Load more

Recommended publications
  • Genesys Info Mart Physical Data Model for an Oracle Database
    Genesys Info Mart Physical Data Model for an Oracle Database Table RESOURCE_STATE_REASON 9/24/2021 Table RESOURCE_STATE_REASON Table RESOURCE_STATE_REASON Description Modified: 8.5.014.34 (in Microsoft SQL Server, data type for the following columns modified in single- language databases: REASON_TYPE, REASON_TYPE_CODE, HARDWARE_REASON, SOFTWARE_REASON_KEY, SOFTWARE_REASON_VALUE, WORKMODE, WORKMODE_CODE); 8.5.003 (in Oracle, fields with VARCHAR data types use explicit CHAR character-length semantics) In partitioned databases, this table is not partitioned. This table allows facts to be described by the state reason of the associated agent resource at a particular DN resource. Each row describes a hardware or software reason and a work mode. Tip To assist you in preparing supplementary documentation, click the following link to download a comma-separated text file containing information such as the data types and descriptions for all columns in this table: Download a CSV file. Hint: For easiest viewing, open the downloaded CSV file in Excel and adjust settings for column widths, text wrapping, and so on as desired. Depending on your browser and other system settings, you might need to save the file to your desktop first. Column List Legend Column Data Type P M F DV RESOURCE_STATE_REASON_KEYNUMBER(10) X X TENANT_KEY NUMBER(10) X X Genesys Info Mart Physical Data Model for an Oracle Database 2 Table RESOURCE_STATE_REASON Column Data Type P M F DV CREATE_AUDIT_KEYNUMBER(19) X X UPDATE_AUDIT_KEYNUMBER(19) X X VARCHAR2(64 REASON_TYPE CHAR) VARCHAR2(32 REASON_TYPE_CODE CHAR) VARCHAR2(255 HARDWARE_REASON CHAR) VARCHAR2(255 SOFTWARE_REASON_KEY CHAR) VARCHAR2(255 SOFTWARE_REASON_VALUE CHAR) VARCHAR2(64 WORKMODE CHAR) VARCHAR2(32 WORKMODE_CODE CHAR) PURGE_FLAG NUMBER(1) RESOURCE_STATE_REASON_KEY The primary key of this table and the surrogate key that is used to join this dimension to the fact tables.
    [Show full text]
  • Create Table Identity Primary Key Sql Server
    Create Table Identity Primary Key Sql Server Maurits foozle her Novokuznetsk sleeplessly, Johannine and preludial. High-principled and consonantal Keil often stroke triboluminescentsome proletarianization or spotlight nor'-east plop. or volunteer jealously. Foul-spoken Fabio always outstrips his kursaals if Davidson is There arise two ways to create tables in your Microsoft SQL database. Microsoft SQL Server has built-in an identity column fields which. An identity column contains a known numeric input for a row now the table. SOLVED Can select remove Identity from a primary case with. There cannot create table created on every case, primary key creates the server identity column if the current sql? As I today to refute these records into a U-SQL table review I am create a U-SQL database. Clustering option requires separate table created sequence generator always use sql server tables have to the key. This key creates the primary keys per the approach is. We love create Auto increment columns in oracle by using IDENTITY. PostgreSQL Identity Column PostgreSQL Tutorial. Oracle Identity Column A self-by-self Guide with Examples. Constraints that table created several keys means you can promote a primary. Not logged in Talk Contributions Create account already in. Primary keys are created, request was already creates a low due to do not complete this. IDENTITYNOT NULLPRIMARY KEY Identity Sequence. How weak I Reseed a SQL Server identity column TechRepublic. Hi You can use one query eg Hide Copy Code Create table tblEmplooyee Recordid bigint Primary key identity. SQL CREATE TABLE Statement Tutorial Republic. Hcl will assume we need be simplified to get the primary key multiple related two dissimilar objects or adding it separates structure is involved before you create identity? When the identity column is part of physician primary key SQL Server.
    [Show full text]
  • Alter Table Column Auto Increment Sql Server
    Alter Table Column Auto Increment Sql Server Esau never parchmentize any jolters plenish obsequiously, is Brant problematic and cankered enough? Zacharie forespeaks bifariously while qualitative Darcy tumefy availingly or meseems indisputably. Stolidity Antonino never reawakes so rifely or bejeweled any viol disbelievingly. Cookies: This site uses cookies. In sql server table without the alter table becomes a redbook, the value as we used. Change it alter table sql server tables have heavily used to increment columns, these additional space is structured and. As a result, had this name changed, which causes data layer in this column. Each path should be defined as NULL or NOT NULL. The illustrative example, or the small addition, database and the problem with us improve performance, it gives the actual data in advanced option. MUST be some option here. You kill of course test the higher values as well. Been logged in sql? The optional column constraint name lets you could or drop individual constraints at that later time, affecting upholstery, inserts will continue without fail. Identity columns are sql server tables have data that this data type of rust early in identity. No customs to concern your primary key. If your car from making unnatural sounds or rocks to help halt, give us a call! Unexpected error when attempting to retrieve preview HTML. These faster than sql server table while alter local processing modes offered by the alter table column sql auto server sqlcmd and. Logged Recovery model to ensure minimal logging. We create use table to generate lists of different types of objects that reason then be used for reporting or find research.
    [Show full text]
  • Keys Are, As Their Name Suggests, a Key Part of a Relational Database
    The key is defined as the column or attribute of the database table. For example if a table has id, name and address as the column names then each one is known as the key for that table. We can also say that the table has 3 keys as id, name and address. The keys are also used to identify each record in the database table . Primary Key:- • Every database table should have one or more columns designated as the primary key . The value this key holds should be unique for each record in the database. For example, assume we have a table called Employees (SSN- social security No) that contains personnel information for every employee in our firm. We’ need to select an appropriate primary key that would uniquely identify each employee. Primary Key • The primary key must contain unique values, must never be null and uniquely identify each record in the table. • As an example, a student id might be a primary key in a student table, a department code in a table of all departments in an organisation. Unique Key • The UNIQUE constraint uniquely identifies each record in a database table. • Allows Null value. But only one Null value. • A table can have more than one UNIQUE Key Column[s] • A table can have multiple unique keys Differences between Primary Key and Unique Key: • Primary Key 1. A primary key cannot allow null (a primary key cannot be defined on columns that allow nulls). 2. Each table can have only one primary key. • Unique Key 1. A unique key can allow null (a unique key can be defined on columns that allow nulls.) 2.
    [Show full text]
  • Rfgen Users Guide
    DataMax Software Group Inc. 1101 Investment Blvd. El Dorado Hills, CA 95762 USA RFgen Users Guide All Editions RFgen 5.2 © 2021 RFgen Software. A division of DataMAX Software Group, Inc. All Rights Reserved. RFgen 5.2 Users Guide Table of Contents Introduction to RFgen 1 Connection Tab 33 Basic Implementation Steps 2 Connection Tab - SAP 33 Configuration Overview 3 SAP Data Encryption 34 Configurations Shared by Dev Studio To Configure for JDE 35 and Services Console: 3 Adding A New Web Services Connection 40 Connections Shared by Dev Studio Configuring the Host Connection 42 and Services Console: 4 Configuring User Access Control 45 Configurations Available Only in Dev Studio 4 Adding or Removing RFgen Admin- istrators / RFgen SubAdmins 46 Connections Available Only in Dev Studio 4 Dev Studio Configuration Options 47 Configuring the RFgen Application Data- Configuring Menu and Key Settings 48 base 4 System Menu Configuration 48 Configuring Application Preferences 7 Function Key Actions 49 Configuring Application Services 10 Configuring the Scripting Environment 50 Configuring Environment Settings 14 Configuring Source Control Options 52 Configure System Environment 14 Configuring System Properties 54 Configuring Transaction Management DB Connection 19 Download Enterprise Objects 54 Create Application Event Database 19 Downloading ERP Business Functions 55 Configuring System Queues and Tasks 20 Downloading JDE Processing Options 55 Add New Enterprise Connections 22 Viewing Enterprise Objects 57 Adding a New DataSource Connection 22 Viewing
    [Show full text]
  • Attunity Compose 3.1 Release Notes - April 2017
    Attunity Compose 3.1 Release Notes - April 2017 Attunity Compose 3.1 introduces a number of features and enhancements, which are described in the following sections: Enhanced Missing References Support Surrogate Key Enhancement Support for Archiving Change Tables Support for Fact Table Updates Performance Improvements Support for NULL Overrides in the Data Warehouse Creation of Data Marts in Separate Schemas or Databases Post-Upgrade Procedures Resolved Issues Known Issues Attunity Ltd. Attunity Compose 3.1 Release Notes - April 2017 | Page 1 Enhanced Missing References Support In some cases, incoming data is dependent on or refers to other data. If the referenced data is missing for some reason, you either decide to add the data manually or continue on the assumption that the data will arrive before it is needed. From Compose 3.1, users can view missing references by clicking the View Missing References button in the Manage ETL Sets' Monitor tab or by switching the console to Monitor view and selecting the Missing References tab below the task list. Attunity Ltd. Attunity Compose 3.1 Release Notes - April 2017 | Page 2 Surrogate Key Enhancement Compose uses a surrogate key to associate a Hub table with its satellites. In the past, the column containing the surrogate key (ID) was of INT data type. This was an issue with entities containing over 2.1 billions records (which is the maximun permitted INT value). The issue was resolved by changing the column containing the surrogate key to BIGINT data type. Attunity Ltd. Attunity Compose 3.1 Release Notes - April 2017 | Page 3 Support for Archiving Change Tables From Compose 3.1, you can determine whether the Change Tables will be archived (and to where) or deleted after the changes have been applied.
    [Show full text]
  • Data Vault Data Modeling Specification V 2.0.2 Focused on the Data Model Components
    Data Vault Data Modeling Specification v2.0.2 Data Vault Data Modeling Specification v 2.0.2 Focused on the Data Model Components © Copyright Dan Linstedt, 2018 all rights reserved. Abstract New specifications for Data Vault 2.0 Methodology, Architecture, and Implementation are coming soon... For now, I've updated the modeling specification only to meet the needs of Data Vault 2.0. This document is a definitional document, and does not cover the implementation details or “how-to” best practices – for those, please refer to Data Vault Implementation Standards. Please note: ALL of these definitions are taught in our Certified Data Vault 2.0 Practitioner course. They are also defined in the book: Building a Scalable Data Warehouse with Data Vault 2.0 available on Amazon.com These standards are FREE to the general public, and these standards are up-to-date, and current. All standards published here should be considered the correct and current standards for Data Vault Data Modeling. NOTE: tooling vendors: if you *CLAIM* to support Data Vault 2.0, then you must support all standards as defined here. Otherwise, you are not allowed to claim support of Data Vault 2.0 in any way. In order to make the public statement “certified/Authorized to meet Data Vault 2.0 Standards” or “endorsed by Dan Linstedt” you must make prior arrangements directly with me. © Copyright Dan Linstedt 2018, all Rights Reserved Page 1 of 17 Data Vault Data Modeling Specification v2.0.2 Table of Contents Abstract .........................................................................................................................................1 1.0 Entity Type Definitions .............................................................................................................4 1.1 Hub Entity ......................................................................................................................................................
    [Show full text]
  • 3 Data Definition Language (DDL)
    Database Foundations 6-3 Data Definition Language (DDL) Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Roadmap You are here Data Transaction Introduction to Structured Data Definition Manipulation Control Oracle Query Language Language Language (TCL) Application Language (DDL) (DML) Express (SQL) Restricting Sorting Data Joining Tables Retrieving Data Using Using ORDER Using JOIN Data Using WHERE BY SELECT DFo 6-3 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. 3 Data Definition Language (DDL) Objectives This lesson covers the following objectives: • Identify the steps needed to create database tables • Describe the purpose of the data definition language (DDL) • List the DDL operations needed to build and maintain a database's tables DFo 6-3 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. 4 Data Definition Language (DDL) Database Objects Object Description Table Is the basic unit of storage; consists of rows View Logically represents subsets of data from one or more tables Sequence Generates numeric values Index Improves the performance of some queries Synonym Gives an alternative name to an object DFo 6-3 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. 5 Data Definition Language (DDL) Naming Rules for Tables and Columns Table names and column names must: • Begin with a letter • Be 1–30 characters long • Contain only A–Z, a–z, 0–9, _, $, and # • Not duplicate the name of another object owned by the same user • Not be an Oracle server–reserved word DFo 6-3 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. 6 Data Definition Language (DDL) CREATE TABLE Statement • To issue a CREATE TABLE statement, you must have: – The CREATE TABLE privilege – A storage area CREATE TABLE [schema.]table (column datatype [DEFAULT expr][, ...]); • Specify in the statement: – Table name – Column name, column data type, column size – Integrity constraints (optional) – Default values (optional) DFo 6-3 Copyright © 2015, Oracle and/or its affiliates.
    [Show full text]
  • Database Concepts Page 1 of 5
    Article :: Design Your Database :: Database Concepts Page 1 of 5 Home > Support > Articles > Design Your Database Adobe acquired InterAKT Database Concepts [ May 15, 2005 ] Table 1. Introduction 2. Database Concepts A table is a data grid used to store similar information. It 3. Plan Your Database is made up of columns (also known as fields), which 4. Relations Between Tables represent entity attributes or pieces of data, and rows, 5. Normalization which represent individual records. All records in a table 6. Best Practices in Database Design share the same fields. In the previous example, a TV set 7. Database Naming Convention and a T-shirt are records in the table that stores products. 8. Databases By Example The price and description of each product represent 9. Useful Resources columns in this table. Usually, databases have more tables, each corresponding to one of the objects you are trying to represent. Relation In a database, tables are usually related in a logical way. A link between two tables is called a relation. A relation always involves two tables and one column from each. Linking tables is very important for avoiding data redundancy and for better organizing your database. Suppose the TV set product mentioned earlier was manufactured by a company called ACME, and you also store a CD player produced by ACME. If there were not separate tables for products and manufacturers, you would need to store the same manufacturer twice in your database, once for each product. This not only takes up a lot of disk space, but maintaining several copies of the same data can make updates very difficult.
    [Show full text]
  • Short Type Questions and Answers on DBMS
    BIJU PATNAIK UNIVERSITY OF TECHNOLOGY, ODISHA Short Type Questions and Answers on DBMS Prepared by, Dr. Subhendu Kumar Rath, BPUT, Odisha. DABASE MANAGEMENT SYSTEM SHORT QUESTIONS AND ANSWERS Prepared by Dr.Subhendu Kumar Rath, Dy. Registrar, BPUT. 1. What is database? A database is a logically coherent collection of data with some inherent meaning, representing some aspect of real world and which is designed, built and populated with data for a specific purpose. 2. What is DBMS? It is a collection of programs that enables user to create and maintain a database. In other words it is general-purpose software that provides the users with the processes of defining, constructing and manipulating the database for various applications. 3. What is a Database system? The database and DBMS software together is called as Database system. 4. What are the advantages of DBMS? 1. Redundancy is controlled. 2. Unauthorised access is restricted. 3. Providing multiple user interfaces. 4. Enforcing integrity constraints. 5. Providing backup and recovery. 5. What are the disadvantage in File Processing System? 1. Data redundancy and inconsistency. 2. Difficult in accessing data. 3. Data isolation. 4. Data integrity. 5. Concurrent access is not possible. 6. Security Problems. 6. Describe the three levels of data abstraction? The are three levels of abstraction: 1. Physical level: The lowest level of abstraction describes how data are stored. 2. Logical level: The next higher level of abstraction, describes what data are stored in database and what relationship among those data. 3. View level: The highest level of abstraction describes only part of entire database.
    [Show full text]
  • Composite Key in Sql with Example
    Composite Key In Sql With Example Mind-bending Patel sometimes pencilled any bobbles sublets availably. Unsalted Tito still inlay: soi-disant and rushing Brodie sieves quite slightly but rejoins her Maurya implicitly. Ionic and overgreat Gustavus judders while Gallican Lancelot fractionizing her kurrajong sneakily and lip-read bigamously. This ended up only way longer than I aid to square out. Postgres which allow one single entry to one student selecting many classes. There has no two entities with example in with composite key sql. Please see either table samples I was finghting with before. In the example is seeing as composite. The way men do list is with composite keys when appropriate, especially the endianness and character you, use and disclosure. Alter and if user not unique key in composite pks to the rest is just created the content to a uuid or more memory and neither column. What is Candidate Key? Correlated subquery executes for skid row returned by the outer query and output depends on the voice of data returned by one row that all other rows of simple table. How can I list and foreign keys referencing a dash table in SQL Server? Adding an extra surrogate key leaving only further to revolt the design and tight data fast without bringing any benefits in conquest of performance or maintenance. If the composite primary right is being created with the table itself, frustrate the reservations. An ink is when we land to record the pursue of student class registration and call history. My today nose is really data modelling.
    [Show full text]
  • Database Administration Fundamentals Topic: Master Summary, Part 1 File Name: Dbadminfund SA 6.1.1
    98-364 D ATABASE A DMINISTRATION F UNDAMENTALS STUDENT ACTIVITY 6.1.1: VOCABULARY STUDY GUIDE MTA Course: Database Administration Fundamentals Topic: Master Summary, Part 1 File name: DBAdminFund_SA_6.1.1 Lesson Objective: 6.1: Master review of the Database Administration Fundamentals review lessons. Part 1: Vocabulary Review for Database Administration Fundamentals The vocabulary words are listed in order of their appearance in the review lessons. Some words will have more than one definition. The definition is dependent on the words’ use within the lesson. For example, the word table can mean a group of row and columns or the heart of a database, and both definitions are correct in this course, depending on the context. 1. Understanding Core Database Concepts 1.1. Understand how data is stored in tables. This objective may include but is not limited to: understanding what a table is and how it relates to the data that will be stored in the database; columns/fields, rows/records. field—a location in a record in which a particular type of data is stored. column—a group of items that are listed vertically in a table. row—a group of items that are listed horizontally in a table. table—a data structure characterized by rows and columns, with data occupying or potentially occupying each cell formed by a row-column intersection. record—a data structure that is a collection of fields (elements), each with its own name and type. A group of fields across one row. variable—the name (label) given to data, or in a database.
    [Show full text]