Sorry dude…writing simple queries is what I said was easy…and for the record they are. That example is probably not a great example. Simply from my experience, I never started my career in IT, I was in healthcare and far from it all.

Anyway, I’ve had some idiots approach me about their shitty ideas before too…most notably was one person asking to create an app that “uses AI” to help a person search for the right individual when they send a text message. Couldn’t explain how it would know that it found the right person? There was another one that wanted to track the origin of “content” and how it changes over time on social media… again “using AI”.

Ooof my guy if you got folks running queries on your PROD db you got bigger problems even if they were the best SQL writers in the world.

You can’t fuck up step 1 and complain the rest of the steps aren’t working. I write and maintain a set of ELT jobs and a bunch of front end dashboards. By default, we never run analytics queries in PROD db. I create views and such for the simple queries to run.

I picked up SQL a few years ago for a school project. It took me a week. The DBA stuff just came by itself as I went along. Query optimizations took a while but you don’t need to write every query super optimally. If the DB tables are set up correctly your users will not have to worry about it at all.

My previous comment assumes you guys already have a db set up for analytics where folks can run queries. If you don’t then IDK how the director of IT got their job…That’s very basic shit.

SQL isn’t hard to learn unless they’re asking you guys to do T-SQL and PLSQL.

For simple queries it’s pretty easy.

This sounds like an interesting project, what programming language did you use? Was the endpoint relative to the person making the query, how was the data stored?

This brings back some nightmares. Once I get them working I never upgrade or even look at them.