What should you recommend?

You need to recommend a solution for the error handling of sp3. The solution must minimize the amount of
custom code required. What should you recommend?
Case Study:
A)
Datum Case B
Overview:
General Overview
A)
Datum Corporation has offices in Miami and Montreal.The network contains a single Active Directory forest named adatum.com. The offices connect to each other by
using a WAN link that has a 5-ms latency.
A)
Datum standardizes its database platform by using SQL Server 2012 Enterprise edition.
Databases Each office contains databases named Sales, Inventory, Customers, Products, Personnel, and Dev.
Servers and databases are managed by a team of database administrators. Currently, all of the database
administrators have the same level of permissions on all of the servers and all of the databases.
The Customers database contains two tables named Customers and Classifications. The following graphic
shows the relevant portions of the tables:

The following table shows the current data in the Classifications table:

The Inventory database is updated frequently. The database is often used for reporting. A full backup of the
database currently takes three hours to complete.
Stored Procedures
A stored procedure named sp1 generates millions of rows of data for multiple reports. Sp1 combines data from
five different tables from the Sales and Customers databases in a table named Table1.
After Table1 is created, the reporting process reads data from Table1 sequentially several times. After the
process is complete, Table1 is deleted.
A stored procedure named sp2 is used to generate a product list. The product list contains the names of
products grouped by category. Sp2 takes several minutes to run due to locks on the tables the procedure
accesses. The locks are caused by sp1 and sp3.
A stored procedure named sp3 is used to update prices. Sp3 is composed of several UPDATE statements
called in sequence from within a transaction. Currently, if one of the UPDATE statements fails, the stored
procedure fails.
A stored procedure named sp4 calls stored procedures in the Sales, Customers, and Inventory databases. The
nested stored procedures read tables from the Sales, Customers, and Inventory databases. Sp4 uses an
EXECUTE AS clause. All nested stored procedures handle errors by using structured exception handling.A stored procedure named sp5 calls several stored procedures in the same database. Security checks are
performed each time sp5 calls a stored procedure.
You suspect that the security checks are slowing down the performance of sp5.
All stored procedures accessed by user applications call nested stored procedures. The nested stored
procedures are never called directly.
Design Requirements:
Data Recovery
You must be able to recover data from the Inventory database if a storage failure occurs. You have a Recovery
Time Objective (RTO) of 5 minutes.
You must be able to recover data from the Dev database if data is lost accidentally. You have a Recovery Point
Objective (RPO) of one day.
Classification Changes
You plan to change the way customers are classified. The new classifications will have four levels based on the
number of orders. Classifications may be removed or added in the future.
Management requests that historical data be maintained for the previous classifications.
Security
A group of junior database administrators must be able to manage security for the Sales database. The junior
database administrators will not have any other administrative rights. A. Datum wants to track which users run
each stored procedure.
Storage
A)
Datum has limited storage. Whenever possible, all storage space should be minimized for all databases and
all backups.
Error Handling
There is currently no error handling code in any stored procedure. You plan to log errors in called stored
procedures and nested stored procedures. Nested stored procedures are never called directly.

You need to recommend a solution for the error handling of sp3. The solution must minimize the amount of
custom code required. What should you recommend?
Case Study:
A)
Datum Case B
Overview:
General Overview
A)
Datum Corporation has offices in Miami and Montreal.The network contains a single Active Directory forest named adatum.com. The offices connect to each other by
using a WAN link that has a 5-ms latency.
A)
Datum standardizes its database platform by using SQL Server 2012 Enterprise edition.
Databases Each office contains databases named Sales, Inventory, Customers, Products, Personnel, and Dev.
Servers and databases are managed by a team of database administrators. Currently, all of the database
administrators have the same level of permissions on all of the servers and all of the databases.
The Customers database contains two tables named Customers and Classifications. The following graphic
shows the relevant portions of the tables:

The following table shows the current data in the Classifications table:

The Inventory database is updated frequently. The database is often used for reporting. A full backup of the
database currently takes three hours to complete.
Stored Procedures
A stored procedure named sp1 generates millions of rows of data for multiple reports. Sp1 combines data from
five different tables from the Sales and Customers databases in a table named Table1.
After Table1 is created, the reporting process reads data from Table1 sequentially several times. After the
process is complete, Table1 is deleted.
A stored procedure named sp2 is used to generate a product list. The product list contains the names of
products grouped by category. Sp2 takes several minutes to run due to locks on the tables the procedure
accesses. The locks are caused by sp1 and sp3.
A stored procedure named sp3 is used to update prices. Sp3 is composed of several UPDATE statements
called in sequence from within a transaction. Currently, if one of the UPDATE statements fails, the stored
procedure fails.
A stored procedure named sp4 calls stored procedures in the Sales, Customers, and Inventory databases. The
nested stored procedures read tables from the Sales, Customers, and Inventory databases. Sp4 uses an
EXECUTE AS clause. All nested stored procedures handle errors by using structured exception handling.A stored procedure named sp5 calls several stored procedures in the same database. Security checks are
performed each time sp5 calls a stored procedure.
You suspect that the security checks are slowing down the performance of sp5.
All stored procedures accessed by user applications call nested stored procedures. The nested stored
procedures are never called directly.
Design Requirements:
Data Recovery
You must be able to recover data from the Inventory database if a storage failure occurs. You have a Recovery
Time Objective (RTO) of 5 minutes.
You must be able to recover data from the Dev database if data is lost accidentally. You have a Recovery Point
Objective (RPO) of one day.
Classification Changes
You plan to change the way customers are classified. The new classifications will have four levels based on the
number of orders. Classifications may be removed or added in the future.
Management requests that historical data be maintained for the previous classifications.
Security
A group of junior database administrators must be able to manage security for the Sales database. The junior
database administrators will not have any other administrative rights. A. Datum wants to track which users run
each stored procedure.
Storage
A)
Datum has limited storage. Whenever possible, all storage space should be minimized for all databases and
all backups.
Error Handling
There is currently no error handling code in any stored procedure. You plan to log errors in called stored
procedures and nested stored procedures. Nested stored procedures are never called directly.

A.
Use the @@ERROR variable in the nested stored procedures.

B.
Use a TRY CATCH block in the called stored procedures.

C.
Use the @@ERROR variable in the called stored procedures.

D.
Use the RAISERROR command in the nested stored procedures.

Explanation:
A)
Datum Case A



Leave a Reply 0

Your email address will not be published. Required fields are marked *