At times I have had jobs that did nothing but monitor other jobs, either to check that they started or completed at the appropriate time. Hard to prevent the sharing...

I don't see why not. Are you sure you have connectivity on the second one? I'd suggest just stopping the one that is working while you work on the other....

I'd have to check on merge, rarely use it. For transactional I think you only need to add the column if you're doing updating subscribers. In SQL2K you can add...

Or look at ways to reduce tempdb usage - I think you'd be better off in the long run. Maybe leverage the table valued functions available in SQL2K.

Andy

Maybe its a scoping issue? It is a local or global temp?

Andy

I had no issues when I applied it.

Andy

Works fine on my machine, using this statement:

SELECT *

FROM OPENROWSET('MSDASQL','Driver={Microsoft Text Driver (*.txt; *.csv)};DBQ=\\eg\c$;','SELECT * FROM [Details#txt]') AS t

Perhaps its a permission error?

Andy

Try an alias for the instance.

Andy

I'd suggest considering a couple others; Admin911 by some guy named Brian Knight and another about prepping for the SQL 2000 Designing exam by Mr Jones himself.

Shameless plug!

Andy

Hey Paul,

Not sure I have the answers, but I at least have comments! EM might be a start, though I have to wonder how it would hold up at that...

Glad you find it helpful. Please visit often and ask questions when you have them!

Andy

Take a look at the maintenance wizard, it lets you configure how many days are kept on disk.

Andy

I dont mind the local variables as much, I tend to do much the same as you suggest - a holdover from coding in VB for me. Changing local variables...

It is possible. You could use xp_cmdshell to issue a a 'delete filename'.

Andy

This applies both 7 and 2000, or 2000 only?

Andy