Free 1Z0-882 Exam Dumps Preview

What are two ways in which normalizing your tables helps improve performance In MySQL?

Assume the user has just connected to the MySQL server.

What is the result of the query SELECT @ a?

Which two keywords cannot be used in multi-table deletes?

The contents of the parent and child tables are:

The child table has the parent_id column that has a foreign key constraint to the id column of the parent
table with ON DELETE CASCADE clause.
Consider the command WHERE id =1;

What is the effect of the above command?

Assume your connection uses SQL mode ANSI_QUOTES.

Which two statements cause a syntax error?

Consider the table t1 created with this statement: CREATE TABLE t1(
id INT NOT NULL AUTO_INCREMENT
PRIMARY KEY,
Name CHAR (20)
ENGINE=InnoDB;
After inserting three rows, the table contains:

These commands are executed:

DELETE FROM t1 WHERE id=200;

INSERT INTO t1 (name) VALUES (`pluto'):

Which data set is inserted in the table?

Consider the statements:
Mysql> drop function foo;
ERROR 1305 (420000): FUNCTION test, foo does not exist Mysql > show warnings;

Mysql> get diagnostics condition 2 @msg=MESSAGE_TEXT;

What is the result of the final statement?

Inspect the CREATE TABLE below: Mysql> CREATE TABLE foo (a INT, PRIMARY KEY (a)) ENGINE =InnoDB; Query Ok, 0 rows affected, 2
warnings (0.11 sec)

Mysql> SHOW WARNINGS;

Which two is true connecting the meaning of the warnings?

What is true about the contents of the INFORMATION_SCHEMATA table?

An application packs several fields of information into the details column of the table sensors. The first six characters of that data represent a location code.

Example: "ABCDEFOO ooozzz comments will be here FIELDS----FIELD64"

Given the query pattern: SELECT----FROM sensors WHERE details LIKE `ABCDEF

Which three ALTER TABLE commands enable the optimizer to user an index for this WHERE patterns?

Consider the content of the class and student tables: Class

Which three queries produce the same result?

You have two tables:
CREATE TABLE department (
Department_ID int unsigned NOT NULL auto_increment PRIMARY KEY, Department_Name varchar(12)
NOT NULL
) ENGINE=InnoDB
CREATE TABLE employee (
Employee_Number int unsigned NOT NULL PRIMARY KEY, Employee_Name varchar(10) NOT NULL,
Department_ID int unsigned DEFAULT NULL,
FOREIGN KEY (Department ID) REFERENCES Department (Department_ID) ON UPDATE SET NULL
ON DELETE CASCADE
) ENGINE= InnoDB
The tables have the data: Department

You execute the statement: REPLACE INTO department (Department_ID, Department_Name) VALUES (1, `Admin');

What data is in the employee table after the statement?

Consider the statement:

CREATE TABLE t1 (a INT) PARTITION BY KEY

/*150611 ALGORITHM = 1*/

What does this statement do?

Your application is running slow.

Which two features provide information that help to identify problems?

You are connected to a MySQL server and using a prepared statement. You accidentally exit your session.

What will happen if you log back in to use your prepared statement?