SQL server does not keep any logs for this purpose.

SQL server has a replication monitor in Enterprise manager. It has detailed logs for all agents.

Check what account (windows account) you are using to run sql server service. It seems that someone changed the password. Try another account or local system account.

Maybe not exactly what you want, In sql server the function ::fn_virtualfilestats and tables master.dbo.spt_monitor,

master.dbo.sysperfinfo can provide IO activity infromation and other performance counter.

These are ODBC format data type, from BOL:

ODBC Datetime Format

The ODBC API defines escape sequences to represent date and time values, which ODBC calls timestamp data. This ODBC...

In terms of SQL 2000, BEGIN TRAN and BEGIN DISTRIBUTED TRAN do NOT have big difference.

MSDTC will promote a local transaction to distributed transaction if multiple servers (even multiple dbs on SAME...

1) "But why does BOL says that "Sp_OA" requires "sysadmin" role then, when I can simply grant execute to any regular user?"

What BOL said is the DEFAULT permission.

2) "Also,...

Forget one thing. If u just need to use sp_OA.. sps, not the xp_cmdShell and you do not have ActivX script job owned by the login, the proxy account is not necessary.

You need three steps:

1) Add this login to master db

2) GRANT EXECUTE sp_OACareate on [user name of the login in master db]

3) define a proxy account for non-sysadmin login

You need to run sp_grantdbaccess to add the login to the database first. Then  you can add the user to the db role

Alan, what you need to do is to create the job on the fly in the trigger. When you call

EXECUTE @ReturnCode = msdb.dbo.sp_add_jobstep,

pass your sp/xp and parameter in the @command...

when u create the SP, you need:

SET ANSI_NULLS ON

GO

before your create procedure your_sp_name.

In the event, inlcudes SP:Starting and/or SP:Complete;

In the filters, find the TextData, under like type '%SP5%'.

Run the trace.

It's different between Connection time out and lock time. Connection time out is to control the maximum time that a client can wait for the response. If the time is expired...

I don't think SQL server ever has this feature.

However, if you right click SQL Agent-->Jobs and in the context menu select all tasks --> generate script, it will generate scripts for ALL jobs