Ans: By writing scripting procedure in the TCL we can connect to the database and we can test data base and queries.
The exact process should be:
1)connect to the database
db_connect("query1",DRIVER={driver name};SERVER=server_name;
UID=uidname;PWD=password;DBQ=database_name ");
2)Execute the query
db_excecute_query("query1","write query u want to execute");
-Condition to be mentioned-

3)disconnect the connection
db_disconnect("query");

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 need 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: You have to do the following for writing the database test cases.

1. First of all you have to understand the functional requirement of the application thoroughly.

2. Then you have to find out the back end tables used, joined used between the tables, cursors used (if any), triggers used(if any), stored procedures used (if any), input parameter used and output parameters used for developing that requirement.

3. After knowing all these things you have to write the test case with different input values for checking all the paths of SP.

One thing writing test cases for backend testing not like functional testing. You have to use white box testing techniques.

Ans: To find the second largest salary amount from employee table
Select max (salary) from employees
Where pin< (select max (salary) from employees)

Ans: Data Integrity checks should be performed. IF the database schema is 3rd normal form, then that should be maintained. Check to see if any of the constraints have thrown an error. The most important command will have to be the DELETE command. That is where things can go really wrong.
Most of all, maintain a backup of the previous database.

Ans:
Verify the data in the database with respect to frontend transactions

Verify the constraint (primary key, forien key ....).

Verify the performance of the procedures.

Verify the triggers (execution of triggers).

Verify the transactions (begin, commit, rollback).

Ans: It depends on your application interface.

1. If your application provides view functionality for the entered data, then you can verify that from front end only. Most of the time Black box test engineers verify the functionality in this way.

2. If your application has only data entry from front end and there is no view from front end, then you have to go to Database and run relevant SQL query.

3. You can also use database checkpoint function in Win Runner.

Ans: It can be verified by querying the common audit log where we can able to see the triggers fired.

Ans: Observing that operations, which are operated on front-end is effected on back-end or not.
The approach is as follows:
While adding a record front-end check back-end that addition of record is effected or not. So same for delete, update. Ex: Enter employee record in database front-end and check if the record is added or not to the back-end (manually).

Ans: You have to do the following for writing the database test cases.
1. First of all you have to understand the functional requirement of the application thoroughly.
2. Then you have to find out the back end tables used, joined used between the tables, cursors used (if any), triggers used(if any), stored procedures used (if any), input parameter used and output parameters used for developing that requirement.
3. After knowing all these things you have to write the test case with different input values for checking all the paths of SP.
One thing writing test cases for backend testing not like functional testing. You have to use white box testing techniques.