[au123]

Hi Friends

I want desperately ur help regarding database testing process in
detail. I mean I wanted to know how this database testing are
performed in real-time scenario. like

1. Database testing process in real-time
2. Level of database testing
3. what are the tools used for database testing and their detail etc...
4. anything which is necessary, u think

Plz try to post these information asap. That could be great help for
me.

thanks and regards

Ashok K Prasad

[au123]

Hi Friends

I am looking for SQL server FAQs desperately.
I expect faster response especially from Spoorthi and Other Sr member of this group.

Plz try to post these information asap. That could be great help for
me.

thanks and regards

Ashok K Prasad

[sk_kireeti]

Hi Ashok,

Don't expect reply from any ONE member of the forum to be very quick. Poeple will reply you only when they got some free time from their work.

Belive you can understand.

Thanks,
Krishna

[slinkanand]

Hi,

here are some faq's, if u know the answers for below questions, try to give reply for each one, if not will give the answers..

1. how to Increase, the size of Database in sql server 2000, in terms of GB size
2. can we have multiple recordset from stored procedure
3. Advance features of sqlserver2005 over sql server 2000?
4.Which is the best option used to move database from one server to another serve on same network?a) Import
5. What are the new enhancements in sqlserver 2005?
6. What is DESCRIBE command in SQL Server?What is its purpose?How to use it?
7. what is #table in sqlserver ?what is ##table in sqlserver?
8. how can we use rollback in sqlservre
9. What is the difference between Inner join and full outer join in terms of the Number of rows returne
10. what is fill factor, where it can be used?







Cheer's
Anand

[sunnyhup]

Database tests are supported via ODBC using the following functions:
SQLOpen, SQLClose, SQLError, SQLRetrieve, SQLRetrieveToFile, SQLExecQuery, SQLGetSchema and SQLRequest.
You can carry out cursor type operations by incrementing arrays of returned datasets.
All SQL queries are supplied as a string. You can execute stored procedures for instance on SQL Server you could use “Exec MyStoredProcedure” and as long as that stored procedure is registered on the SQL Server database then it should execute however you cannot interact as much as you may like by supplying say in/out variables, etc but for most instances it will cover your database test requirements

A sample database test could look like this:

Sub main
' Declarations
'
Dim connection As Long
Dim destination(1 To 50, 1 To 125) As Variant
Dim retcode As long
Dim query as String
Dim outputStr as String
connection = SQLOpen("DSN=SblTest",outputStr,prompt:=3)
'
' Execute the query
query = "select * from customer"
retcode = SQLExecQuery(connection,query)

' retrieve the first 50 rows with the first 6 columns of each row into
' the array destination, omit row numbers and put column names in the
' first row of the array

retcode = SQLRetrieve(connection:=connection,destination:=destination, columnNames:=1,rowNumbers:=0,maxRows:=50, maxColumns:=6,fetchFirst:=0)

' Get the next 50 rows of from the result set
retcode = SQLRetrieve(connection:=connection,destination:=destination,columnNames:=1,rowNumbers:=0,maxRows:=50, maxColumns:=6)
' Close the connection
retcode = SQLClose(connection)
End Sub

[kiran2710]

Hi,

Check dis , may b u will get an idea..

[Spoorthi]

sorry for the late reply au123....just 2day i've cn ur post.
here r some sql-syntax...SQL Syntax.doc

[sunnyhup]

Some more stuff...........

Most multi-user applications today use some form of persistence, and more often than not, that persistence is done using a relational database management system (RDBMS), such as Oracle, SQL Server, MySQL, or DB2. This article will discuss some quick and easy ways that a tester can start to perform 'grey box' or 'white box' testing against the databases in their application, which will allow them to more easily uncover problems with the database.

Functionality of the database is one of the most critical aspects of your application's quality; problems with the database could lead to data loss or security breaches, and may put your company at legal risk depending on the type of data you are storing.

Considering how important the database is to the success of applications, it is surprising how little attention is focused on database testing. In my experience, the biggest barrier is that most testers simply don't have time to directly test the database, so they end up focusing their testing efforts on testing via the GUI.

Referential Integrity:
As the name implies, relational databases store data as well as information about the relationships between various data. Data records will often contain references to other data records in other tables. Maintaining integrity of these relationships is critical; if relationships between data become broken, the function of your application could be compromised.

Database developers use a number of different tools to provide referential integrity including constraints (rules within the database which require references to be maintained), triggers (processes which are 'triggered' by changes to specific data) and application code (logic contained in the application which describes how to manipulate the data).

Depending on which methods your database developers have used, the database will be vulnerable to different sorts of referential integrity issues. Constraints are the most effective way to maintain integrity, since the RDBMS will prevent anyone from making changes that will break integrity. Maintaining referential integrity via application code is the most risky (but also most flexible) approach, since you are relying on the programmers' code to make every modification correctly.

As a tester, the first thing to do is find out how referential integrity is being maintained in your database. One of the best ways to do this is via a schema, which is a visual diagram of all the tables in the database. You can ask your database administrator (DBA) or the development team for a schema, or you can create one yourself via tools like Visio.

The tools used by the developers and/or DBA to create the database will also show you any constraints and triggers used in the database, and are usually pretty easy to set up.

Once you know how integrity is being maintained, you can then begin to analyze how it could be broken, and what the risks are in your application. For instance, if your application relies on the application code to maintain integrity, then you will want to make sure that every piece of code that modifies the data is thoroughly tested and doesn't introduce data integrity issues. If the application relies on triggers, then you will want to have tests which cause every trigger to be fired, and make sure that the data is being modified correctly by the triggers.

Security:
There are a number of ways that security of the database is maintained. The most common ways are via usernames and passwords, or via integration with a directory such as LDAP. Some of the key questions to consider are:

• Does each user of the application have a separate password to the database, or is their a shared database account for all users of the application?
• What is the permission-level of the account(s) used to access the database?
• What interface is used to manage the accounts used to access the database? What other ways are there to access the database using the same login information as the application?

In practice, many applications require that each user has a different account at the application-level, but there is a single account shared by all users to access the database. As a tester, it's important to understand how the database is being accessed, with what level of permission, and to make sure that all stakeholders are aware of the risks being introduced via the chosen methods.

The best resources for testing the security of your database are the developers/DBAs, and the management tools provided by your RDBMS. Developers can tell you how the database is being accessed, and the RDBMS can provide information about the privileges associated with the accounts your application is using.

[sunnyhup]

also check this link

http://www.ashgrovesoftware.com/index.htm

[P.Gita]

Hi Kireeti

I can understand ur msg that u conveyed me that people need free time to answer my question, but I have interview on 27/09/06 so I was in hurry, as I got this information on 3 days back and no time to wait. Ok

Anyway, I was not through, hope for the best for next time by ur grace.

thanks and sorry

Ashok

Originally Posted by sk_kireeti

Hi Ashok,

Don't expect reply from any ONE member of the forum to be very quick. Poeple will reply you only when they got some free time from their work.

Belive you can understand.

Thanks,
Krishna

[simhadri44]

this is really very bad.it doesnt mean that u can say what ever u want.if u can give help then help them else leave it what is the need to say that if we r free then we can give reply .of course what u said is right but dont say like that

Originally Posted by sk_kireeti

Hi Ashok,

Don't expect reply from any ONE member of the forum to be very quick. Poeple will reply you only when they got some free time from their work.

Belive you can understand.

Thanks,
Krishna

[simhadri44]

gita dont get dissapointed by keerti words he dosent mean that but he a very useful member so take it light

[AjayKumar.Kataram]

thanks to all...

[aforarun]

Thanks a lot to all... gr8 team work....I am very to see this effort from all......