The depth of DB testing depends on once requiremets.Generally Its falls in WhiteBox part of testing where we will be checking database fields and tables.All values that appear in frontend and the values that are send from frond end should be reflected(stored) in the database.For checking this fields you will use sql satatement diffrent toold are used for this (SQL tools,TOD,SQL +) [img]images/icons/smile.gif[/img] .Through this u can connect to database and query the each fields.
Testing starts from simple query to checking stored procedure.
Do you mean an specific database that is the back store of a business app?
Or do you mean a database engine itself?
Manually is a no-no from the get go. If in addition to the time penalty of compiling queries, and of I/O operations, you add the delay of manual labor, you will encounter that your tests per second rate will suffer, and a lot.
Involving a GUI is also a no-no. The penalty of fighting for screen repaint is too expensive also.
If the subject is a simple database that will be a backstore of a business app, you have a pretty well defined and constrained test subject.
Just limit yourself to those tables and layout.
If on the other hand you are working on a db engine itself, you will need to get creative and mind your bytes and cpu cycles.