DBM/384 Special Purpose Databases

   

Or you may purchase tutorials by the Week below.
DBM/384 Data Warehouse Project Part 1
DBM/384 Data Warehouse Project Part 1

DBM/384 Data Warehouse Project

DBM/384 WEEK 1

Includes Everything listed below for Week 1! A+ Work!  

Get the Entire Week of Tutorials for One Low Price!

 

Individual: Wk 1 - Data Warehouse Project, Part I 

Includes Option #1 with sql scripts and screenshots in both MS Word and MS Powerpoint

Includes Option #2 with sql scripts and screenshots

 

Complete the following using Microsoft SQL Server 2016:

Write SQL scripts in Microsoft SQL Server for OLTP that include:

  • A Data Definition Language (DDL) script creating the four tables with appropriate data types, primary and foreign keys
  • Data Manipulation Language (DML) scripts that insert a minimum of five records into each table
  • Select scripts showing the full contents of each table

Write and run a test script for Step Two.

Save a screenshot of the results.

Create a 6-page Technical Design Document that includes the SQL scripts in Microsoft SQL Server, test script, and screenshots.

Compress the Technical Design Document that includes the SQL scripts in Microsoft SQL Server, test script, and screenshots into a ZIP file.

Submit the ZIP file.

Wk 1 Discussion - General vs. Special-Purpose Databases 

Includes 5 Long Answers to Discussion Question

Identify a general purpose and a special purpose database of your choice. Research and compare the general and special purpose databases that you have selected. Describe differences between the two databases.

 

DBM/384 Data Warehouse Project Part II
DBM/384 Specialist Database Presentation
DBM/384 Week 2 DQ

COMING SOON!

DBM/384 WEEK 2

 

Includes Everything listed below for Week 2!  

Get the Entire Week of Tutorials for One Low Price!

 

Learning Team: Wk 2 Specialist Database Presentation

Your team is tasked with creating an inventory price-tracking database for a company of your choosing.

Complete the following steps in Microsoft® SQL Server® 2016:

  1. Create a table. This table will tell you what price the inventory item started at, what it currently is, and what it ends at. The primary key must be a combination of the inventory number and the current price date. Elements to include in your table are as follows:
  2. a. Inventory Number Integer

    b. Inventory Description Text

    c. Date Price Previous Date

    d. Date Price Current Date

    e. Date Price End Date

    f. Inventory Price Decimal

  3. Create an insert statement that will be used to initially add an inventory item. Remember that the previous date will be null, the start date will be today's date, and the end date will be null.
  4. Create a stored procedure that will be used to update the price of an item. The procedure will take the inventory number and a new price.
  5. Update the current record by updating the Date Price End Date to be the current date. Then, create a new inventory record where the Date Price Previous Date is today's date, Date Price Current Date is tomorrow's date (price is effective tomorrow), and Date Price End Date is null. Remember to bring over the inventory description and inventory number, as well.
  6. Create a query that will display a list of all the current inventory prices.
  7. Write and run a test script for Steps Two through Four.
  8. Save a screenshot of the results.

Compress your DDL and DML scripts, query, test script, and results into a ZIP file.

Submit the ZIP file.

 

Individual: Wk 2 - Data Warehouse Project, Part II 

Includes 5 Long Answers to Discussion Question

Use the credit card database from the Week One Individual assignment, "Data Warehouse Project, Part I," as a basis for the creation of a data warehouse.

Complete the following steps:

  1. Define the business requirements, objectives, and deliverables.
  2. Declare the grain.
  3. Choose dimensions.
  4. Identify fact duration.
  5. Identify facts.

Create a 6-page Technical Design Document that includes a description of the five steps above and the results of completing the steps for the credit card data warehouse.

Submit your Technical Design Document.

 

Wk 2 Discussion - OLTP and OLAP

Organizations use database technology to store data that they collect, analyze, measure, and monitor as they conduct business. Data that is captured during transactional processes, as organizations sell products and services to their customers, is best structured in an OLTP database. Data that is used to analyze trends, key metrics, summary data, and for data mining is best stored in an OLAP database. Database designers need to understand the differences between OLTP and OLAP data and how to best design and build databases to support OLTP or OLAP requirements.
From the perspective of a Database Designer, identify the differences between Online Transaction Processing (OLTP) and Online Analytical Processing (OLAP) databases. Explain when a company would choose one database over the other and why.

 

DBM/384 Data Warehouse Project Part III
DBM/384 Specialist Database Presentation
DBM/384 Week 3 DQ

COMING SOON!

DBM/384 Week 3

Everything listed for this week is included in purchase!

 

Learning Team: Wk 3 Specialist Database Presentation

Determine how spatial components can be used in the database your team created in Week Two.

Create an Entity Relationship Diagram (ERD) with spatial components. Use Microsoft Visio to create this diagram.

Include a minimum of two spatial components from the list below:

  • Longitude/Latitude
  • Polygon
  • Points
  • Lines

Add comments to your ERD explaining the components and their use.

Submit your ERD.


 

Individual: Wk 3 - Data Warehouse Project, Part III 

Use Microsoft Visio and an Excel spreadsheet or Word document to complete this assignment.

Identify and define all dimension attributes for the dimensions identified in the Week Two Individual Assignment, "Data Warehouse Project, Part II".

For each dimension, document the following information for each of its attributes:

  • Name
  • Description
  • Type
  • Characteristics

Design a star schema diagram for the credit card data warehouse.

Create a 5-page Technical Design Document that includes both the dimension definitions for each dimension attribute and the star schema diagram.

Submit your Technical Design Document.

 

Wk 3 Discussion - Spatial Database Indexing

Includes 5 Long Answers to Discussion Question 

Part of a Database Administrator's job is to ensure appropriate information retrieval performance of their databases. End users do not and in many cases can't wait for databases that perform slowly. This is true for many spatial databases. Consider Google Maps and the spatial data that this application stores and provides to its users. If it performs slowly, it would not provide useful driving directions. It has to perform well to be used. Slow database performance would make this application ineffective and could be dangerous or life threatening for the people who rely on it for driving directions.
From the perspective of a Database Administrator who is concerned about database performance, explain why indexing is so important when working with a spatial database.

 

DBM/384 Data Warehouse Project Part IV
DBM/384 Specialist Database Presentation
DBM/384 Week 4 DQ

COMING SOON!

DBM/384 Week 4

Everything listed for this week is included in purchase!

 

Learning Team: Wk 4 Specialist Database PresentationComplete the following activities:

  • In the SQL Server 2016 query window, write an XML script that provides an update to one table in the database your team created in Week Two.  
  • Write a XML script that provides a data feed to an external dashboard used by the executives of the company. The Dashboard is not required to be turned in only the XML code providing the data.
  • Write and run a test script for Steps One and Two.
  • Save a screenshot of the results.

Add comments to your XML scripts explaining the benefits to your Learning Team company that a mobile database would provide the existing data system.

Compress your XML scripts, comments, test script, and results into a ZIP file.

Submit the ZIP file.

 

Individual: Wk 4 - Data Warehouse Project, Part IV 

Complete the following using Microsoft SQL Server 2016:

  • Write SQL scripts that include the following:
  • A Data Definition Language (DDL) script creating the dimension and fact tables for the credit card database
  • Data Manipulation Language (DML) scripts that insert records into each table from the data created in the OLTP database created in Week One
  • Select scripts showing the full contents of each table
  • Create a star schema using the Database Diagram tool in SQL Server®
  • Write and run a test script for Step One.
  • Save a screenshot of the results.

Create a 5-page Technical Design Document that includes the following topics:

  • The star schema diagram
  • The SQL DDL scripts
  • The SQL DML scripts
  • The test script
  • The screenshot of the results from running the scripts

Submit your Technical Design Document.

 

Wk 4 Discussion - NoSQL

Includes 5 Long Answers to Discussion Question

A mid-sized financial services company is considering implementing a NoSQL database. From the perspective of an IT Manager in this financial services company, describe how NoSQL databases could be used in the organization. Under what circumstances might it be an appropriate implementation choice for a financial services business? 

 

DBM/384 Data Warehouse Project Final Project
DBM/384 Specialist Database Presentation
DBM/384 Week 5 DQ

COMING SOON!

DBM/384 Week 5

 

Everything listed for this week is included in purchase!

 

Learning Team: Wk 5 Specialist Database PresentationCreate a 1-page Technical Design Document, which describes the business use of the Learning Team company's database. 

Include scripts and Entity Relationship Diagrams (ERDs).

Submit your document.

 

Individual: Wk 5 - Data Warehouse Project Final Project 

Finalize the credit card data warehouse by completing the following steps using MicrosoftSQL Server 2016:

  • Write a Select query against the fact table and one dimension table.
  • Write a Select query against the fact table and at least two dimension tables, one of which should be the time dimension.
  • Create a view that queries the fact table and three dimension tables.
  • Write and run a test script for steps one through three.
  • Save a screenshot of the results.

Complete the 6-page Technical Design Document that includes the SQL queries created for Week Five, the test script, and screenshots of the results.

Construct a final 15-slide tutorial in Microsoft PowerPoint with speaker notes that addresses the following criteria:

  • Differentiates between general purpose and specialized databases
  • Identifies uses of special purpose databases in business
  • Introduces goals for effective database design
  • Explains how temporal databases are used in business
  • Explains how Structured Query Language (SQL) is used with temporal databases
  • Demonstrates how a temporal database is used in business
  • Explains how spatial databases are used in business
  • Explains how SQL is used with spatial databases
  • Explains the importance of indexing with spatial databases
  • Demonstrates how a spatial database is used in business
  • Demonstrates how an eXtensible Markup Language (XML) database is used
  • Explains how multimedia databases are used in business
  • Explains how NoSQL databases are being used to store unstructured business data
  • Explains how mobile databases are used in business
  • Contrasts Online Transaction Processing (OLTP) and Online Analytical Processing (OLAP) databases
  • Describes data warehouses and data mining
  • Explains knowledge management
  • Explains the process of information retrieval

Submit the Technical Design Document and the tutorial presentation.

 

 

Wk 5 Discussion - Strengths and Weaknesses of Info Retrieval

Includes 5 Long Answers to Discussion Question

Select a website from the Internet that provides information to its stakeholders; examples of websites to consider are SEC.gov or USA.gov. Describe the strengths and weaknesses of the information retrieval processes used on this website from an end-user perspective.