I can't think of any way to do this other than brute force.  You need a list of computers on your network.  You need a user that is in each...

A few thoughts:  is the server where you scheduled the job running at high CPU?  Is the server where you scheduled the job not either the source for the data...

I'm going to take a stab.  Try:

@Message + '  FieldName to:' + isnull(Cast(Inserted.FieldName AS Varchar(10)), ' NULL') 

I think that Access is updating all of the columns, even if you only change...

You can put your sql into an ExecuteSQL task, using the SQL Server connection as your connection.

To deal with your other issue, you will need to use global variables and output...

Pete, you nailed something that I hadn't thought about.  This query would work quickly with an index on the CPTCODE column.

I assumed the join was correct in the original.

Try inner join.

select d.field5, d.field2,

d.field6, d.crc, d.lc,

QuestionID, AnswerID

FROM  (Select DialID , 1 as QuestionID, KP1 AS AnswerID

from Digits

where KP1 is not null

union all

Select DialID , 2, KP2 AS AnswerID

from Digits

where...

What is the correct value if the condition is false?  If I read the code right, the else condition is that Last Sale Date = 0.  So what is the meaning...

The query is slow because it requires SQL Server to do something that it isn't really built for.  Basically, for every record it has to build a string.  It does...

Is this a one time population of a table or is this a query that you are running frequently?  If it is a one time population, then you aren't going to get...

I would prefer to compare dates.  You could recast the string date value back to date.  Otherwise, I prefer to use the YYYYMMDD format.

What do you think that this result will look like?

This will work with a small number of records or where you don't need for it to work fast:

declare @PNO int

declare @OtherPCPCode varchar(3000)

create table #newPCP (

PNO int not null,

PCPTCode int...

We had a similar problem and had to apply a hotfix:

http://support.microsoft.com/kb/814509/

When you run the query in query analyzer you have the same security context as when the dts package failed (same NT login, same SQL login, whether the NT login...