I've never got round to really investigating the problem, but I had a similar on a win 2000 ADV server machine running SQL 2000.

What I found was if I closed...

Thanks Brian, meant to add that at the end, about replying on something which should be fixed.

NGS Software released a paper on threat profiling, which includes a hack on gaining admin rights via sql agent to gain admin rights. It may be worth taking a look...

Linked servers can behave differently depending on the query

The UK SSUG has a nice example page on it

(http://www.sqlserverfaq.com/)

Search for the word 'linked', and pick the article called ...

If I remember correctly (don't quote me)

adding 'and' to the 'on' statement is more ansi-92 compliant, which sql server is optimised for.

You may want to see if changing your sql to (below) is any better

SELECT *

FROM tblA

INNER JOIN tblB ON tblA.LinkID = tblB.LinkID

and tblb.currentinfo >= 10000

Not to worry. I picked up nextgenss on that.

Hence the fixed code being posted on there site 🙂

Just a quick fix to the t-sql (which David from NGSoftware has now put live at the above link)

use master

go

revoke execute on [sp_MSSetServerProperties] to [public]

go

revoke execute on [sp_MSsetalertinfo] to [public]

go

...

The best bet would be to monitor the server.

ie cpu, memory, pagefile etc.

If the cpu is being heavly used/max'ed out getting another cpu would help, but if the server...

Also there is a little bug in S2K sp1 (fixed in sp2) where you need to give the proxy account access to the sql temporary directories

What version of sql server are you using?

I would suggest a server side trace, which in sql 2000 you create with the following stored procuedures

sp_trace_create

sp_trace_setevent

sp_trace_setstatus

books online (the...

If you audit logons on the sql server you can add an alert (eg add an alert on error no 18454/55) which runs only when a named account logs on....

I had a simular problem with running a DTS from the xp_cmdshell (using the proxy account)

It was a bug with SP1 (Q302828). It may be worth setting the permissions on...

How about testing it with a test perl script.

Something which writes to a log file. That way you can test if the perl is executing correctly.

DTS is a client side tool. Have you got perl installed on the pc you are running the dts from