I'm very happy to hear you were able to figure out a query that gives you the data you need. Just so you know, the @ symbol is actually an indicator that the word after it (v in this case) is an attribute rather than an element. e.g. USERID is an element name, v is an attribute name so /USERID/@v selects...

Well, the above query works but after modifying the query to include other nodes (no syntax errors), no data values ever appear in the output area. Hmmmm.

Visual Log Parser XML queries: Here is what I discovered. Once I set the following values in the "XML Parameters" window and modified my query accordingly, I managed to extract 13 rows for a given userid in an XML log file with XML tags that use " v=" in data nodes. I believe I read somewhere that space...

Log Parser isn't very well suited for this format of XML. You might be able to get something of use by changing the fMode parameter. Try each of the three settings (Branch, Tree, or Node) and see if any of them will work for you.

I am using the Visual LogParser tool and am confused how to parse the following XML file looking for a specific USR_ID value of "MyUserIDHere". As I understand it, Visual LogParser uses the Microsoft Log Parser tools for executing queries. Any suggestions? -Ed <AUDIT_TRAIL> <TRANSACTION>...

Hello Daniel, tanks for your answer..... english isn't my native language .... i'm from germany .... I think you right that im must test the xml file direkt white SQL Server. Thanks for your help. by

LogParser might not be the most useful tool for you to use when importing XML into MSSQL. I am unable to understand exactly what trouble you are having. Are the errors you are seeing related to the structure of the XML itself or some part of LogParser's loading into the database? Can you post an example...

I must import xml files into a data base. I bring xml the file in and look at myself then the error message in the program. The program validates the XML file and imports these only if it error free. Correct the error and play the improved xml data. Then correct I the next error and bring the improved...

JTaylor, There were a few emails exchanged privately to try to work through this problem with no success. I think we ended up agreeing that it was a bug with the way logparser handles those random byte values when outputting XML. I'm not sure what your situation is. In my case using logparser the way...

Can we get a version of this I am having the same errors or is there another fix?