Latest Contributions by ForrestChevaillier1

Thank you, very useful stuff. I will try out both options in the next few days and let you know what I end up doing. For option 1, would this entail setting a trigger that re-creates the table every time there is an edit to either the polygons or the points, or did you have another method in mind? For option 2, could I accomplish this with a Query Layer? ... View more

The final venue is for ArcMap, I want this to be a layer accessible by my users. I am testing the speed by running just the SELECT query in SSMS, then I will go ahead and create the view and test it in ArcMap. -ArcMap loads quickly when I am using the default tables to create the view and SSMS runs the SELECT query in less than a second. -ArcMap loads slowly when I am using the versioned view to create the view and SSMS runs the SELECT query in 29 seconds. What are the regular methods of accessing versioned data? I am new to SQL Server and versioning. ... View more

Christian, Thank you for your assistance. I ended up deleting my pa feature class and archive table, re-importing it back to the database, re-enabling archiving, and re-creating my views and they worked! So, I guess I must have corrupted that pa feature class somehow in my SQL experiments. Good thing it was just practice data! Thanks, Chloe ... View more

Thank you for the suggestion. I tried the STIsValid() function on the intermediate view and on the pa and pa_evw tables and all records returned 1 in the validate column. ... View more

Thanks for the responses. I should have mentioned initially - I am a complete novice, so please forgive my ignorance. I’ve only been playing with SQL Server 2012 Express for about three weeks. Based on your info, I changed the query to use a simpler boundary file and used Filter() instead of STIntersect(). The view now draws and I can do selections. Though it is still a little slower than the unaltered parcels feature class, it sounds like that’s the best I can hope for when attempting cross-database queries - at least until I learn more about optimization. I'm realizing I need to crawl before I run. The new query is: CREATE VIEW dbo.parcView AS SELECT parc.OBJECTID, parc.PROP_ID, parc.SITE_ADDR, parc.SHAPE FROM MASTER_GIS.dbo.PARCELS AS parc JOIN dbo.SIMPLE_BOUNDARY AS bdry ON parc.SHAPE.Filter(bdry.SHAPE) = 1 Here are the stats (or at least some of them, omissions made where my answer is a simple shrug): How complex the "BOUNDARY" geometry is (number of vertices) 1607 vertices (the original boundary file had 4125) The exact time it takes to query BOUNDARY from a SQL prompt I put just the SELECT query in a new query in SSMS and the time said 00:00:01 The exact time it takes to draw the view in ArcMap. I don’t know how to measure this – would love to learn though. The spatial index options used on the PARCELS geometry column index The default spatial index that is added when you import data, I don’t know how to look at the options or alter the index right now. Something I will look into. I am very interested in trying the tessellation method. I need to Google about 6000 terms before I even understand what that means, but I’ll get there eventually! ... View more