Top Banner
Microsoft SQL Server – How to Improve Interoperability using FME May 1st, 2013
26

Microsoft SQL Server – How to Improve Interoperability using FME

Nov 14, 2014

Download

Technology

Safe Software

Discover how to easily read, write, and update data in Microsoft SQL Server. We’ll share ways to automate SQL Server workflows while using FME’s transformation capabilities, featuring support for multiple geometry columns and the geography data type. Plus, see what’s new with FME 2013’s support for SQL Server 2012 including the ability to create a spatial index.

This webinar is the second in our series of database webinars on SQL Server, PostGIS 2.0, and Oracle.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Microsoft SQL Server – How to Improve Interoperability using FME

Microsoft SQL Server – How to Improve Interoperability using FME

May 1st, 2013

Page 2: Microsoft SQL Server – How to Improve Interoperability using FME

Who Are We?

Mark StoakesProfessional Services Mgr

Robyn RennieFME Desktop Support Mgr

Page 3: Microsoft SQL Server – How to Improve Interoperability using FME

Questions are Encouraged!

This morning’s Q&A Support:

Steve MacCabe Professional Support Specialist

Page 4: Microsoft SQL Server – How to Improve Interoperability using FME

Questions are Encouraged!

We’re happy to answer any questions you have.

To submit a question:

If we can’t get to your question during the webinar we’ll send a follow-up email.

Page 5: Microsoft SQL Server – How to Improve Interoperability using FME

Powering The Flow of Data

FME – Feature Manipulation Engine

Page 6: Microsoft SQL Server – How to Improve Interoperability using FME

FME Technology Capabilities

Transform spatialand non-spatial

data into the precise data

model you need

400+ data

transformation tools

The only complete spatial data transformation solution

Translate spatial data from oneformat to another

300+ supported formats in FME 2013

Page 7: Microsoft SQL Server – How to Improve Interoperability using FME

FME Workbench Workspace Graphical authoring environment

Page 8: Microsoft SQL Server – How to Improve Interoperability using FME

Poll: What is your FME level of expertise?

Page 9: Microsoft SQL Server – How to Improve Interoperability using FME

Getting started page:

http://fme.ly/GetStarted

Attend a weekly FME Desktop overview webinar:

http://fme.ly/WeeklyIntro

New to FME?

Page 10: Microsoft SQL Server – How to Improve Interoperability using FME

Poll: What frustrations do you have with your database workflows that don’t involve FME?

Page 11: Microsoft SQL Server – How to Improve Interoperability using FME

FME Version & Edition

FME SQL Server Edition

FME 2013 SP1 SQL Server 2012

Page 12: Microsoft SQL Server – How to Improve Interoperability using FME

Poll: General Questions

Page 13: Microsoft SQL Server – How to Improve Interoperability using FME

Agenda

Demos Reading and Writing – tips and tricks SQL Server functionality Database Transformers Supported Database functionality Edits and Change Detection

Follow-up Webinar recording and materials

Page 14: Microsoft SQL Server – How to Improve Interoperability using FME

Warp Speed Demos!

Page 15: Microsoft SQL Server – How to Improve Interoperability using FME

Writing Data

Data Loading Multiple Spatial Columns Creating complex tables

Incremental Updates fme_db_operation SQL Key Columns or fme_where

Example

Tips n’ Tricks Use a unique key field Use Bulk Insert mode - 5-10x speed increase Transaction Interval

Set 1 for a commit on every feature Set to a very large number to commit at the end.

Example

Page 16: Microsoft SQL Server – How to Improve Interoperability using FME

Performance

Make the database do the work

Index, index, index – both spatial and attribute

Bulk insert mode where available on Inserts – 5-10x speed increase inserting into SQL Server

Page 17: Microsoft SQL Server – How to Improve Interoperability using FME

Database TransformersLet the database do the work…

SQLCreator/SQLExecutor Efficient database joins for SQL capable datasets

Joiner Multiple attribute joins No requirement to understand SQL Non-spatial only

FeatureMerger Single attribute join No requirement to write any SQL

FeatureReader Spatial & non-spatial queries

Example

Example

Page 18: Microsoft SQL Server – How to Improve Interoperability using FME

Geometry Validation

PASSED detectionFAILED detection

Detection

PASSED detectionFAILED to repairREPAIRED fully

Repair

Issue Reporting .issue_found .location_sample.x .location_sample.y .location_sample.z .repair_state

GeometryValidator Transformer

Example

Page 19: Microsoft SQL Server – How to Improve Interoperability using FME

GIS & CAD

Exporting to CAD Dynamic Workflows Schema Mapping Schema Table CAD Styling

20

Example

Page 20: Microsoft SQL Server – How to Improve Interoperability using FME

SQL Server and ArcMap

21

Page 21: Microsoft SQL Server – How to Improve Interoperability using FME

Question & Answer Period

FMEDatabases

Page 22: Microsoft SQL Server – How to Improve Interoperability using FME

2013 FME World Tour!

40+ FME User Meetings happening world wide and one live stream

Register atwww.safe.com/worldtour

Page 23: Microsoft SQL Server – How to Improve Interoperability using FME

Upcoming webinars

Oracle - How to Improve Interoperability using FME – June 11

Reading and Writing XML with FME – May 8th

Recorded Webinars:http://fme.ly/webinars

Page 24: Microsoft SQL Server – How to Improve Interoperability using FME

View the offerings at: http://fme.ly/online

Poll: Would you like more information on our free training options?

Page 25: Microsoft SQL Server – How to Improve Interoperability using FME

We’ll Be Following Up

Page 26: Microsoft SQL Server – How to Improve Interoperability using FME

Thank You!

For more information, please contact: Sales

[email protected] Support

www.safe.com/support (604)501-9985 ext. 278

Mark [email protected]

Robyn [email protected]