Any way logging or tracking method for dropped tables

Most of my tables is dropped after they are created. I cannot tell when this
happen. This include stored procedures as well. I checked the maintenance job
and none are dropping tables or stored procedures.
The funny part is my tables and stored procedure which is published out as
articles remain and not dropped as others. Why?
Is there any logs or tracking that can be put in place to find out who
deleted my tables?
Paul,
I'm using SQL Server 2000 so I guess I would need to use the log explorer
tool. Are there any recommendation which I can try first?
Another question which hopefully can narrow down my suspect here is..Do you
think replication dropped the tables?
Cheers,
Philip
"Paul Ibison" wrote:

> If you're on SQL Server 2005 you could set up ddl triggers to log who/what
> is performing the drops. Alternatively a 3rd party log explorer tool will
> have the info in it.
> HTH,
> Paul Ibison
>
>
|||Replication by default will drop tables on the subscriber, but never on the
publisher so i'd look elsewhere. The reason replicated objects haven't been
dropped is probably because once they're published, they have to be removed
from the publication to be allowed to be dropped, so that distinguishes them
from your other objects. (this is a bit of guesswork, but it makes sense).
Lumigent Log Explorer will audit DDL commands to help you figure out who did
the drop (http://lumigent.com/products/le_sql_faq.html#_I_do_not). If it
happens regularly then you could use profiler yourself to monitor for these
drops.
HTH,
Paul Ibison

Any good link on tracking memory issues

I have always found it hard to figure out if SQL has memory issues using
tools like perfmon,etc..
Its easy for CPU and IO i.e. high CPU or disk queue, but could never figure
out how to go about memory.
Yes some may say look at DBCC memorystatus,etc.. but that things greek ;)
Can someone help or maybe theres some documentation that talks about
tracking memory usage,etc. for SQL Server..Hi Hassan,
Two excellent sources I know are:
Paper "Troubleshooting Performance Problems in SQL Server 2005"
http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx
Chapter 1, book "Inside SQL Server 2005: Query Tuning and Optimization"
by Kalen Delaney, et al.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Hassan" wrote:
> I have always found it hard to figure out if SQL has memory issues using
> tools like perfmon,etc..
> Its easy for CPU and IO i.e. high CPU or disk queue, but could never figure
> out how to go about memory.
> Yes some may say look at DBCC memorystatus,etc.. but that things greek ;)
> Can someone help or maybe theres some documentation that talks about
> tracking memory usage,etc. for SQL Server..
>
>