I'm working on a script someone else wrote. Is this stored SQL procedure going to be executed for once for each incoming feature, or once on the collection of features?
Best answer by redgeographics
View original
Userlevel 5
+25
- Influencer
- 3339 replies
-
24 March 2022
- Best Answer
The SQLExecutor will trigger once per feature, so in this case 100000 times.
If you only want to run it once you can use e.g. a Sampler to split off one feature to trigger it, or aggregate the data first (and then deaggregate later), although with 100000 features that's probably going to be a performance hit.
Userlevel 5
+25
- Influencer
- 3339 replies
-
25 March 2022
Thanks! I'm glad I took the time to ask. :-)
You're welcome! The HTTPCaller works in the same one (one request per feature) so I once ended up doing a DOS attack by mistake 😅
Userlevel 4
+25
- Safer
- 2392 replies
-
25 March 2022
You're welcome! The HTTPCaller works in the same one (one request per feature) so I once ended up doing a DOS attack by mistake 😅
I haven't done that, but I have managed to send multiple emails by mistake. Thankfully I had a lot fewer features than 100,000
+8
- Contributor
- 67 replies
-
28 March 2022
You're welcome! The HTTPCaller works in the same one (one request per feature) so I once ended up doing a DOS attack by mistake 😅
This case was almost the worst possible combination. It turns out the stored procedure was copying all records from one table to another, so 100,000 FME features * copy 540,000 rows. 😨
Userlevel 5
+25
- Influencer
- 3339 replies
-
29 March 2022
You're welcome! The HTTPCaller works in the same one (one request per feature) so I once ended up doing a DOS attack by mistake 😅
Oh wow! Yeah, that would have been bad!
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.