Re: MSSQL 2000 Activity Logs
From: Uri Dimant (urid_at_iscar.co.il)
Date: 03/22/04
- Next message: Julie: "Copy or insert Columns from a table in another Database, How?"
- Previous message: Mario Splivalo: "Re: MSSQL 2000 Activity Logs"
- In reply to: Mario Splivalo: "Re: MSSQL 2000 Activity Logs"
- Next in thread: Mario Splivalo: "Re: MSSQL 2000 Activity Logs"
- Reply: Mario Splivalo: "Re: MSSQL 2000 Activity Logs"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 22 Mar 2004 13:58:12 +0200
Mario
You can run SQL Server Profile to capture those commands and save it to the
table.
As far as I know with SQL Server 2005 you will be able to define a trigger
on a table or even on a database ( I am not certain) for drop table events.
"Mario Splivalo" <majk@fly.srk.fer.hr> wrote in message
news:slrnc5tjfd.p0k.majk@fly.srk.fer.hr...
> On 2004-03-22, Hari Prasad <hari_prasad_k@hotmail.com> wrote:
> > Hi,
> >
> > I feel that SQL Server wont store any information of that sort by
default.
> >
> > If you keep enabled the profiler then you can see the command DROP
DATABASE
> > , by using that you can identify the user who has dropped it. But old
data
> > can not be retrived.
> >
>
> Yes, when I have the profiler running, then I can see what's going on.
But,
> most of the time, I don't keep the profiler up.
>
> Is there a way to tell SQL server 'do, please, keep logs of who and when
> created/dropped/attached/deatached databases'?
>
> Mike
> --
> "I can do it quick. I can do it cheap. I can do it well. Pick any two."
>
> Mario Splivalo
> msplival@jagor.srce.hr
- Next message: Julie: "Copy or insert Columns from a table in another Database, How?"
- Previous message: Mario Splivalo: "Re: MSSQL 2000 Activity Logs"
- In reply to: Mario Splivalo: "Re: MSSQL 2000 Activity Logs"
- Next in thread: Mario Splivalo: "Re: MSSQL 2000 Activity Logs"
- Reply: Mario Splivalo: "Re: MSSQL 2000 Activity Logs"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|