Vista - I am looking for information on parsing log files (text)

I am looking for information on parsing log files (text).

Check out Microsoft's LogParser 2.2


-----
Shay Levi
$cript Fanatic
http://scriptolog.blogspot.com

rferrisx wrote:This might get you started:
http://www.microsoft.com/technet/scr.../payette1.mspx

Might need to be more specific though...

Marco

--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp

PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:
http://marcoshaw.blogspot.com

You might also look at Scott Hanselman's recent blog - http://feeds.feedburner.com/~r/Scott...owerShell.aspx


Joe Brinkman
----------------------------------------------------------
DotNetNuke Corp. ASP.Net MVP
www.dotnetnuke.com
----------------------------------------------------------

"Shay Levi" <no@xxxxxx> wrote in message
news:8766a944bc578c9ea017bee4006@xxxxxxDude, you totally beat Flowering Weeds to the punch on this one! Way to go!
:-)

--
Keith

Hello Keith Hill [MVP],
go! :-)You should have put a screen warning there, Keith!

Thanks for the laugh.

Karl

Thanks for all of this. I know about log parser and will reconsider using
it. This is more of the post I am looking for. I want to maximize the dot
net interface and PS ability to store very large log files (GBs) in memory
as a variable to produce specific output and charts. I will reconsider log
parser as a useful tool, but quite frankly I think PS can do more for me.
Help not run X and gnu plot on my windows box....

Thanks again,

Ryan

"Joe Brinkman" wrote:

It really depends on the format of the Log file... Powershell is pretty good
at parsing natively.

Brandon Shell
---------------
Blog: http://www.bsonposh.com/
PSH Scripts Project: www.codeplex.com/psobject

r> Thanks for all of this. I know about log parser and will reconsider
r> using it. This is more of the post I am looking for. I want to
r> maximize the dot net interface and PS ability to store very large log
r> files (GBs) in memory as a variable to produce specific output and
r> charts. I will reconsider log parser as a useful tool, but quite
r> frankly I think PS can do more for me. Help not run X and gnu plot
r> on my windows box....
r>
r> Thanks again,
r>
r> Ryan
r>
r> "Joe Brinkman" wrote:
r>

"rferrisx"
Okay all, the ball is in your hands!

Show us all how PowerShell is the right
way (tool) here and not Microsoft's data
parser, Log Parser 2.2 (even when ran
within PowerShell) using Log Parser's
own .NET classes ("to maximize the dot
net interface - and charts")?

So what is the PowerShell only (mmm define
PowerShell too) way of doing the above?

"rferrisx" <rferrisx@xxxxxx> wrote in message
news:753FCC93-E652-497D-846B-6D970DFB5CD5@xxxxxxWe poke fun at Flowering Weeds for his undaunted support of LogParser but
honestly, in this case, he's right. LogParser, as a dedicated tool for
handling log files (even large ones) will give you much better performance
than using PowerShell in the way you have indicated. For instance, you say
you want to store GBs in a single variable. Well on 32 bit windows, each
process only gets 2 GB of virtual address space (unless you use the /3GB
boot.ini switch). Even then, I've seen processes top out at a little over 1
GB of private memory usage before die-ing with OutOfMemoryExceptions.

Now if you are on x64 then perhaps PowerShell is worth giving a go but I
suspect LogParser will have much better performance.

--
Keith