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.
4. 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.
6. FME Technology Capabilities
Transform spatial
and 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 one
format to
another
300+
supported
formats in FME
2013
15. 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
16. 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
17. Database Transformers
Let 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
22. 2013 FME World Tour!
40+ FME User Meetings
happening world wide and
one live stream
Register at
www.safe.com/worldtour
23. 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
24. View the offerings at:
http://fme.ly/online
Poll: Would you like more
information on our free
training options?
26. Thank You!
For more information, please contact:
Sales
info@safe.com
Support
www.safe.com/support
(604)501-9985 ext. 278
Mark
Mark.Stoakes@safe.com
Robyn
Robyn.Rennie@safe.com
Editor's Notes
Steve on QA
We’re happy to answer any questions you have during the webinar. To submit a question just open up the questions box in the GoToWebinar pane and type away. If we don’t get to your question during the webinar we’ll send you a followup email.
FME also does data of all kinds – doesn’t have to be spatial.
2013 highlights – you can talk about interesting new formats here:INGRES Spatial & non-SaptialAutodesk IMXOdata – web XML/JSON messagesSocrata – web based for local Gov.PostGIS Raster & PostGIS 2Point Cloud: Riegl LaserScan & Terrasolid TerrascanAbout 30 new formats for 2013
Workbench: The tool that lets you draw the flow of data
NoviceIntermediateExpertI have never used FME (note: next slide will tell them where to get more info)
Not covering the basics of FME, but here is where you can get more background.
(multiple choice)- Need to know SQL and use it- Need to create intermediary files when switching between DBs- Need to spend time working through a DBA- Need to create a workflow for every database scenario- Other
Here’s what we’re usingFME 2012 – released yesterday
More for our info than for any scientific feedbackMultiple choiceAre you using SQL Server 2012 yet?Do you use ArcGIS Desktop to access your SQL Server database directlyDo you use the Geometry storage type?Do you use the Geography storage type?
David Eagle gave some excellent tips on this during the Turbo charging FME webinar so I am not sure there is much left for me to say here – just to reiterate the main points for those of you who haven’t yet listened to the webinar. And to recommend that you find the webinar on our website and take a listen.Show where these things are in a workspace- Spatial envelopes, where clauses, native predicates- File Geodatabase API allows for attribute indexingSQL Server spatial now has an automatic spatial index creation option – show where this is and the options – only available in SQL Spatial 2012 – still impacts FME 2013 because the default mode is AUTO which doesn’t work.BEWARE – only do the spatial indexing at the end of the operation – writing to an existing geodatabase does the index updating as the writing is happening.Bulk insert mode – doesn’t work with fme_db_operation – 2.2 secs vs 6.8 on a load of the address informationSpatial envelope – 3122000, 10076000, 3146000,10103000
SQL Server is very forgiving about the kind of spatial data which can be written into the database. Consequently it is easy to get features with invalid geometries into the feature classes. FME offers some transformers which can help with this. Here we have a shape file with all the countries in the world in it. Right away we can guess that we might have problems with Russia, Antartica and perhaps some of those countries which are made up of multiple small polygons. So this example adds this shape data into two tables – one with the geometry spatial type and one with the geography spatial type. Notice that the geography spatial type cannot handle Antartica because this data appears to have some coordinates with enough precision to drop them below the -90 latitude which is impossible. So it is rejected. A clipper would get around this problem.We assume that because the data has been written that SQL Server will be happy with it but this isn’t always the case. Issuing the commandSELECT COUNTRY, GEOG.IsValidDetailed() FROM [support].[dbo].[countries] WHERE GEOG.STIsValid()=0 order by COUNTRYIn the SQL Server management studio shows that there is invalid geometries in there. So this is where the GeometryValidator can be useful.
Update:- Extend ArcGIS- ArcMap - open Catalog and add connection to city parks- ArcMap - drag connection into map to open- Properties - categorize by park name- rt-click - Data - Export Data - output feature class - create new geodatabase- save data and add as layer.- remove connection- Editor - start editing- pick park, then choose attributes - change alternate name- choose another park - move vertex- Editor - stop editing and save edits- open 5_DB_Operation and add parks gdb- explain processrun workspace, then add updated table to view
There are still a few cities left on the World Tour – if you can spring for a trip to Australia and NewZealand or maybe England or Europe there is still time to find out all the new goodies in FME 2013
Note: These 3 database webinars are a series – we will be basically covering the same material with additional information for each format