You might want to look at passing the parsed request to a data factory pipeline which has more advanced mechanisms to work with SQL Server. We use logic apps solely to get information from the 'outside world' into our systems.
@josefrichberg
Principal Data Architect, Azure @ Penguin Random House
I've been working in and around SQL for over 3 decades.
I am currently working on making our business intelligence systems self-driven by using an event-based architecture. This involves providing curated data in some of the largest SQL Azure Analysis Services cubes ever built (over 6 billion records in 1 table alone).
I've developed several APIs leveraging a serverless Azure architecture to provide real-time data to various internal processes and projects.
Currently working on Project Dormouse; Durable select messaging queue that enables polling processes to extract specific messages.
Nothing here yet.
You might want to look at passing the parsed request to a data factory pipeline which has more advanced mechanisms to work with SQL Server. We use logic apps solely to get information from the 'outside world' into our systems.
Find a language that makes sense to you. This will make coding more about solving the problem than wrestling with the language. Once you get a foothold in a language you can then try other languages and see if they too make sense. Some people can do multiple languages easily, others struggle with 1. If you are good at only one, then work hard to be very good at it. If you are at multiple, then find one that is the right fit for the problem you are solving (which you won't need to worry about for many years to come)>
I wonder about OSS. Originally it was designed to solve problems that were either too expensive to use or didn't exist. It was hailed as the way to unshackle your project from the exclusivity of corporate contracts, but I fear it has gone down the path of 'problems looking for solutions. We as developers look to reinvent the wheel any chance we get as a way to prove our worth, sort of like a rite of passage. This comes at an immense cost. We no longer solve business problems in an efficient manner, we solve them haphazardly with various bits and bobbles. I think OSS has seat at the table, but maybe not the table it currently takes residence at.