Is SQL really this easy :gucci:?

[Mr Rager]

I'm at the tail end of a SQL course on Udemy and this shyt is not hard at all
The syntax is simple and its in plain english...a lot of these BI and data science gigs emphasis proficiency in SQL...is there something more complex about this language that I'm not aware of? It seems pretty common sense to me.

 

[Rich Spirit]

What course are you taking? I'm trying to learn SQL myself

Thanks @Clutch Robinson

 

[greenvale]

I'm at the tail end of a SQL course on Udemy and this shyt is not hard at all
The syntax is simple and its in plain english...a lot of these BI and data science gigs emphasis proficiency in SQL...is there something more complex about this language that I'm not aware of? It seems pretty common sense to me.

The baseline is pretty easy, but depending on the enterprise/data your processing some of the joins and pivots and shyt can be ridiculous. Stored procedures can get a bit complex too.

 

[Secure Da Bag]

Pivots are a MFer. Especially since you must have the columns you want beforehand. No dynamic SQL.

But getting the basics of SQL is super easy. But SQL is not great with string manipulation at all.

 

[krazykid18]

Of course it is easy until you have to write stored procedures for a report or a cursor or ETL and if u are fortunate to work in cube coding

 

[PikaDaDon]

If you're using ORMs you don't even need to type in any SQL

class PersonSchema( int id, string name, int age ) ;

class Person extends Table<PersonSchema>()

transaction = tmySuperEasyORMLibraryThingy.createTable( Person.notjava.className ) ;

transaction.insert( new PersonSchema( whatever, "Bob", 19 ) ) ;
transaction.insert( new PersonSchema( whatever, "James", 22 ) ) ;
transaction.insert( new PersonSchema( whatever, "Barbara", 27 ) ) ;

transaction.delete( "Barbara" ) ;

transaction.update( "James", age++ ) ;

Probably the worst psuedocode ever but you get the point.

 

[F K]

Doing SQL is easy, doing it well is harder, doing it well when you got millions and millions of rows...

 

[patscorpio]

Doing SQL is easy, doing it well is harder, doing it well when you got millions and millions of rows...

this

 

[Snoopy Loops]

Can you give a sample of your sql scripts? Kinda hard to assess the difficulty level of your course

 

[Obreh Winfrey]

Our schema is so all over the place that anything other than select * on TABLE; will require some legitimate effort.

 

[Sccit]

 

[Takerstani]

I found MySQL to be really straight forward, too. I'd still in the back of my mind fear accidentally irreversibly deleting something, even though it hasn't happened with smaller data sets.

 

[Rawtid]

It’s easy to learn the sample questions, harder in practice. So many other things to consider. Infrastructure could be trash, butt ass schema, no indexes, etc.

 

[Regular Developer]

Compared to programming in general, I think SQL is pretty simple as far as base use cases. The logic is pretty much set theory. Joins and subqueries, though, can start to get a bit crazy depending on the business rules you need to apply to the data.

So the next step is really what will you be doing with sql. Building for Data Warehousing, building an operational data base, just inserting data into an already created database, or pulling data from an already existing database

 

[Macallik86]

I've been working with SQL daily for a few years now. It is simple enough to wrap your head around, but I think that one of the hardest parts about querying databases is that just because your query returns results, doesn't mean that the results are correct. There is an additional layer of QA that is necessary for most tasks that catch a lot of incorrect assumptions, bad data, and the likes. Remember that good data is the results of a lot of other processes going smoothly since inception and that is rarely the case.

This isn't to say that you aren't well on your way to becoming a skilled SQL user, but more to say that database work can be a very humbling act.