SQL Server Performance Forum – Threads Archive

Logging PW changes?

I want to log all users who change their passwords, not necessarily the PW that they change from or to, just the fact that the sql user pw changes. Anyway that I can do this? Thanks.

---

You mean any user via EM or Query Analyzer change his sql password?
Luis Martin
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

---

yes..

---

You mean, your users have hand on such tools and are not forced to use some kind of app for this task?
–Frank
http://www.insidesql.de

---

You can create a trigger on the sysxlogins table in the master database. But like Frank has said, you probably shoudn’t allow users to do this directly. —————————–
Brad M. McGehee, MVP
Webmaster
SQL-Server-Performance.Com

---

How many users do you have? What kind of business is this (web hosting, etc?) All you need to do is set up a trace or Profiler to track: Security Audit
..Audit Login Change Password Event MeanOldDBA
[email protected] When life gives you a lemon, fire the DBA.

---

Triggers on system tables? –Frank
http://www.insidesql.de

---

Sometimes I walk on the wild side. —————————–
Brad M. McGehee, MVP
Webmaster
SQL-Server-Performance.Com

---

Hey, do you also overclock your servers? [<img src=’/community/emoticons/emotion-5.gif’ alt=’‘ />]<br />I always thought, that such triggers are NOT guaranteed to fire and that at best you run an unsupported system.<br /><br /><br /><br />–Frank<br /<a target="_blank" href=http://www.insidesql.de>http://www.insidesql.de</a><br />

---

Hey Brad, I tried creating a trigger on sysxlogins table but it said I cannot create it. I have sysadmin privileges on the database. Is there some flag that I can set or let me know what I am missing? Thanks
-Rajeev Lahoty

---

??? You can’t create a trigger on sysxlogins unless there’s a hack I don’t know about. That would be kewl though. Not sure I’d put it on production, but definitely kewl. MeanOldDBA
[email protected] When life gives you a lemon, fire the DBA.

---

I’ve never seen such hack to create trigger on system tables, as its not allowed. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

---

Even, if it is possible or allowed, it wouldn’t be supported. Methinks, that’s even more important.<br />Maybe you need to be a MVP to know about such things [<img src=’/community/emoticons/emotion-1.gif’ alt=’‘ />]<br /><br /><br />–Frank<br /<a target="_blank" href=http://www.insidesql.de>http://www.insidesql.de</a><br />

---

Just to add, I think we must divide system tables into two categories:
For example, you can do the following:
use msdb
go
create trigger test on dbo.backupfile
for insert, update, delete
as
select ‘Hallo Welt’
while
use master
go
create trigger test on dbo.sysobjects
for insert, update, delete
as
select ‘Hallo Welt’
results in
Server: Nachr.-Nr. 229, Schweregrad 14, Status 5, Prozedur test, Zeile 4
CREATE TRIGGER permission denied on object ‘sysobjects’, database ‘master’, owner ‘dbo’. That’s what I meant above. And even if it is possible to create such triggers, they are NOT guaranteed to fire.
–Frank
http://www.insidesql.de

---

]]>