|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Who Added Indexing to Table?Is there a script to query a table that will tell me the user that added the
Indexing or the user that changed on table on a specific date? It appears to me this is not an option in SQL 2000. Any help is appreciated. Thanks. No, SQL Server does not track this information.
Show quote "Colette" <Cole***@discussions.microsoft.com> wrote in message news:E9B9F2BF-92A2-4F31-B95E-BA1823E817E4@microsoft.com... > Is there a script to query a table that will tell me the user that added > the > Indexing or the user that changed on table on a specific date? It appears > to > me this is not an option in SQL 2000. > > Any help is appreciated. > > Thanks. If only it were possible to add triggers to system tables, then more
interesting possibilities would be available for things like custom auditing. Then again, it would also open the door for completly hosing the database. Show quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:%23S7LqHl1FHA.3124@TK2MSFTNGP12.phx.gbl... > No, SQL Server does not track this information. > > > > "Colette" <Cole***@discussions.microsoft.com> wrote in message > news:E9B9F2BF-92A2-4F31-B95E-BA1823E817E4@microsoft.com... >> Is there a script to query a table that will tell me the user that added >> the >> Indexing or the user that changed on table on a specific date? It >> appears to >> me this is not an option in SQL 2000. >> >> Any help is appreciated. >> >> Thanks. > > No, but if only the DBA or a designated database developer had rights to add
or modify database objects, then the answer would be obvious. Show quote "Colette" <Cole***@discussions.microsoft.com> wrote in message news:E9B9F2BF-92A2-4F31-B95E-BA1823E817E4@microsoft.com... > Is there a script to query a table that will tell me the user that added > the > Indexing or the user that changed on table on a specific date? It appears > to > me this is not an option in SQL 2000. > > Any help is appreciated. > > Thanks. Sadly, in most environments, everyone gets sa privileges because it's
"easier that way"... :-( Show quote "JT" <some***@microsoft.com> wrote in message news:%236WqAgl1FHA.1028@TK2MSFTNGP12.phx.gbl... > No, but if only the DBA or a designated database developer had rights to > add or modify database objects, then the answer would be obvious. If someone really wanted to simplify one's life, one could try leaving a
book of blank checks sitting on one's desk, so anyone else in the office one owed money to could just debit the account themselves without all the fuss. However, one would soon find one's life a lot more complicated. ;-P Show quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:uY6bnjl1FHA.1740@TK2MSFTNGP09.phx.gbl... > Sadly, in most environments, everyone gets sa privileges because it's > "easier that way"... :-( > > > "JT" <some***@microsoft.com> wrote in message > news:%236WqAgl1FHA.1028@TK2MSFTNGP12.phx.gbl... >> No, but if only the DBA or a designated database developer had rights to >> add or modify database objects, then the answer would be obvious. > > To answer, only the DBA(s) have access to change the table. Notice I said
plural for DBAs. Get the picture. I won't bother to try and find out the user then if SQL 2000 doesn't provide the functionality. Question: Is this a forum for snide comments or is this a forum for serious answers? If it's not a serious forum, I won't bother to ask questions here any longer... Show quote "JT" wrote: > If someone really wanted to simplify one's life, one could try leaving a > book of blank checks sitting on one's desk, so anyone else in the office one > owed money to could just debit the account themselves without all the fuss. > However, one would soon find one's life a lot more complicated. ;-P > > "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message > news:uY6bnjl1FHA.1740@TK2MSFTNGP09.phx.gbl... > > Sadly, in most environments, everyone gets sa privileges because it's > > "easier that way"... :-( > > > > > > "JT" <some***@microsoft.com> wrote in message > > news:%236WqAgl1FHA.1028@TK2MSFTNGP12.phx.gbl... > >> No, but if only the DBA or a designated database developer had rights to > >> add or modify database objects, then the answer would be obvious. > > > > > > > > Question: Is this a forum for snide comments or is this a forum for Well, were the answers useful to you, or not? Everyone has their own > serious > answers? If it's not a serious forum, I won't bother to ask questions > here > any longer... definition of "snide" and, without turning into machines or not bothering to respond at all, we cannot possibly answer in a way that guarantees we won't offend *somebody*... Someone had already provided a suitable answer to your specific technical
question, which was that SQL Server does not store the UserID of whomever creates objects, other than perhaps the owner of the table. However, sometimes questions lead to peripheral commentary and discussions. Show quote "Colette" <Cole***@discussions.microsoft.com> wrote in message news:A912521A-A949-4594-BEA0-89BB12205505@microsoft.com... > To answer, only the DBA(s) have access to change the table. Notice I said > plural for DBAs. Get the picture. I won't bother to try and find out the > user then if SQL 2000 doesn't provide the functionality. > > Question: Is this a forum for snide comments or is this a forum for > serious > answers? If it's not a serious forum, I won't bother to ask questions > here > any longer... > > > "JT" wrote: > >> If someone really wanted to simplify one's life, one could try leaving a >> book of blank checks sitting on one's desk, so anyone else in the office >> one >> owed money to could just debit the account themselves without all the >> fuss. >> However, one would soon find one's life a lot more complicated. ;-P >> >> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in >> message >> news:uY6bnjl1FHA.1740@TK2MSFTNGP09.phx.gbl... >> > Sadly, in most environments, everyone gets sa privileges because it's >> > "easier that way"... :-( >> > >> > >> > "JT" <some***@microsoft.com> wrote in message >> > news:%236WqAgl1FHA.1028@TK2MSFTNGP12.phx.gbl... >> >> No, but if only the DBA or a designated database developer had rights >> >> to >> >> add or modify database objects, then the answer would be obvious. >> > >> > >> >> >> All I can say is "I need to win the lottery and take a long vacation around
the world". Until then... Dilbert... ----------------------------------- Show quote "JT" wrote: > Someone had already provided a suitable answer to your specific technical > question, which was that SQL Server does not store the UserID of whomever > creates objects, other than perhaps the owner of the table. However, > sometimes questions lead to peripheral commentary and discussions. > > "Colette" <Cole***@discussions.microsoft.com> wrote in message > news:A912521A-A949-4594-BEA0-89BB12205505@microsoft.com... > > To answer, only the DBA(s) have access to change the table. Notice I said > > plural for DBAs. Get the picture. I won't bother to try and find out the > > user then if SQL 2000 doesn't provide the functionality. > > > > Question: Is this a forum for snide comments or is this a forum for > > serious > > answers? If it's not a serious forum, I won't bother to ask questions > > here > > any longer... > > > > > > "JT" wrote: > > > >> If someone really wanted to simplify one's life, one could try leaving a > >> book of blank checks sitting on one's desk, so anyone else in the office > >> one > >> owed money to could just debit the account themselves without all the > >> fuss. > >> However, one would soon find one's life a lot more complicated. ;-P > >> > >> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in > >> message > >> news:uY6bnjl1FHA.1740@TK2MSFTNGP09.phx.gbl... > >> > Sadly, in most environments, everyone gets sa privileges because it's > >> > "easier that way"... :-( > >> > > >> > > >> > "JT" <some***@microsoft.com> wrote in message > >> > news:%236WqAgl1FHA.1028@TK2MSFTNGP12.phx.gbl... > >> >> No, but if only the DBA or a designated database developer had rights > >> >> to > >> >> add or modify database objects, then the answer would be obvious. > >> > > >> > > >> > >> > >> > > > What you're talking about has already been given a name some time in the 19th
century: communism. Later that name had to be changed to: utopic communism. For obvious reasons. ML > Is there a script to query a table that will tell me the user that added A script, I don't know, but there is the old "look in the eyes of the person > the > Indexing or the user that changed on table on a specific date? It appears > to > me this is not an option in SQL 2000. > > Any help is appreciated. > > Thanks. while asking the question". There are times when it's good to rely on good ole human interactions to solve common IT issues. Good luck. Thank you, Nicolas. You're hearing me, buddy...
Show quote "Nicolas Verhaeghe - White Echo" wrote: > > Is there a script to query a table that will tell me the user that added > > the > > Indexing or the user that changed on table on a specific date? It appears > > to > > me this is not an option in SQL 2000. > > > > Any help is appreciated. > > > > Thanks. > > A script, I don't know, but there is the old "look in the eyes of the person > while asking the question". There are times when it's good to rely on good > ole human interactions to solve common IT issues. > > Good luck. > > > Just like Larry David...
Show quote > Thank you, Nicolas. You're hearing me, buddy... > > > "Nicolas Verhaeghe - White Echo" wrote: > >> > Is there a script to query a table that will tell me the user that >> > added >> > the >> > Indexing or the user that changed on table on a specific date? It >> > appears >> > to >> > me this is not an option in SQL 2000. >> > >> > Any help is appreciated. >> > >> > Thanks. >> >> A script, I don't know, but there is the old "look in the eyes of the >> person >> while asking the question". There are times when it's good to rely on >> good >> ole human interactions to solve common IT issues. >> >> Good luck. >> >> >> If it happened more than 90 days ago, there are some developers who will
honestly deny it, becuase they just flat don't remember. Show quote "Nicolas Verhaeghe - White Echo" <nospam_nicolas@whiteecho.com_nospam> wrote in message news:435931d0$0$3753$39cecf19@news.twtelecom.net... >> Is there a script to query a table that will tell me the user that added >> the >> Indexing or the user that changed on table on a specific date? It >> appears to >> me this is not an option in SQL 2000. >> >> Any help is appreciated. >> >> Thanks. > > A script, I don't know, but there is the old "look in the eyes of the > person while asking the question". There are times when it's good to rely > on good ole human interactions to solve common IT issues. > > Good luck. > > If it happened more than 90 days ago, there are some developers who will And in some places, that threshold can be 90 hours or 90 minutes, no hard > honestly deny it, becuase they just flat don't remember. rule. :-) As others have said, this is not available natively, but there are 3rd party
tools that can provide this information. Some maybe read transaction logs and thus be able to tell using old logs - most would do it on a go-forward basis. Vendors like Idera, SQLPowerTools, Qwest, etc. provide tools for this, specifically designed to meet certain auditing requirements (like SAS70, HIPAA, etc.), so they might be worth the money. [google for "sql server auditing"] Show quote "Colette" <Cole***@discussions.microsoft.com> wrote in message news:E9B9F2BF-92A2-4F31-B95E-BA1823E817E4@microsoft.com... > Is there a script to query a table that will tell me the user that added > the > Indexing or the user that changed on table on a specific date? It appears > to > me this is not an option in SQL 2000. > > Any help is appreciated. > > Thanks. Good information to know because HIPAA affects my world. I will look into
the 3rd party tools to place in my handy-dandy toolkit for the future. Thanks for the help to all four of you. Show quote "Trey Walpole" wrote: > As others have said, this is not available natively, but there are 3rd party > tools that can provide this information. > Some maybe read transaction logs and thus be able to tell using old logs - > most would do it on a go-forward basis. > > Vendors like Idera, SQLPowerTools, Qwest, etc. provide tools for this, > specifically designed to meet certain auditing requirements (like SAS70, > HIPAA, etc.), so they might be worth the money. [google for "sql server > auditing"] > > "Colette" <Cole***@discussions.microsoft.com> wrote in message > news:E9B9F2BF-92A2-4F31-B95E-BA1823E817E4@microsoft.com... > > Is there a script to query a table that will tell me the user that added > > the > > Indexing or the user that changed on table on a specific date? It appears > > to > > me this is not an option in SQL 2000. > > > > Any help is appreciated. > > > > Thanks. > > >  |
|||||||||||||||||||||||
Other interesting topics