To what extent should a developer study the features of database systems?

Question

Modern database systems today have many features. And you will agree with me that in order to study one database, you must wean the concepts that you learned in another database. For example, each database will implement a lock differently than the others. Thus, moving concepts from one database to another would be a recipe for failure. And there may be other examples where two databases will work very differently.

So, when developing database-based systems, do programmers need to know the database in detail so that they encode performance? I do not think it would be advisable for the DBA to require performance later, since its job is to maintain the database and help the developer in case of emergency, but not on a regular basis.

How much do you think the developer should get an idea of ​​the database?

Answer 1

I think these are the most important things (from least important to IMO):

• SQL (obviously) . It helps to know how to perform basic queries, aggregates (sum (), etc.) and internal joins
• Normalization - database design skills are a basic requirement
• Locking Model/MVCC. , ( MVCC ).
• ACID, Txns. , , .
• . , , , . , .
• . , - , / .

, FOSS , , db.

Answer 2

, , , , . , .

Answer 3

, , , , ( ). - , ?

, , .., , - .

Answer 4

, . , , , , . .

, .

Answer 5

, SQL, , , , . , SQL (T-SQL, PL/SQL ..), .

, , , . , , .

, , , SQL . , , SQL . , , , - .

Answer 6

If you are not sure about the best way to access the database, you should use tried and tested solutions, such as application blocks from Microsoft - http://msdn.microsoft.com/en-us/library/cc309504.aspx . They may also be useful for you by learning how this code is implemented.

Answer 7

Need basic questions about Sql queries. then you can develop a simple system. but when you are going to implement complex systems, you should know the normalization, procedures, functions, etc.