InnoDB uses row and table-level locks, but row locks are not escalates
InnoDB locks only those rows that are updated
InnoDB only uses row locks, not page or table-level locks
InnoDB row locks may be escalated to page or table-level locks
InnoDB uses row-level or table-level locks depending on the number of rows affected
第1题:
A.因为InnoDB在一个日志中保存到所有主键的指针,短的主键使日志小
B.因为InnoDB使用主键定位二级索引,短的主键使查询快
C.因为InnoDB使用主键定位表记录,短的主键使查询快
D.因为InnoDB使用主键定位表,短的主键使查询快
第2题:
简述MyISAM与innoDB存储引擎有何差别?
第3题:
How does DB2 protect the integrity of indexes when data is updated?()
第4题:
Which three statements about subqueries are true?()
第5题:
Following a server crash, the automatic recovery of InnoDB fails. How would you begin to manually repair the InnoDB tables?()
第6题:
Which two statements are true about InnoDB auto-increment locking?()
第7题:
The InnoDB engine has a feature known as clustered indexes. Which three statements are true about clustered indexes as used in InnoDB?()
第8题:
Which two statements are true regarding single row functions?()
第9题:
The auto-increment lock can be a table-level lock
InnoDB never uses table-level locks
Some settings for innodb_autoinc_lock_mode can help reduce locking
InnoDB always protects auto-increment updates with a table-level lock
第10题:
To maintain control of updated rows for commit processing
To ensure only committed changes are altered by another application
To allow two applications to update the same row of data simultaneously
To prevent multiple applications from accessing the same data simultaneously
第11题:
A primary key must exist for creation of a clustered index
A clustered index allows fulltext searching within InnoDB
The first unique index is always used as a clustered index and not a primary key
A clustered index provides direct access to a page containing row data
If no indexes exist, a hidden clustered index is generated based on row IDs
A primary key is used as a clustered index
A clustered index is a grouping of indexes from different tables into a global index for faster searching
第12题:
Use a Dynamic Management View to check for locks.
Use a Dynamic Management View to check for blocked queries.
Use a Dynamic Management View to check for long-running queries.
Use a Dynamic Management View to check the size and maximum size of the database.
第13题:
Onboard a Ro-Ro vessel many decks are used for the carriage of both rolling and container cargoes,as such it is most useful if a deck socket accepts both ______.
A.Twist-Locks and lashing hooks
B.Container locks and bridge fittings
C.Bridge fittings and lashing hooks
D.Twist-locks and container locks
第14题:
Which two of statements are true?()
第15题:
Which of the following best describes how locks are used in DB2?()
第16题:
What is true regarding InnoDB locking?()
第17题:
User Scott has updated the salary of one of the employees in the EMPLOYEES table and has not committed the transaction. What are the two types of locks that this scenario would lead to?()
第18题:
Which two statements describe good practices for an application developer to reduce lockingconflicts in Oracle database()
第19题:
A SQL Azure database generates an error when a row is inserted into any table in the database. No error is generated when a row is deleted. You need to recommend an approach for locating the source of the errors. What should you recommend?()
第20题:
Start the server with the – innodb_recover_options option set to FORCE
Start the server with the – innodb_force_recovery option set to a non-zero value
Start the server as usual, and then execute the REPAIR TABLE command
Start the server as usual, and then execute the CHECK TABLE command
第21题:
A single row subquery can retrieve only one column and one row.
A single row subquery can retrieve only one row but many columns.
A multiple row subquery can retrieve multiple rows and multiple columns.
A multiple row subquery can be compared by using the “>” operator.
A single row subquery can use the IN operator.
A multiple row subquery can use the “=” operator.
第22题:
因为InnoDB在一个日志中保存到所有主键的指针,短的主键使日志小
因为InnoDB使用主键定位二级索引,短的主键使查询快
因为InnoDB使用主键定位表记录,短的主键使查询快
因为InnoDB使用主键定位表,短的主键使查询快
第23题:
null lock on the row being updated
null lock on the table containing the row
ROW SHARE lock for the row being updated
ROW EXCLUSIVE lock for the row being updated
shared row-exclusive lock for the row being updated
a shareable table lock for the table containing the row
exclusive table-level lock for the table containing the row