I've only ever heard it called "sequel" in my work dealings with developers and whatnot so that's what I've always called it too.
Oh God. I wasn't trained but the guy I worked with used like 20 sub queries (Fine in themselves) but did not name any of them with an alias other than a letter nor did he keep the same names for columns over a massive query with tons of sub queries.
Every fucking time, he had several operations and the automated queries he'd set up always failed randomly. Most people also tried the hardest to us MSAccess and combo of pass through T-SQL and Jet SQL and they would create a query which linked to another query, so many union queries and queries post that. They always failed, my boss was like but you're the best at SQL why can't you fix it... there are fucking a 100 queries with shit labelling.I hope you didn't have to trouble shoot that at some point lol
Yeah if you actual have real SQL training you would know it's "sequel" because that's what Microsoft calls itI say 'sequel', like everyone else who actually uses SQL
To me, saying "Ess Q El" would be like pronouncing gif as "Gee Eye Eff"
as someone who spent years as a programmer for database applications the correct term is sequel.sequel
I probably also called it ess cue ell as a kid but everyone in the industry says sequel for the most part
It's an abbreviation for Structured Query Language, which would technically make SQL "correct", but…
Been a system engineer/admin for 11 years now. It's always been Sequel. It is pronounced that way in VMware and Citrix classes as well.I haven't worked with databases in over a decade.
However I am now starting a new role with new projects and all my colleagues are talking about sequel, which greatly confuses me...
I first learnt about databases back in high school and we pronounced in SQL [ess-que-ell].