stoolpigeon
Programmer
I am administrating a SQL Server 6.5 database for a small company.
Everybody and their brother has their hands in my tables (through linked Access tables)
As of right now I do not have the ability to change that situation.
There have been some changes in the database that I believe are happening through this avenue. But I don't have any way to prove that. I'm a programmer by trade, not a DBA, but I'm reading a lot-- so here's an idea I have come up w/and I'd like to know if this is worthwhile or if there is a more efficient way of ending up at the same place.
I was thinking that I could put a trigger on my problem table that would write to a Audit Log table. Then whenever someone makes changes I could go look at my audit table and see who did it and when.
My applications usually track this kind of information but in this case they are going around my application. Ultimately I would like to see that stop but for now- I don't have the pull to stop the management folks who have been used to this kind of free reign.
The reading I've done seems to steer away from triggers do to performance issues. I want to put the trigger on a table w/about 300,000 records and about 180 users. My machine and software are not the best in the world, though they do o.k.
Any opinions would be appreciated.
thanks,
Ron
Everybody and their brother has their hands in my tables (through linked Access tables)
As of right now I do not have the ability to change that situation.
There have been some changes in the database that I believe are happening through this avenue. But I don't have any way to prove that. I'm a programmer by trade, not a DBA, but I'm reading a lot-- so here's an idea I have come up w/and I'd like to know if this is worthwhile or if there is a more efficient way of ending up at the same place.
I was thinking that I could put a trigger on my problem table that would write to a Audit Log table. Then whenever someone makes changes I could go look at my audit table and see who did it and when.
My applications usually track this kind of information but in this case they are going around my application. Ultimately I would like to see that stop but for now- I don't have the pull to stop the management folks who have been used to this kind of free reign.
The reading I've done seems to steer away from triggers do to performance issues. I want to put the trigger on a table w/about 300,000 records and about 180 users. My machine and software are not the best in the world, though they do o.k.
Any opinions would be appreciated.
thanks,
Ron