hello I think this might be a SQL query problem. I need to extract info from two different files in different folder (same server) the first file contains the filename and the second file with that filename contains the errormessage I need. Is this possible? I have tried to merge the pash and the filename...

Hello all, Is there any way of stating another character for line-delimiter except of \n? For example: &512| text1 text2 text3 &123| text4 text5 with a line-delimiter of '&' and a seperator of | will return: Fld1 Fld2 === === 512 text1\ntext2\ntext3 123 text4\ntext5 Thanks, Itay

Hi, I gave input of around 35 GB and expected output is around 1 GB but it is throwing out of memory exception. even though i have around 12 GB of Free space in my system. Please guide as soon as possible For reference i have attached the error screen in word doc

Hi, I was trying to use log parser to query TEXTLINE from file. My machine stopped responding for long time. Files were in 100 MB range. I waited for 2 hour approx then I restarted my machine. Then I tried to start log parser again, but it throws error (attached screenshot). We need to have x64 bit version...

I have text logs I am trying to query. I have developed a vbs script which is working to some degree but I need help in how to get the results to show up in a variable so when I write it to a file I can format it. The current vbs looks like this: LogDir = " \\SERVER1\f$\Progra~1\Symantec\SMSSMTP\logs...

Could you not do this: "Select Text into 'Path to output file' From 'Path to input file' Where text like '%Msg%' OR text like '%Time %'" -i:textline -o:csv I think that would get you what you wanted.

Alas Logparser will not do this for you ... it is very simple to do with vbscript Graham

I have a text file with data similar to this: ID : INFO-1000706 Time : 2006-11-07 14:43:30.416 GMT+02 Process : psin_listener.exe (ID:8696) Thread : (ID:4040) Msg : The Listener agent for i3 is starting on port 22222. ======================================== ID : INFO-1001701 Time : 2006-11-07 14:43...

Did you try the generic W3C input instead of the IISW3C?

Oh. :/ That's kinda rough because it means you will have to stick with TEXTLINE or try my regex input format to be able to read those log files. Hopefully the next version of LogParser will have a more flexible #Fields based input format.