There are an infinite number of XML formats -- did you have a particular DTD/XSD in mind?I doubt it would be easier or faster, but it would be simple and fast to use 'sdequery' to dumpthe data to ASCII (comma, tab, or pipe-delimited strings with Well-Known Text geometries).D:\>sdequery
ArcSDE 10.0 Generic Query Tool Thu May 24 07:05:22 2012
------------------------------------------------------------------------
sdequery -h
sdequery [-C <column_list>] [-t <table_list>] [-w <'where clause'>]
[-# <row_count>] [-l <table,column>] [-V <Version_Reference>] [-q]
[-A] [-v] [-N] [-vI <feature_count>] [-d <Dumpfile_Reference>]
[-B <buffer_distance>] [-P {UTM | ALBERS | LAMBERT | proj_code}]
[-S <sampling_probability>] [-Q {ATTR | JFA | JSF | JSFA | V3}]
[-L <query_logfile>] [-R <result_logfile>] [-O <Order-by clause>]
[-a <alias_list>] [-Fn <method:[{TRUE | FALSE}:]shape_string>]
[-E <minx,miny,maxx,maxy>] [-s <server_name>]
[-i {instance | port#}] [-D <database>] [-u <DB_user_name>]
[-p <DB_user_password>]
D:\>sdequery -t table -d table.txt,'|' -s server -u user -p userspassword ...
Line and polygon data tend to be very large in Well-Known Text, which will be the primecontributor to runtime performance.'sdequery' is part of the se_toolkit tool suite. I've got "to-do" tasks for SQL, CSV, and KMLexport, but no time to do them in. - V