<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">After upgrading GDAL to a version that supports MSSQL bulk inserts (v2.2.3) I have found an issue with data append operations using ogr2ogr between MSSQL spatial tables. If the destination table has a column of type varchar(max) then it
is only populated with the first character from the source record. No such issue for nvarchar(max) types or varchar with a restricted length.<o:p></o:p></p>
<p class="MsoNormal">The GDAL command I am using is simply:<o:p></o:p></p>
<p class="MsoNormal">ogr2ogr -append -f MSSQLSpatial "MSSQL:server=SQLSERVER;database=DATABASE;trusted_connection=yes" "MSSQL:server=SQLSERVER;database=DATABASE;trusted_connection=yes;tables=SOURCETABLE" -nln DESTTABLE<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The only work around for this is to disable bulk inserts first with:<o:p></o:p></p>
<p class="MsoNormal">SET MSSQLSPATIAL_USE_BCP=NO<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We are using MSSQL Server 2014. Has anyone else come across this?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks<o:p></o:p></p>
<p class="MsoNormal">Jason<o:p></o:p></p>
</div>
<p>************************************************************************<br>
Confidentiality: This email and its contents and any attachments are intended only for the above named. As the email may contain confidential or legally privileged information, if you are not the above named person or responsible for delivery to the above named,
or suspect that you are not an intended recipient please delete or destroy the email and any attachments immediately.<br>
<br>
Security and Viruses: This note confirms that this email message has been swept for the presence of computer viruses. We cannot accept any responsibility for any damage or loss caused by software viruses.</p>
<p>Monitoring: The Council undertakes monitoring of both incoming and outgoing emails. You should therefore be aware that if you send an email to a person within the Council it may be subject to any monitoring deemed necessary by the organisation from time
to time. The views of the author may not necessarily reflect those of the Council.</p>
<p>Access as a public body: The Council may be required to disclose this email (or any response to it) under the Freedom of Information Act, 2000, unless the information in it is covered by one of the exemptions in the Act.</p>
<p>Legal documents: The Council does not accept service of legal documents by email.<br>
************************************************************************</p>
</body>
</html>