Saving the db state for bug reproduction and tests

[George Homorozeanu]

We are developing a .net database driven application. The application is
already quite complex and uses at time aprox. 150 data tables stored in the
MSSQL 2000 database server. Our application has multiple modules. Some
customers already use some modules while we currently developing more
modules.

The problem that we are starting to have is the difficulty to save the
database state in case of a bug. We need the database state in order to
reproduce and correct the bug and also to write and run some tests to be
sure the bug never occurs.

The simplest way is to use the MS SQL 2000 database back-up functionality.
Another way could be to use SQL Server Tools (like Red Gate, etc.)

I am also a student and I tried to find some answers in the academic field
(books, asking some other students/assistants) but nothing to find. It seems
that a solution can only be found in practice. That's why I ask the people
who had this kind of problem to help me to get closer to a solution. How are
you resolving this kind of problems? Which tools can be used to automate
this process?

Any ideas, literature, links could help me a lot.

Thanks,

George Homorozeanu.

[Marina]

Sorry, I don't understand why you need to save the database state, or what
that really even means.

Presumably, this bug is reproduceable on their system.
So, when a user is experiencing a particular bug, they can back up the
database, send it to you, and then tell you what steps need to be taken to
reproduce it.

"George Homorozeanu" <ge************ ****@hotmail.co m> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

We are developing a .net database driven application. The application is
already quite complex and uses at time aprox. 150 data tables stored in
the MSSQL 2000 database server. Our application has multiple modules. Some
customers already use some modules while we currently developing more
modules.

The problem that we are starting to have is the difficulty to save the
database state in case of a bug. We need the database state in order to
reproduce and correct the bug and also to write and run some tests to be
sure the bug never occurs.

The simplest way is to use the MS SQL 2000 database back-up functionality.
Another way could be to use SQL Server Tools (like Red Gate, etc.)

I am also a student and I tried to find some answers in the academic field
(books, asking some other students/assistants) but nothing to find. It
seems that a solution can only be found in practice. That's why I ask the
people who had this kind of problem to help me to get closer to a
solution. How are you resolving this kind of problems? Which tools can be
used to automate this process?

Any ideas, literature, links could help me a lot.

Thanks,

George Homorozeanu.