FreeTDS Development Group

[Frediano Ziglio <freddy77 AT gmail.com>]

Hi,
   first make sure you are using a recent protocol, I would say 7.4 for
sure.
Said that it could be that MSSQL refuses to send the reply for a XML text
(FreeTDS does not
support XML binary).
I would try to get logs and see if there are any hints.

Regards,
  Frediano


Il giorno gio 30 set 2021 alle ore 10:34 Tille, Andreas via FreeTDS <
freetds AT lists.ibiblio.org> ha scritto:

> Hi,
>
> I have a query which returns a result as XML which is larger than 2GB.
> When doing this on Windows via
>
>    sqlcmd -S myserver -d mydb -E -i myquery.sql > myresult.xml
>
> a 2.7GB XML file myresult.xml is created.
>
> If I try this with freetds 1.2.3 under Debian 11 I get:
>
>    sqsh -w 256 -h -S myserver -U myuser -D mydb -i myquery.sql -o
> myresult.xml
>
> I get
>
> Msg 6365, Level 16, State 1
> Server 'myserver', Line 70
> An XML operation resulted an XML data type exceeding 2GB in size.
> Operation aborted.
>
>
> I used this query successfully a long time but I used a Python3 script to
> run it.  This stopped working some days ago when the amount of data seemed
> to exceed some limit.  The actual error message that was thrown by the
> Python3 script is
>
>
> An XML operation resulted an XML data type exceeding 2GB in size.
> Operation aborted.
> DB-Lib error message 20018, severity 16:
> General SQL Server error: Check messages from the SQL Server
>
>
> Any idea why sqlcmd on Windows is succeeding here why sqsh and Python3 are
> throwing this error?
>
> Kind regards
>
>      Andreas.
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> https://lists.ibiblio.org/mailman/listinfo/freetds
>