debug via Enterprise Manager

Hi
I wonder if there is a trick I can use to debug what was changed in my
database (mssql2000).
The idea maybe sound stupid but my boss have got old console application
which is doing some changes in database (only in data in tables rather. I
have no code for that application and we are wondering where this appl.
writes - what changes and so on.
Any idea?
DarekHi
You may want to use SQL Profiler to see what statements the application is
sending to the database server.
John
"Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
news:eIJBW$aKGHA.216@.TK2MSFTNGP15.phx.gbl...
> Hi
> I wonder if there is a trick I can use to debug what was changed in my
> database (mssql2000).
> The idea maybe sound stupid but my boss have got old console application
> which is doing some changes in database (only in data in tables rather.
> I have no code for that application and we are wondering where this appl.
> writes - what changes and so on.
> Any idea?
> Darek
>

debug via Enterprise Manager

Hi
I wonder if there is a trick I can use to debug what was changed in my
database (mssql2000).
The idea maybe sound stupid but my boss have got old console application
which is doing some changes in database (only in data in tables rather. I
have no code for that application and we are wondering where this appl.
writes - what changes and so on.
Any idea?
Darek
Hi
You may want to use SQL Profiler to see what statements the application is
sending to the database server.
John
"Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
news:eIJBW$aKGHA.216@.TK2MSFTNGP15.phx.gbl...
> Hi
> I wonder if there is a trick I can use to debug what was changed in my
> database (mssql2000).
> The idea maybe sound stupid but my boss have got old console application
> which is doing some changes in database (only in data in tables rather.
> I have no code for that application and we are wondering where this appl.
> writes - what changes and so on.
> Any idea?
> Darek
>

debug

Hi all,
I go into SQL QueryAnalyzer for debugging. Expand Stored Procedures for my
database, right click the SP I want and select Debug. It prompts me for the
parameters and I enter them. It seems to execute the procedure and give me
@.RETURN_VALUE =0. I go through the procedure and set breakpoints at every
line. I hit F5 for GO and it runs right through it again and gives me the
return value. It does not break at my break points.
Sql Server is running under a domain user account, not the local system
account.
Server is SQL Server Enterprise Edition, version 8.00.818 (SP3). Client is
8.00.194, Windows XP, SP2.
I've read Sql Server Tools Troubleshooting, but everything is ok.
Anyone have an idea why I can't debug?Please post the stored procedure so that we can better assist you. Without
being able to see what you are working with, we are just guessing.
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"meri2" <meri2@.gmail.com> wrote in message
news:OLFOQzwqGHA.1796@.TK2MSFTNGP03.phx.gbl...
> Hi all,
> I go into SQL QueryAnalyzer for debugging. Expand Stored Procedures for my
> database, right click the SP I want and select Debug. It prompts me for
> the parameters and I enter them. It seems to execute the procedure and
> give me @.RETURN_VALUE =0. I go through the procedure and set breakpoints
> at every line. I hit F5 for GO and it runs right through it again and
> gives me the return value. It does not break at my break points.
> Sql Server is running under a domain user account, not the local system
> account.
> Server is SQL Server Enterprise Edition, version 8.00.818 (SP3). Client is
> 8.00.194, Windows XP, SP2.
> I've read Sql Server Tools Troubleshooting, but everything is ok.
> Anyone have an idea why I can't debug?
>
>|||It happens with all the stored procedure.
thanks
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:OdmWh1zqGHA.5008@.TK2MSFTNGP05.phx.gbl...
> Please post the stored procedure so that we can better assist you. Without
> being able to see what you are working with, we are just guessing.
> --
> Arnie Rowland
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "meri2" <meri2@.gmail.com> wrote in message
> news:OLFOQzwqGHA.1796@.TK2MSFTNGP03.phx.gbl...
>