Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Security

Author  Topic 

tfountain
Constraint Violating Yak Guru

491 Posts

Posted - 2009-02-24 : 08:55:53
Is there a way to identify who created a database user? Assume it was created by someone creating a server login and granting that login access to a database, but later deleted the server login. This leaves an orphaned database user. Is there a way to identify who created this database user originally?

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2009-02-24 : 12:17:14
I don't think you can. What if it was restored from other server?
Go to Top of Page

tfountain
Constraint Violating Yak Guru

491 Posts

Posted - 2009-02-24 : 12:34:55
It was not restored from another server. What about the default trace in SQL Server 2005 SP2? Are there any reports that will identify such changes?
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2009-02-24 : 12:36:49
quote:
Originally posted by tfountain

It was not restored from another server. What about the default trace in SQL Server 2005 SP2? Are there any reports that will identify such changes?



Yes it will log but it won't have things logged which was done weeks before.
Go to Top of Page

tfountain
Constraint Violating Yak Guru

491 Posts

Posted - 2009-02-25 : 10:34:57
Which report would it be? It does not appear to be captured under the schema changes report.
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2009-02-25 : 11:10:16
quote:
Originally posted by tfountain

Which report would it be? It does not appear to be captured under the schema changes report.



Yes it won't even be captured with default trace. You need to use SQL profiler or Server -side trace to detect that.
Go to Top of Page

tfountain
Constraint Violating Yak Guru

491 Posts

Posted - 2009-02-25 : 16:16:07
quote:
Originally posted by sodeep

quote:
Originally posted by tfountain

Which report would it be? It does not appear to be captured under the schema changes report.



Yes it won't even be captured with default trace. You need to use SQL profiler or Server -side trace to detect that.


The default trace is a server side trace...
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2009-02-25 : 16:18:25
quote:
Originally posted by tfountain

quote:
Originally posted by sodeep

quote:
Originally posted by tfountain

Which report would it be? It does not appear to be captured under the schema changes report.



Yes it won't even be captured with default trace. You need to use SQL profiler or Server -side trace to detect that.


The default trace is a server side trace...




Incorrect. Read about Default trace. It is black box for sql server.
Go to Top of Page

tfountain
Constraint Violating Yak Guru

491 Posts

Posted - 2009-02-25 : 16:29:50
quote:
Originally posted by sodeep

quote:
Originally posted by tfountain

quote:
Originally posted by sodeep

quote:
Originally posted by tfountain

Which report would it be? It does not appear to be captured under the schema changes report.



Yes it won't even be captured with default trace. You need to use SQL profiler or Server -side trace to detect that.


The default trace is a server side trace...




Incorrect. Read about Default trace. It is black box for sql server.



And it is implemented as a server side trace. A tree can be an Oak, Pine or even a Banzai, but is still a tree.

References:
http://www.mssqltips.com/tip.asp?tip=1111
http://blogs.techrepublic.com.com/datacenter/?p=156
http://blogs.technet.com/vipulshah/archive/2007/04/16/default-trace-in-sql-server-2005.aspx
http://msdn.microsoft.com/en-us/library/ms175513(SQL.90).aspx

Oh, there's more but I hope this conveys the point.
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2009-02-25 : 16:50:06
quote:
Originally posted by tfountain

quote:
Originally posted by sodeep

quote:
Originally posted by tfountain

quote:
Originally posted by sodeep

quote:
Originally posted by tfountain

Which report would it be? It does not appear to be captured under the schema changes report.



Yes it won't even be captured with default trace. You need to use SQL profiler or Server -side trace to detect that.


The default trace is a server side trace...




Incorrect. Read about Default trace. It is black box for sql server.



And it is implemented as a server side trace. A tree can be an Oak, Pine or even a Banzai, but is still a tree.

References:
http://www.mssqltips.com/tip.asp?tip=1111
http://blogs.techrepublic.com.com/datacenter/?p=156
http://blogs.technet.com/vipulshah/archive/2007/04/16/default-trace-in-sql-server-2005.aspx
http://msdn.microsoft.com/en-us/library/ms175513(SQL.90).aspx

Oh, there's more but I hope this conveys the point.



Like you are saying person can be male or female but still human beings. Default trace doesn't give any overheads at all and doesn't satisfy your need for server-side trace.So there is difference.
Go to Top of Page

tfountain
Constraint Violating Yak Guru

491 Posts

Posted - 2009-02-26 : 09:34:02
quote:
Originally posted by sodeep
Like you are saying person can be male or female but still human beings. Default trace doesn't give any overheads at all and doesn't satisfy your need for server-side trace.So there is difference.



sodeep, you are truly a tool. I just wanted to put that out there.

First, I do not recall stating the default trace incurs any overhead. Regardless of the fact that it does or does not is moot. This is some connection you made in your own head.

Second, my only statement is that the implementation of the default trace is as a server side trace. Plain and simple. Query sys.traces for yourself.

Third, this conversation is so far removed from my original inquiry so do me a favor and discontinue this conversation.
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2009-02-26 : 09:43:46
quote:
Originally posted by tfountain

quote:
Originally posted by sodeep
Like you are saying person can be male or female but still human beings. Default trace doesn't give any overheads at all and doesn't satisfy your need for server-side trace.So there is difference.



sodeep, you are truly a tool. I just wanted to put that out there.

First, I do not recall stating the default trace incurs any overhead. Regardless of the fact that it does or does not is moot. This is some connection you made in your own head.

Second, my only statement is that the implementation of the default trace is as a server side trace. Plain and simple. Query sys.traces for yourself.

Third, this conversation is so far removed from my original inquiry so do me a favor and discontinue this conversation.




Reviewing your response from long time, I can say that your don't infact understand or takes people advice.Anyway Whatever. Why do you post when you don't trust on people response. Stop posting.. simple. Read Booksonline carefully for Default Trace.
Go to Top of Page

tfountain
Constraint Violating Yak Guru

491 Posts

Posted - 2009-02-26 : 13:03:16
I welcome others suggestions. Most of them are valid, well thought out and make sense. It's just yours I have an issue with. Yours are usually invalid, not thought out and don't make sense. 9 times out of 10 (much like this one), you reply with what equates to spam just to increase your post count. I do not see the logic in that.

Mods, do me a favor and kill this thread. I'll repost my original question.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-02-26 : 13:31:46
I'm not sure why sodeep said "Incorrect" as tfountain was definitely correct on that statement.

I am locking this topic.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page
   

- Advertisement -