Drop Table
Support Forum for database administrators and web based access to important newsgroups related to databasesI 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?
Post Follow-up to this messageWhich 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?
Post Follow-up to this messageSQL 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 tha t > 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 th e > top yourself. > - H. Norman Schwarzkopf > > > "Mike M" <Mike M@discussions.microsoft.com> wrote in message > news:894B8BA5-206D-4BEE-96FB- 9C81D7F7036E@microso ft.com... > > >
Post Follow-up to this message"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
Post Follow-up to this messageMicrosoft 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: >SQL server 2000 > >Can anything in Profiler do this? > >"Arnie Rowland" wrote: >
Post Follow-up to this message
Show a Printable Version
Email This Page to Someone!
Receive updates to this thread