(Part 2) Top products from r/Database

Jump to the top 20

We found 23 product mentions on r/Database. We ranked the 58 resulting products by number of redditors who mentioned them. Here are the products ranked 21-40. You can also go back to the previous section.

Next page

Top comments that mention products on r/Database:

u/arnimar_ · 2 pointsr/Database

I'm no expert in database certification so I won't comment on them, but they sound expensive. I'm sure you could go a long way in improving your skills by working through some free resources and classic texts.

A nice tutorial on fundamentals is:
http://philip.greenspun.com/sql/

A classic introductory to intermediate text is the following. It can get you amazingly far because even advanced topics are explained well:
http://pages.cs.wisc.edu/~dbbook/

Don't get thrown off by the publication year. The fundamentals of relational databases have barely changed for decades.

An excellent in-depth look at database theory is presented in:
http://www.amazon.com/Foundations-Databases-The-Logical-Level/dp/0201537710

For data warehousing and analytical querying (beyond Ramakrishnan et al) this is a great resource:
http://www.amazon.com/The-Data-Warehouse-Toolkit-Dimensional/dp/0471200247

Source: I'm a graduate student in databases.


u/el_chief · 2 pointsr/Database

For your particular application I would look at OpenStreetMaps. Otherwise...

David Hay's

u/QuirkySpiceBush · 2 pointsr/Database

Since relational databases are a mature technology, there is some well-established theory that is very useful to learn (in conjunction with the more practical, vendor-specific knowledge).

I'd suggest:

Database Management Systems - an undergrad-level textbook with a good balance of theory and practice, foundations and advanced material.

Readings in Database Systems - a compilation of influential academic papers from the database field.

Data Modeling Made Simple - a great little book that bridges the gap between databases and the real-world entities they store.

u/bitcycle · 1 pointr/Database
  1. Use a relational data store first: MySQL/PostgreSQL/M$ SQL Server.
  2. Put CRUD operations behind a web service.
  3. Instead of arbitrary key/value pairs, try to get as specific as possible about the data (instead of storing everything as strings). Being more specific will help things (usually) to be more performant.
  4. Build the application on top of the service.
  5. Scale to the # of users you want to be able to support
  6. At this point, if you need to move part of the data into a non-relational data store, you can.

    I also recommend reading this book: Patterns of Enterprise Application Architecture
u/wolf2600 · 1 pointr/Database

What courses does your school offer for databases? SQL? Administration?

A great starting point would be to learn and become proficient in SQL:

http://www.amazon.com/Oracle-Database-Fundamentals-Exam-Guide/dp/0071597867/ref=sr_1_2?ie=UTF8&qid=1415821007&sr=8-2

After that, pick up the book for the 2nd Oracle OCA exam, Administration 1.

u/doublenns · 2 pointsr/Database

https://www.amazon.com/Database-Design-Mere-Mortals-Hands/dp/0201752840

I read that book back in college for my Databases class and thought it was a pretty easy read. It's long, but can also surprisingly be a quick read, esp if you just go thru it w/ a highlighter and don't take much notes beyond that.

There's also a newer version of the book available.

Are there any specific questions you have about databases tho, or any specific topics that confuse you? What database software are you guys working with? MySQL? MariaDB? Microsoft Access? PostgreSQL? MongoDB?

u/HawkeyeGK · 3 pointsr/Database

You're thinking like a java developer. Stop thinking open source and retrain your mind to think in sets. Once you've got the basics of set-based computing down, the particular DBMS you end up working with is just a matter of learning server config and eventually the nuances of particular execution plan creation and management.

Try something like this that is totally independent of RDMS. Learn the fundamentals of the SQL language, thinking in terms of sets, and basic performance management through indexing and you'll be miles ahead of the game.

u/tynman · 1 pointr/Database

For data modeling, I prefer Object Role Modeling (ORM2) over UML. It gives you a conceptual model (ideas and relationships) rather than a logical model (tables and columns), which ends up being more semantically stable as you refine your domain.

The cool thing is that you can generate a 5th Normal Form logical model from it algorithmically. The NORMA tool for Visual Studio can even generate the Barker ER diagram for those who prefer that view.

Full disclosure: I'm a fanatic of ORM2 and have started blogging about fact modeling in my copious spare time.

EDIT: The definitive work on ORM2 is Terry Halpin's book

u/yehauma · 1 pointr/Database

Database Modeling and Design


My ex was building some databases for a job and I found this book (well an older version) to be excellent and concise about explaining the why behind database design.

u/Tofinochris · 1 pointr/Database

Agreed, OP, you're massively overcomplicating this. If you learn a bunch of math and theory to try and become a database professional you will just come across as an academic rather than someone who can get work done. Learn how to get work done. Check out books like SQL Cookbook and SQL For Smarties to learn stuff that will actually help you do what you need to do.

You do want to have normalization down and basically understand set theory, but you're already doing that.

u/odinsride · 0 pointsr/Database

This might be good. You can also read some of the documentation/white papers/marketing materials on otn.oracle.com for Exalytics and/or TimesTen

u/amaxen · 3 pointsr/Database

I'd recommend first, the Inside SQL Server Series mentioned above. Also I'd recommend the Guru's guide to Transact-SQL. I found it really enhanced my skills in T-SQL over the years. I'd run into some difficult problem only to think 'hey, the guru's guide had something on this....'. I tried to re-read it every year. Also, lots of good code samples.