Skip to main content
Question

Bug in MSSQL_SPATIAL writer ?

  • September 30, 2016
  • 2 replies
  • 10 views
lifalin2016
Contributor
Forum|alt.badge.img+29

Hi,

I just encountered an unexpected problem with the MSSQL_SPATIAL writer.

I originally set a manual command ("exec some-stored-procedure-with-arguments") to define a spatial index and more, which err'ed because there was no primary index on the relevant table. That's fine and understandable.

As I really didn't needed a spatial index on the specific table anyway, I just switched the dropdown "Spatial Index Type" to "None", and reran the translation.

But the translation still failed in the same place, while trying to execute the now deselected and unwanted command.

It seems like the command was still present, and FME tried to execute it as such, even though the setup stated it shouldn't. This I believe to be buggy behaviour, the overall choice should not be overridden like that.

Cheers

 

Lars I.
-- Cheers, Lars I.

    2 replies

    mark2atsafe
    Safer
    Forum|alt.badge.img+44
    • mark2atsafeSafer
    • Safer
    • September 30, 2016

    Seems that this is a known issue (filed as PR#50727). I'm told that a workaround is "deleting the SQL statement then hit OK, then come back and re-set spatial index type to None" , but this is obviously not ideal.

    So I will add a link to this thread in that problem report and increase the priority. Seems to me it should not be a huge deal to fix this one.

    mark2atsafe
    Safer
    Forum|alt.badge.img+44
    • mark2atsafeSafer
    • Safer
    • April 26, 2017
    mark2atsafe wrote:

    Seems that this is a known issue (filed as PR#50727). I'm told that a workaround is "deleting the SQL statement then hit OK, then come back and re-set spatial index type to None" , but this is obviously not ideal.

    So I will add a link to this thread in that problem report and increase the priority. Seems to me it should not be a huge deal to fix this one.

    So this one is now reported fixed in FME2018. If it's causing major problems for you right now, and you don't have a workaround, the best thing to do is contact our support team (safe.com/support) mention the PR number and ask if it can be backported to 2017.

     

    Reply


    Helpful Members This Week

    Community Stats

    31,336
    Posts
    118,868
    Replies
    38,958
    Members

    Latest FME

    Terms & ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings
    A product of
    Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.