To all, especially Lynn,

Thanks for helping me solve this. I did a LOT of reading, and made the changes. I also modified the code and created a stored...

It really is the simple things that trip you up. What can I say except thank you for all the help. As I said earlier, this is the...

Now it works:-) So that begs the question, how come it worked on your setup? The difference is KILLING me! I have tried every which way to...

Lynn, your code works insofaras the output required. It just processes one row (assuming you remove the group by clause, and I don't see whay that would make any...

This is the error message running your code as is:-

Msg 306, Level 16, State 2, Line 102

The text, ntext, and image data types cannot be compared or sorted, except when...

These are the top 35 records straight out of the syslog database.

|CALL_END |0 |0 ...

You are correct. I did a select top 10 because I know those records are clean, and it would not process any data at all, even after I modified...

Still fails. Try removing the data from the callconnect_datetime segment and just filling it full of the same number of spaces and run it again. I get the...

Lynn,

I have been reading up on this all day. I'm not the only one asking this question. It appears that for some, the WHILE loop is the only...

Bill, you are doing the same thing in your code as everyone else appears to be doing. You supply the srting to process and "Voila!" it works. Yet...

Well, I tried everything. The code does not loop through the records. It just produces 1 entry and finishess. Oddly enough ALL the examples I have looked...

So, after another few hours of reading and just trying to get something to work, I still hit a brick wall. I'm sure that I am running the code...

Yep, as I thought. Take out the Group By statement at the end, you get a message related to time/date conversion and a NULL value being eiminated at some...

Lynn, out of the last 7 days data this is the only discrepency I have found. That second field is blank in 11 records out of 7000, but it...

Does this have anything to do with the fact I'm using SQL 2008 and nchar is no longer supported, or am I just trying to be clever googling the error...