| Author |
Table locks / logging
|
|
| Mike M 2006-10-28, 7:14 pm |
| I have a client who is repeatitly looking at SQL tables in SQL manager when
our software is making an attempt to write and update those tables.
I'd like to impliment a logging program that will log each time the table is
opened in SQL manager and also log any attempts that our software makes to
update those tables.
Any ideas on where I can start?
| |
| Arnie Rowland 2006-10-28, 7:14 pm |
| Which version of SQL Server? (2000 or 2005)
You can create a profile trace for blocks. There are third party tools that
can facilitate this task as well.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Mike M" <Mike M@discussions.microsoft.com> wrote in message
news:894B8BA5-206D-4BEE-96FB- 9C81D7F7036E@microso
ft.com...
>I have a client who is repeatitly looking at SQL tables in SQL manager when
> our software is making an attempt to write and update those tables.
>
> I'd like to impliment a logging program that will log each time the table
> is
> opened in SQL manager and also log any attempts that our software makes to
> update those tables.
>
> Any ideas on where I can start?
| |
| Mike M 2006-10-28, 7:14 pm |
| SQL server 2000
Can anything in Profiler do this?
"Arnie Rowland" wrote:
> Which version of SQL Server? (2000 or 2005)
>
> You can create a profile trace for blocks. There are third party tools that
> can facilitate this task as well.
>
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
>
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> You can't help someone get up a hill without getting a little closer to the
> top yourself.
> - H. Norman Schwarzkopf
>
>
> "Mike M" <Mike M@discussions.microsoft.com> wrote in message
> news:894B8BA5-206D-4BEE-96FB- 9C81D7F7036E@microso
ft.com...
>
>
>
| |
| David Browne 2006-10-31, 12:15 am |
|
"Mike M" <Mike M@discussions.microsoft.com> wrote in message
news:894B8BA5-206D-4BEE-96FB- 9C81D7F7036E@microso
ft.com...
>I have a client who is repeatitly looking at SQL tables in SQL manager when
> our software is making an attempt to write and update those tables.
>
> I'd like to impliment a logging program that will log each time the table
> is
> opened in SQL manager and also log any attempts that our software makes to
> update those tables.
>
> Any ideas on where I can start?
Start by asking your client not to do that. Then find out why your client
needs to do that. Then provide your client with a means of accomplishing
that that doesn't adversely impact your application. Perhaps you could
provide some views with (NOLOCK) that your client can open instead?
David
| |
| Sue Hoegemeier 2006-10-31, 12:15 am |
| Microsoft has a script for monitoring blocking:
How to monitor blocking in SQL Server 2005 and in SQL Server
2000
http://support.microsoft.com/?id=271509
-Sue
On Fri, 27 Oct 2006 14:15:01 -0700, Mike M
<MikeM@discussions.microsoft.com> wrote:
[color=darkred]
>SQL server 2000
>
>Can anything in Profiler do this?
>
>"Arnie Rowland" wrote:
>
|
|
|
|