Categories
MySQL

i already down my task but i dont know why the solution is wrong please help, th

i already down my task but i dont know why the solution is wrong please help, these question about the Stored Procedures

Categories
MySQL

Write the query and then take a screenshot of the output for each question. See

Write the query and then take a screenshot of the output for each question.
See attached assignment and use the script provided.

Categories
MySQL

Write the query and then take a screenshot of the output for each question. See

Write the query and then take a screenshot of the output for each question.
See attached assignment and use the script provided.

Categories
MySQL

Looping JavaScript Object Values <p id="d

Looping JavaScript Object Values

const myJSON = ‘{“name”:”John”, “age”:30, “car”:null}’;
const myObj = JSON.parse(myJSON);
let text = “”;
for (const x in myObj) {
text += myObj[x] + “, “;
}
document.getElementById(“demo”).innerHTML = text;

Categories
MySQL

Note: lab should be built in SSIS and saved as a package. Take screen shots of e

Note: lab should be built in SSIS and saved as a package. Take screen shots of each step and paste them all in one MS Word Document. zip file both and send to me. Using adventureworks2019 in sql server management studio and visual studio 2017
question 1.
Create an SSIS package to load Employee.txt file in to LearningSSIS..tblEmployee
Create table tblEmp in LearningSIS2 database with the same schema as LearningSSIS..tblEmployee table
(do not populate tblEmp)
Create a SSIS package to load the data from LearningSSIS..tblEmployee to LearningSSIS2..tblEmp
Create database Prospects
Create table tbl_stg_Prospects in Prospects– (Refer to Project document)
Create a SSIS package Load_Prospects_Staging.dtsx to load the data from Prospect_B.xls to tbl_stg_Prospect
end of question 1
Question 2
Note: lab should be built in SSIS and saved as a package. Take screen shots of each step and paste them all in one MS Word Document. zip file both and send to me. Using adventureworks2019 in sql server management studio and visual studio 2017
Modify Load_Prospects_Staging.dtsx to include the followingTruncate the tbl_stg_Prospects table before loading the Prospect_B.xls file.
Add functionality to load multiple Excel files

Categories
MySQL

Project Description: “Nutrition tracking is the process of collecting and anal

Project Description: “Nutrition tracking is the process of collecting and analyzing qualitative or quantitative data on your dietary intake patterns, typically for the purpose of achieving health-related or fitness-related goals.” Intake In this project, you will design and implement a nutrition-tracking database. This database will help the users to track the food and drinks they consume. The stored data includes but not limited to, food names, quantities, calories, consumption date and time, workout sessions and any other information you find related to the project. The final project is composed of three parts: • Part 1: Project proposal (10%) • Part 2: Project implementation (60%) • Part 3: Project Presentation (30%) Part 1 – Project Proposal – due Nov 4th @ 11:59 pm: What data will your database store? You can list a preliminary set of entities/attributes that will be in the database?
Our database will store data related to :
 Users info (weight , height, age, gender , name)
 Exercise frequency ( daily, never )
 Eating Frequency ( how many times do the user eats)
 Food types ( Proccessed , Organic food, Homemade food)
 Number of drinks an user consume in the day.
 Types of drinks ( sodas, water, organic fruit juice)
 Food consumption day ( example May 22 or June 20)
 Calories intake per meal ( breakfast, lunch, dinner)
 Total calories consumption in a day .
 Weigh result (Gain weight, lose weight , stay fit)
2. List 10 questions (Not SQL) that can be answered by querying the database (e.g. How many calories did the user consume on July 12, 2022?). Ten questions that can be answered by the database are:
 What is the user information: like name, height, weight?
 What kind of food gives more calories?
 How many times the user eat in a day?
 How often do the user practice exercise?
 How much extra calorie did the user consume?
 How much calorie did the user burn?
 What types of drinks has less calorie?
 What is the calorie amount that different types of food gives?
 What is the total calorie that the user consumed in a specific date?
 What will be the change in user’s weight after the calorie intake
Part 2: – Project Implementation – due Nov 27th @ 11:59 pm: Report 2 Contents: 1) Project goals. 2) Database description: A general description of the database, what data is stored in the database. How the database will benefit the users. 3) Data model & design: o Completed ER/EER diagram, 5 tables minimum.  MUST use https://www.draw.io to draw the ER diagram, and then take a snapshot.  Include a snapshot of the diagram in the report. o Business rules. o Data dictionary: For each one of the tables, list columns, data types, column restrictions, column descriptions.
4) Implementation: o Use MySQL Server and MySQL Workbench to create the database/tables.  Include a snapshot of the SQL code in your report o Populate the each table with a minimum of 20 rows of sample data. Make sure the entered data is descriptive (not just random numbers and letters.  Include a snapshot of the SQL code in your report. o Use MySQL Server and MySQL Workbench to write/run all of the SQL queries below. For each query, provide the following in Report 2:  Snapshot of the code and the output in the report.  In about 2 lines, explain what the query returns. Queries:  1 trivial query. Simple select with ordering.  2 medium difficulty queries. Queries that use composite condition for selection, computations, aggregate function and grouping.  1 query that uses subquery.  2 queries that uses join (1 inner join, 1 left or right outer join).  1 view (query must use join – hint: you can use one of the queries from the previous question).  1 query that uses union.  1 custom stored function.  1 custom stored procedure.

Categories
MySQL

Scott = public_knowledge

1) Create a NEW pluggable database with your first initial and last name. For example, my pluggable database would be named jackalbert. Connect to your pluggable database using the ALTER SESSION command.
2) Verify that OLS is enabled in your pluggable database. If it isn’t, then enable it and re-verify.
3) Within your pluggable database, run the following commands:
create user president identified by president;
create user vicepresident identified by vicepresident;
create user salesmanager identified by salesmanager;
create user generalmanager identified by generalmanager;
create user scott identified by tiger ;
grant create session to president, vicepresident, salesmanager, generalmanager, scott;
grant create table, unlimited tablespace to president;
3) Connect to your pdb as President and run the following table create:
CREATE TABLE SALES_PROJECTIONS (SALES_NO NUMBER, SALES_TYPE VARCHAR2(100), SALES_FIGURE NUMBER));
insert into SALES_PROJECTIONS values (1102, ‘Experimental Concep’, ‘The use of remote viewing to target the minds of diplomats through their dreams’);
insert into SALES_PROJECTIONS values (1436, ‘Hydrogen Cell’, ‘Research into weather controlling technology’);
insert into SALES_PROJECTIONS values (1577, ‘Plug-In Electric’, ‘Anti-gravity research’);
insert into SALES_PROJECTIONS values (1296, ‘Plug-In Hybrid’, ‘Attempts to induce paralysis in an enemy via mental impairment’);
insert into SALES_PROJECTIONS values (1863, ‘Gas-Electric Hybrid’, ‘Speading disinformation about UFOs’);
insert into SALES_PROJECTIONS values (1864, ‘Commercial’, ‘A fully autonomous self-driving car’);
insert into SALES_PROJECTIONS values (1895, ‘Foreign’, ‘A plug-in electric eco friendly sportscar’);
insert into SALES_PROJECTIONS values (1066, ‘Domestic’, ‘A new sports-car with premium turbo accelleration.’);
4) Connect as a user with lbacsys access and create a policy called ols_govproj using a column name lb_col and default option of no control.
Then create the following level components for the policy:
LEVEL NUMBER SHORT NAME LONG NAME
10 TDS Top_Drawer_Secret
9 TS Top_Secret
8 S Secret
7 C Confidential
6 P Privileged
2 UC Unclassified
1 PK Public_Knowledge
NOTE: All users should be able to read data with their own access AND all access levels below.
Apply the policy to the SALES_PROJECTIONS table
5) Give the following access levels to the following users:
President = Top_Drawer_Secret
vicepresident = Top_Secret
salesmanager = Secret
generalmanager = Unclassified
scott = Public_Knowledge
6) Set the following labels to the following projections
SALES_NO Label
1066 Public_Knowledge
1102 Secret
1296 Confidential
1436 Privileged
1577 Unclassified
1863 Top_Secret
1864 Top_Drawer_Secret
1895 Top_Drawer_Secret
7) Change the policy to enforce on read
8) Connect as each user, do a SELECT * ON SALES_PROJECTIONS to show what each user can access
You must submit: A screen shot of you connecting to your pluggable database as each user and then having that user run SELECT * on SALES_PROJECTIONS. So, you should have five (5) screen shots. No more, no less. I MUST see in your screenshot that you are connected to your pluggable database.
SQLPLUS PRESIDENT@president/localhost:1521/jackalbert

Categories
MySQL

1864 top_drawer_secret

1) Create a NEW pluggable database with your first initial and last name. For example, my pluggable database would be named tmacmullen. Connect to your pluggable database using the ALTER SESSION command. 2) Verify that OLS is enabled in your pluggable database. If it isn’t, then enable it and re-verify. 3) Within your pluggable database, run the following commands:
create user president identified by president;
create user vicepresident identified by vicepresident;
create user salesmanager identified by salesmanager;
create user generalmanager identified by generalmanager;
create user scott identified by tiger ;
grant create session to president, vicepresident, salesmanager, generalmanager, scott;
grant create table, unlimited tablespace to president;
3) Connect to your pdb as President and run the following table create:
CREATE TABLE SALES_PROJECTIONS (SALES_NO NUMBER, SALES_TYPE VARCHAR2(100), SALES_FIGURE NUMBER));
insert into SALES_PROJECTIONS values (1102, ‘Experimental Concep’, ‘The use of remote viewing to target the minds of diplomats through their dreams’);
insert into SALES_PROJECTIONS values (1436, ‘Hydrogen Cell’, ‘Research into weather controlling technology’);
insert into SALES_PROJECTIONS values (1577, ‘Plug-In Electric’, ‘Anti-gravity research’);
insert into SALES_PROJECTIONS values (1296, ‘Plug-In Hybrid’, ‘Attempts to induce paralysis in an enemy via mental impairment’);
insert into SALES_PROJECTIONS values (1863, ‘Gas-Electric Hybrid’, ‘Speading disinformation about UFOs’);
insert into SALES_PROJECTIONS values (1864, ‘Commercial’, ‘A fully autonomous self-driving car’);
insert into SALES_PROJECTIONS values (1895, ‘Foreign’, ‘A plug-in electric eco friendly sportscar’);
insert into SALES_PROJECTIONS values (1066, ‘Domestic’, ‘A new sports-car with premium turbo accelleration.’);
4) Connect as a user with lbacsys access and create a policy called ols_govproj using a column name lb_col and default option of no control.
Then create the following level components for the policy:
LEVEL NUMBER SHORT NAME LONG NAME
10 TDS Top_Drawer_Secret
9 TS Top_Secret
8 S Secret
7 C Confidential
6 P Privileged
2 UC Unclassified
1 PK Public_Knowledge
NOTE: All users should be able to read data with their own access AND all access levels below.
Apply the policy to the SALES_PROJECTIONS table
5) Give the following access levels to the following users:
President = Top_Drawer_Secret
vicepresident = Top_Secret
salesmanager = Secret
generalmanager = Unclassified
scott = Public_Knowledge
6) Set the following labels to the following projections
SALES_NO Label
1066 Public_Knowledge
1102 Secret
1296 Confidential
1436 Privileged
1577 Unclassified
1863 Top_Secret
1864 Top_Drawer_Secret
1895 Top_Drawer_Secret
7) Change the policy to enforce on read
8) Connect as each user, do a SELECT * ON SALES_PROJECTIONS to show what each user can access
You must submit: A screen shot of you connecting to your pluggable database as each user and then having that user run SELECT * on SALES_PROJECTIONS. So, you should have five (5) screen shots. No more, no less. I MUST see in your screenshot that you are connected to your pluggable database. SQLPLUS PRESIDENT@president/localhost:1521/tmacmullen

Categories
MySQL

Insert into sales_projections values (1296, ‘plug-in hybrid’, ‘attempts to induce paralysis in an enemy via mental impairment’);

1) Create a NEW pluggable database with your first initial and last name. For example, my pluggable database would be named tmacmullen. Connect to your pluggable database using the ALTER SESSION command. 2) Verify that OLS is enabled in your pluggable database. If it isn’t, then enable it and re-verify. 3) Within your pluggable database, run the following commands:
create user president identified by president;
create user vicepresident identified by vicepresident;
create user salesmanager identified by salesmanager;
create user generalmanager identified by generalmanager;
create user scott identified by tiger ;
grant create session to president, vicepresident, salesmanager, generalmanager, scott;
grant create table, unlimited tablespace to president;
3) Connect to your pdb as President and run the following table create:
CREATE TABLE SALES_PROJECTIONS (SALES_NO NUMBER, SALES_TYPE VARCHAR2(100), SALES_FIGURE NUMBER));
insert into SALES_PROJECTIONS values (1102, ‘Experimental Concep’, ‘The use of remote viewing to target the minds of diplomats through their dreams’);
insert into SALES_PROJECTIONS values (1436, ‘Hydrogen Cell’, ‘Research into weather controlling technology’);
insert into SALES_PROJECTIONS values (1577, ‘Plug-In Electric’, ‘Anti-gravity research’);
insert into SALES_PROJECTIONS values (1296, ‘Plug-In Hybrid’, ‘Attempts to induce paralysis in an enemy via mental impairment’);
insert into SALES_PROJECTIONS values (1863, ‘Gas-Electric Hybrid’, ‘Speading disinformation about UFOs’);
insert into SALES_PROJECTIONS values (1864, ‘Commercial’, ‘A fully autonomous self-driving car’);
insert into SALES_PROJECTIONS values (1895, ‘Foreign’, ‘A plug-in electric eco friendly sportscar’);
insert into SALES_PROJECTIONS values (1066, ‘Domestic’, ‘A new sports-car with premium turbo accelleration.’);
4) Connect as a user with lbacsys access and create a policy called ols_govproj using a column name lb_col and default option of no control.
Then create the following level components for the policy:
LEVEL NUMBER SHORT NAME LONG NAME
10 TDS Top_Drawer_Secret
9 TS Top_Secret
8 S Secret
7 C Confidential
6 P Privileged
2 UC Unclassified
1 PK Public_Knowledge
NOTE: All users should be able to read data with their own access AND all access levels below.
Apply the policy to the SALES_PROJECTIONS table
5) Give the following access levels to the following users:
President = Top_Drawer_Secret
vicepresident = Top_Secret
salesmanager = Secret
generalmanager = Unclassified
scott = Public_Knowledge
6) Set the following labels to the following projections
SALES_NO Label
1066 Public_Knowledge
1102 Secret
1296 Confidential
1436 Privileged
1577 Unclassified
1863 Top_Secret
1864 Top_Drawer_Secret
1895 Top_Drawer_Secret
7) Change the policy to enforce on read
8) Connect as each user, do a SELECT * ON SALES_PROJECTIONS to show what each user can access
You must submit: A screen shot of you connecting to your pluggable database as each user and then having that user run SELECT * on SALES_PROJECTIONS. So, you should have five (5) screen shots. No more, no less. I MUST see in your screenshot that you are connected to your pluggable database. SQLPLUS PRESIDENT@president/localhost:1521/tmacmullen

Categories
MySQL

Here is an example:

Create a relational schema for each of the following diagrams using the following notation:
Table names are shown in boldface with attributes listed in parentheses. Primary key are underlined. Forigen keys are indicated by a separate statement that indicartes the table referenced on the line immediately following the attribute list.
Here is an example:
Department (DepartmentID, DepartmentName, ManagerID)
ManagerID references Employee
Employee (EmployeeID, FirstName, LastName, HireDate, DepartmentID)
DepartmentID references Department
PerformanceReview (ReviewID, ReviewDate, ReviewScore, Notes, EmployeeID, ManagerID)
EmployeeID references Employee
ManagerID references Employee