They’ll come out of the woods and start claiming he wasn’t a true libertarian.

This is exactly what the alt-right Christian fucks want. I’m surprised that they don’t realize how much in common they have with the Taliban.

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”.

For my team I have a mirror that I set up and have a bunch of ELT jobs that load the deltas every night. Queries don’t ever run in PROD, if someone needs a specific view or more data, they go through me and my team. I also set timeouts, precisely to avoid the ahole from using Select * from. Also have a bunch of reports I created to see who is running what queries and timings. We review them quarterly or when someone complains or when a project that needs our data asks us for access.

We also have an autogenerated data dictionary for folks to use as well. Generally I don’t entertain any “it’s slow” complaints unless they go through the documentation, provide their exact query and write what it is they’re trying to get.

My assumption was that OPs shop does the bare minimum in terms of making sure they don’t shoot themselves in the foot.

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?

I’ve worked in a hospital. During my time there we had a true blackout. Even the central power generator couldn’t turn on, because the connection was chewed through my rats. No one did a check on it like they’re supposed to every month…heads rolled for it.

Here to say, you can’t just power ICU beds in isolation. The circuits for emergency power aren’t just going to beds. They’re open sockets on the wall, any one can plug anything in there. You can’t just redo a circuit in the blink of an eye either. If their central generator died and they get a bunch of gas powered ones, they’ll need a lot of time to figure out where they need to splice the wires in order to supply power but not overwhelm the generators.

It’s safe to say they’re probably going to use their large central generator. It’s probably also safe to say they’re going to power more than the ICU beds. Even if they turned off the heating and cooling, they’re still going to use more than the figure you suggested. Some circuits aren’t optional.