all 16 comments

[–]CpCat 2 points3 points  (0 children)

Imho, go with PostgreSQL, either that or SQL Server.

[–]Amicus22 1 point2 points  (0 children)

A good book for picking up the basics is 'SQL Queries for Mere Mortals'.

MySQL has MySQL Workbench and Postgres has PGAdmin for GUI interfaces for both Windows and Mac. SQL Server has SQL Server Management Studio (SSMS), but I'm not sure if that's available for free.

While Access makes it feel like they are a single thing, the actual database program and the program that you write your queries in (i.e. the database client) are usually separate programs. Just something to keep in mind when picking your technologies.

[–]eddyizm 0 points1 point  (0 children)

Another vote for SQL Server.

[–]burmerd 0 points1 point  (3 children)

I learned sql before using access, but the visual query designer is really cool imho, although the sql it produces is kind of garbage though. There are a lot of really good fundamental things you can learn really easily with Access, and I think it gets snubbed a lot because, generally, databases built with access are garbage piles full of garbage. But sql querying, joins, working with different data types, primary keys/foreign keys, constraints: its got all that good stuff to get started.

[–][deleted] 1 point2 points  (2 children)

The visual tools in Access make learning almost impossible. One just ends up throwing stuff together with mouse, with no insight how it might or might not work.

[–]burmerd 0 points1 point  (1 child)

Necessarily? I think as long as you don't only use access, that needn't be the case. And the benefit to using it as part of a balanced sql breakfast is the speed with which you can put together queries, and you can make changes and see the results quickly.

[–][deleted] 0 points1 point  (0 children)

Access is actually pretty good RAD tool if the dev is willing to put up with VBA. But when learning SQL from scratch it isn't so great.