Ans: No. I do not think so. Since the requirement seems to be ambiguous. The SRS should clearly mention the performance or transaction requirements i.e. It should say like 'A DB retrieval rate of 5 micro sec'.

Ans: The SQL JOIN statement is used to combine the data contained in two relational database tables based upon a common attribute. Basically there are two types of Joins 1. Inner Join An inner join is a join that selects only those ...  

Ans: No. I do not think so. Since the requirement seems to be ambiguous. The SRS should clearly mention the performance or transaction requirements i.e. It should say like 'A DB retrieval rate of 5 micro sec'.

Ans: Yes, Requirements should represent exact functionality of AUT.

First of all you have to analyze the requirement very thoroughly in terms of functionality. Then you have to think about suitable test case design techniques (Black Box design techniques like Equivalence Partitioning, Boundary Value Analysis, Error Guessing and Cause Effect Graphing) for writing the test case.

By these concepts you should write a test case which should have the capability of finding the absence of defects.

Ans: To find the second largest salary amount from employee table

select max (salary) from employees
where pin < (select max (salary) from employees)

Ans: The tester needs to go through the requirement of the need of the stored procedure.
Checks whether the indexes, joins, deletions, update are correct in comparison with tables mentioned in stored procedure. Ensure that the stored procedure is following the standards.
Check the calling procedure name, calling parameters and expected responses for different sets of input parameters.
Run the procedure with database client programs like TOAD or Mysql or Query Analyzer etc.
Rerun the available procedures by sending different parameters, and check the results against expected values.
Concluding to the process, automate the tests with Win Runner.

Ans: The following is the process to test triggers and procedures:
1. Open the database project in Solution Explorer.
2. Click on Database Schema View from View menu
3. Open the project folder from Schema View menu, which contains the objects that are needed to be tested.
4. Right click on the object that is to be tested, and Create Unit Tests is to be clicked.
A dialog box by name Create Unit Tests appears. It displays all the folders and objects in the database project and the check box for the selected object is checked.
5. Select the Create a new Language Test Project
6. Choose to either insert the unit test in an existing test class or create a new test class and click on OK
7. For the project to be configured, Project configuration dialog box appears. Using this dialog box, the test project settings can be configured.
This requires the information like database connection for executing test results, data generation plan that is to be run before unit tests are run is to be specified.
8. Configure the project and click on OK

Ans:         1. Perform the following while involving in data load testing:         2. Know about the data tables, columns and associated constraints, data types  &nb...  

Ans:
The stages of database testing are:
2. Verifying the data in the database
3. Verifying the constraints (primary and foreign keys)
4. Verifying the performance of the procedure
5. Verifying the transactions (begin, commit, rollback)
6. Verifying the triggers by executing them

Ans: The following are the ways to write the test cases for database testing:
1. Understand the functional requirement of the application
2. Find out the tables used, joins used between tables, cursors used, triggers used, stored procedures used, input parameters used and output parameters used.
3. Write the test case with multiple input values for checking all paths.
Writing test cases for back end testing, one should use white box testing as opposed to functional testing.