Reddit reviews SQL and Relational Theory: How to Write Accurate SQL Code
We found 4 Reddit comments about SQL and Relational Theory: How to Write Accurate SQL Code. Here are the top ones, ranked by their Reddit score.
Used Book in Good Condition
We found 4 Reddit comments about SQL and Relational Theory: How to Write Accurate SQL Code. Here are the top ones, ranked by their Reddit score.
> And that's perfectly fine, because the relational model is not practical enough for real world uses.
You had me right up until this. Why do you say that it's not practical enough? I've lost count of the number of problems I've encountered in SQL databases that wouldn't have happened--couldn't have happened--had the database been truly relational. Whole classes of these kinds of issues, and their solutions, are found in SQL and Relational Theory: How to Write Accurate SQL Code. So this is not a troll; I'm genuinely curious as to what you mean. Thanks!
http://db-class.org is open this quarter, and covers the fundamental relational database concepts.
SQL and Relational Theory is a solid next step. (and available using the free 10 day Safari Books Online trial account)
For specific syntax, refer to Microsoft's own product documentation. The SQL Server Books Online should have been installed on your workstation along with the client tools if you're using SSMS. The T-SQL language reference begins here.
You might also want to install one of the SQL Server editions on a workstation as a playground so you don't need to worry about breaking your production servers. Developer Edition is under $50 a seat. Express is free. There's also a time-limited full evaluation copy available here.
Actually C.J. Date updated that book and released it under the new name SQL and Relational Theory: How to Write Accurate SQL Code.
I read Database in Depth a few months ago, and my copy of SQL and Relational Theory just arrived. In the preface Date states that he wanted to provide similar information -- updated to match his current understanding -- but use SQL as a concrete example of his theories. It's definately worth a read though, because most developers use SQL in a way that is not compatible with Relational Theory.
http://www.amazon.com/SQL-Antipatterns-Programming-Pragmatic-Programmers/dp/1934356557/ref=pd_sim_b_3
http://www.amazon.com/Joe-Celkos-SQL-Smarties-Programming/dp/1558605762
http://www.amazon.com/Art-SQL-Stephane-Faroult/dp/0596008945/ref=pd_sim_b_4
http://www.amazon.com/SQL-Relational-Theory-Write-Accurate/dp/0596523068/ref=pd_sim_b_7
And then read a book on whichever dialect of SQL you're using, because they're pretty different.