Is there such a tool?

> Is there a tool, which could register all changes in a database? For
> example, a program connects to the database and makes some changes. The
tool
> would give as the results: what tables were affected and even what rows
were
> inserted, modified or deleted.
Have a look on our MSSQL LogManager.
http://www.upscene.com/products/audit/mssqllm_main.htm
Best Regards,
Thomas Steinmaurer
LogManager Serie - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database and MS SQL Server
Upscene Productions
http://www.upscene.com
Vycka wrote:
> Is there a tool, which could register all changes in a database? For
> example, a program connects to the database and makes some changes.
> The tool would give as the results: what tables were affected and
> even what rows were inserted, modified or deleted.
OmniAudit does exactly that. http://www.krell-software.com
Steve Troxell
Krell Software
|||This tool is pretty handy, but...
I installed it to my computer, then I did "prepare database for logging".
After that my program that uses the database got out of order. It started to
behave unpredictably so I decided not to use the tool and I did "unprepare
database from logging". In my opinion after doing this the database should
become clean of this program. But unfortunately now my database program
stopped working at all throwing error messages saying that "could not find
stored procedure dbo.P_INSERTINTOLOGTABLE". What is this? As far as I can
see it is related with triggers that were not deleted by that tool (MS SQL
LogManager).
Please Explain me, how to make my program (and database) work smoothly
exactly as it was?
Thank you for your help
"Thomas Steinmaurer" <t.steinmaurer@._no_upscene_spam_.com> wrote in message
news:#$Vsc2THEHA.1944@.TK2MSFTNGP11.phx.gbl...
> tool
> were
> Have a look on our MSSQL LogManager.
> http://www.upscene.com/products/audit/mssqllm_main.htm
>
> Best Regards,
> Thomas Steinmaurer
> LogManager Serie - Logging/Auditing Suites supporting
> InterBase, Firebird, Advantage Database and MS SQL Server
> Upscene Productions
> http://www.upscene.com
>
|||Hi,

> This tool is pretty handy, but...
> I installed it to my computer, then I did "prepare database for logging".
> After that my program that uses the database got out of order. It started
to
> behave unpredictably so I decided not to use the tool and I did "unprepare
> database from logging".
Can you elaborate what you mean with "got out of order", please?

> In my opinion after doing this the database should
> become clean of this program.
Right.

> But unfortunately now my database program
> stopped working at all throwing error messages saying that "could not find
> stored procedure dbo.P_INSERTINTOLOGTABLE". What is this? As far as I can
> see it is related with triggers that were not deleted by that tool (MS SQL
> LogManager).
The Unprepare-Wizard should take care of that. And so far, it did.
Do you see any tables/views starting with MSSQLLM$... at all?
If the logging trigger weren't remove, then you might find them via
the following name template (btw, that depends, what trigger naming
conventions you've used during the Prepare).
For example:
TRI_<table_name>_L_<event_type>
A concrete example would be:
TRI_ADDRESS_L_D or
TRI_ADDRESS_L_I or
TRI_ADDRESS_L_U
What Microsoft SQL Server are you using?
Best Regards,
Thomas Steinmaurer
LogManager Serie - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database and MS SQL Server
Upscene Productions
http://www.upscene.com
|||"Thomas Steinmaurer" <t.steinmaurer@._no_upscene_spam_.com> wrote in message
news:OQOcEEZHEHA.3564@.TK2MSFTNGP09.phx.gbl...
> Hi,
logging".
started
> to
"unprepare
> Can you elaborate what you mean with "got out of order", please?
My program is a very complex document and contact managemet program. So when
I tried to add a new document, or add a new contact to the database in stead
of getting common notification window I got another program window
absolutely out of point. It is difficult to explain everything when you
don't know my program. I didn't made this program, it is a big commercial
program developed by a company. It was made on Visual Studio ASP.NET.
>
> Right.
find
can
SQL
> The Unprepare-Wizard should take care of that. And so far, it did.
> Do you see any tables/views starting with MSSQLLM$... at all?
Now three tables and one view was dropped after "unprepare" procedure.
But in SysObjects table I found six triggers related with two tables from my
DB. I Dropped them by writing seperate querries. Now everything works fine -
no error messages, no unaccountable program behaviour.
I appreciate your help, thank you.

> If the logging trigger weren't remove, then you might find them via
> the following name template (btw, that depends, what trigger naming
> conventions you've used during the Prepare).
> For example:
> TRI_<table_name>_L_<event_type>
> A concrete example would be:
> TRI_ADDRESS_L_D or
> TRI_ADDRESS_L_I or
> TRI_ADDRESS_L_U
> What Microsoft SQL Server are you using?
I'm Using MS SQL Server 2000 08.00.0760

>
> Best Regards,
> Thomas Steinmaurer
> LogManager Serie - Logging/Auditing Suites supporting
> InterBase, Firebird, Advantage Database and MS SQL Server
> Upscene Productions
> http://www.upscene.com
>
|||> > > This tool is pretty handy, but...
> logging".
> started
> "unprepare
> My program is a very complex document and contact managemet program. So
when
> I tried to add a new document, or add a new contact to the database in
stead
> of getting common notification window I got another program window
> absolutely out of point.
I guess, you don't have an error message or a screenshoot of that
window, do you? I'm just trying to fix a possible issue, if there is
anything to fix at all.

> Now three tables and one view was dropped after "unprepare" procedure.
I did some extensive testing, and I couldn't break the Unprepare
process in any way. Existing log trigger get removed automatically,
before the Unprepare wizard removes logging metadata. It works
here, as expected.

> But in SysObjects table I found six triggers related with two tables from
my
> DB. I Dropped them by writing seperate querries. Now everything works
fine -
> no error messages, no unaccountable program behaviour.
> I appreciate your help, thank you.
You are welcome!
Best Regards,
Thomas Steinmaurer
LogManager Serie - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database and MS SQL Server
Upscene Productions
http://www.upscene.com