<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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
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;}
span.input
{mso-style-name:input;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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-US" 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">Recently we’ve done some improvement to the SQL Spatial Server in order to be able to support Z & M coordinates. Please see ticket
<a href="http://trac.osgeo.org/fdo/ticket/763">http://trac.osgeo.org/fdo/ticket/763</a><o:p></o:p></p>
<p class="MsoNormal">In order to be able to do so we had to move away from WKB format, that offers only 2D support.<o:p></o:p></p>
<p class="MsoNormal">Based on Microsoft documents we could move to the Microsoft geometry format (<a href="http://msdn.microsoft.com/en-us/library/ee320529.aspx">http://msdn.microsoft.com/en-us/library/ee320529.aspx</a>) allowing us to have full support for
Z and M, and arcs in the future release.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Moving to the new format we hit a problem; since we used ODBC and SQL_LONGVARBINARY to bind (WKB) geometries we got an error from Microsoft default driver - Operand type clash: image is incompatible with geometry.<o:p></o:p></p>
<p class="MsoNormal">This might be related to the fact Microsoft plans to remove image data types in the future releases. “<span class="input"><span style="font-size:9.5pt;font-family:"Segoe UI","sans-serif";color:black">ntext</span></span><span style="font-size:9.5pt;font-family:"Segoe UI","sans-serif";color:black">,
<span class="input">text</span>, and image data types will be removed in a future version of Microsoft SQL Server. Avoid using these data types in new development work, and plan to modify applications that currently use them. Use
<a href="http://msdn.microsoft.com/en-us/library/ms186939.aspx" target="_blank">nvarchar(max)</a>,
<a href="http://msdn.microsoft.com/en-us/library/ms176089.aspx" target="_blank">varchar(max)</a>, and
<a href="http://msdn.microsoft.com/en-us/library/ms188362.aspx" target="_blank">varbinary(max)</a> instead.</span>”<o:p></o:p></p>
<p class="MsoNormal">We could solve this by using SQL_VARBINARY binding, however this did not fixed everything. Using SQL_VARBINARY we can bind geometries with size less than 8000 in Microsoft default driver. In case we had a bigger geometry an error “Invalid
precision value” showed up.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We could get rid of all problems by using the new SQL Server Native Client 10.0. This allowed us to bind big geometries using SQL_VARBINARY.<o:p></o:p></p>
<p class="MsoNormal">Since this enhancement generated a small requirement (SQL Server Native Client 10.0 must be installed) in order to be able to use the provider, please ensure you have installed the “SQL Server Native Client 10.0” before trying to use the
provider.<o:p></o:p></p>
<p class="MsoNormal">Please let me know if you have any questions related to this enhancement.<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">Romy.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>