StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1006794
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-06-17T12:46:21.760
FavoriteCount
0
LastActivityDate
2009-06-17T12:46:21.760
LastEditDate
LastEditorUserId
0
OwnerUserId
105929
ParentId
1004149
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
SQL Server does not store explicit information about who created or modified an object. There is information in the metadata catalog about who is the owner of a given object, or to what schema does the object belong to: <pre><code>select * from sys.objects where object_id = object_id('<object name>'); </code></pre> Depending on the object type either the principal_id is populated with the database principal ID of the owner, or the schema_id is populated with the Id of the schema to which the object belongs. All schemas have an owner and which can be retrieved from the metadata catalog: <pre><code>select * from sys.schemas </code></pre> However note that these will only reveal the owner of the object. The owner does not necessarily means the user that created it or modified it. Ownership of objects can be changed during creation or after creation with the <a href="http://msdn.microsoft.com/en-us/library/ms187359.aspx" rel="nofollow noreferrer">ALTER AUTHORIZATION</a> statement, making identification by ownership unreliable at best. Also all members of sysadmin role map to the same database principal, dbo, in every database. To properly identify the the user that created an object you should deploy auditing methods, but that require prior deployment of the audit. Some forensics can be done after the fact if audit was not deployed: <ul> <li>You can dig into the log file, Paul Randal <a href="http://www.sqlskills.com/BLOGS/PAUL/post/Finding-out-who-dropped-a-table-using-the-transaction-log.aspx" rel="nofollow noreferrer">has an example in his recent blog</a>.</li> <li>You can look into the <a href="http://technet.microsoft.com/en-us/library/cc293615.aspx" rel="nofollow noreferrer">default trace</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSQL 2005 Find Out Who Created a View
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRemus Rusanu
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.