Dbm 438 Week 6 Ilab

Submitted by: Submitted by

Views: 10

Words: 1268

Pages: 6

Category: Other Topics

Date Submitted: 10/08/2016 11:37 PM

Report This Essay

DBM 438 Week 6 iLab

Copy and Pate below link into your Browser to buy tutorial

http://hwpool.com/product/dbm-438-week-6-ilab/

DBM 438 Week 6 iLab

Laboratory Procedures

DeVry University

College of Engineering and Information Sciences

I. OBJECTIVES

1. Take a look at the process of creating and managing users in the database, as well as how user management helps support security.

II. ASSUMPTIONS

As a result of this lab, you will have gained a working knowledge of how to create users, grant privileges, and use those privileges to access data in the database.

III. PROCEDURE

1. For each lab it will be necessary for you to create an output file that will capture all of your commands and work within your MySQL session. The steps for doing this are as follows.

438. Create a folder on the S: drive of your Windows VM named DBM438. This will be where you will save all of your session output files.

439. Log into a MySQL session at the ‘root’ level. This will be the default beginning level for all of your iLab sessions.

440. At the mysql> prompt, type the following: tee s:\dbm438\labxoutputfile.log, where the ‘x’ is the lab number.

441. Press enter. You should receive a ‘Logging to ‘s:\dbm438\labxoutputfile.log’ message.

442. To stop writing to the log you simply type note at the prompt.

443. Unfortunately, you cannot copy this file from your VM to your host computer, so you will need to open the file, copy the contents, and then paste them into the Lab Report document for this lab under the Lab Results section. If you use Courier New 9pt. font, formatting will look just like in the session.

NOTE: If you have to stop your lab session and then go back later you need to be sure that you are using the same file name for your output file. Doing so will allow MySQL to append the new work to the end of the file thus allowing you to save all of your lab output into one file. If you do end up using two or more...