you can learn enough to write queries to databases in a few days

learning enough to design your own dbs will take much longer

Querying data is easy. Designing, maintaining, and ensuring data integrity is not.

What exactly do you want to know?

learning enough to design your own dbs will take much MUCH longer

possibly a week

Microsoft Access is thought of a kind introduction to SQL

>>1075189
microsoft access is absolute shit written so non-programmers and non-dbas can smash together their excel sheets and write absolute abominations of queries.

sqlite is a good starting point, it's SQL compliant with very easy setup and few datatypes to worry about

>>1075185
>What exactly do you want to know?
Enough to get a good job essentially. I'm looking for positions as a buyer/procurement specialist or something that involves ERP systems. Most jobs like this list SQL as a desired skill. I dont know enough about it to say I want to be a SQL developer, but looking at their salaries I'd say it wouldn't be a bad idea to get a job where I learn more about it.

Install a DB (I prefer PostgreSQL)

Google some tutorials for it, learn select/insert/delete

Look up "database normalization" and get a feel for what denormalized data looks like

Come up with something you would want to model (like a school which has teachers, students, classes, etc.) and design it in a schema designer (google "www sql designer") at the third normal form

Learn how to do joins (google "visual guide to sql joins)

Write some queries which product reports on your schema (average # of students per class, # of classes within x% of capacity, find all the unique students a teacher is responsible for, find all the unique teachers for a student, etc.)

>>1075202
Ill try this, thanks.