Question; AWK to analyze Windows Server 2k3 logs

ETC Microsoft Windows
1

Hey,

I am looking in to the possibility of trying to analyze Windows Server 2003 files by using the AWK filtering(programming) language, first off. Secondly I'm looking in to the possibility of implementing AWK (results/or the script itself) inside a "Microsoft Access 2007"-database.

Some questions arise, however, questions which I cannot answer. I hope you experts here can help me out with answering these questions.

First off, some core questions as to the possibility of filtering eventlogs with AWK:

  • Is it (even) possible to filter W2k3 Evenlogs with AWK?
  • How would I go "defining" the structure of the Eventlog within AWK?

Secondly, questions about the implementing of AWK within an Access 2007-database(wierd, I know):

  • Is this even possible?!
  • If yes, how would go about doing this? If no, why?
  • How would Access know how to interpet a AWK script?

Why would I ask such wierd/(I think)unheard questions? Because I am in a project at the moment and am kind of stuck with the requirement of having to implement the statistical data of the Eventlog files from a Windows Server 2003-machine into a existing Microsoft Access 2007-database. I really hope someone could answer these questions, as I am in a bit of a predicament.

The deadline is 2 weeks from now, and I can't come up with any psuedo code first off, for the AWK script to get the nesc. data. Secondly, I can't think(or find) anyway of letting a AWK-script work in a Access environment.

I also can't think of a way of how to get the statistical data from AWK(a unix machine) to Access 2007(a windows system).

Thanks for you time,

  • abc
2

Directly? I doubt it. I do know that it's possible to export the eventlog data to text files, but I wouldn't know how to (possibly) automate this. awk itself can only operate on text data.

Exported, it's a simple CSV file.

Maybe as an extension. But I doubt that this would be doable by a single person on a 2 weeks deadline.

Again, it might be possible as an extension-DLL. Or maybe even using a VBscript macro. But not with a 2 weeks deadline.

It doesn't.

You might be a lot faster if you wrote a small awk script to transform the exported data to a format compatible with the existing "database", import the file(s) directly, and do any statistics inside the DB using SQL.