well, there are two issues here, about null values :

there are none.

select count(*) from  #repl_text_holder where sp_text is null  - returns 0

and even if there were any I run this...

Yes, you are right, this is not the most perplexing example. How about this one?

It takes values from #repl_text_holder (with two columns line_no (int identity (1,1)) and sp_text varchar)...

I use

Processor: % Processor Time (total and for each processor)

System: processor Queue Length (on a dual processor machine spikes up to 9)

Physical Disk: Disk Write (and Read) Bytes/sec

System: Context...

May be my original post was a bit misleading. This is not a server-client scenario. Even though one of the machines is a win 2003 server, both of them are...

The original query you posted seems like an elegant solution. If you have the time, may be you could explain the logic behind this segment:

(

run_time * 9

+ run_time...

thanks,

That's actually what I wind up doing.

Thanks, that explains it.

I am not sure what is the logic of the script that you posted . The one I posted has a lot of code, but the logic is simple:

take two...

Try this script:

use msdb

go

select

left(b.run_date,4)+'/'+right(left(b.run_date,6),2)+'/'+right(b.run_date,2) as run_date,

a.name,

b.step_id,

b.step_name,

convert(varchar,(convert(datetime,(cast((CASE

WHEN len(b.run_time)=6 THEN LEFT(b.run_time,2)

WHEN len(b.run_time)=5 THEN LEFT(b.run_time,1)

ELSE 0

END) AS VARCHAR(2))+':'+

cast((CASE

WHEN len(b.run_time)>=4 THEN LEFT(RIGHT(b.run_time,4),2)

WHEN len(b.run_time)=3 THEN LEFT(b.run_time,1)

ELSE 0

END) AS VARCHAR(2))+':'+RIGHT(b.run_time,2)))),108) as start_time,

Convert(varchar,

(

convert(datetime,(cast((CASE

WHEN len(run_time)=6 THEN LEFT(run_time,2)

WHEN...

It would not be so terrible if the result was only that DB files do not get defragmented while anything else wouldn't, and of course we are talking about off...

I'm getting the same error, i.e.

Error: 17883, Severity: 1, State: 0

Process 0:0 (c68) UMS Context 0x0D1536E8 appears to be non-yielding on Scheduler 0.

plus

SQL Server has encountered 8 occurrence(s) of...