1. Beyond the first course in database design and application:

2. Much more experience with design and ER modeling – especially with some fairly complex models. …and especially with fine tuning.

3. More experience with stored procedures and triggers – especially when triggers can be helpful and when they can be a problem. Greater knowledge of T-SQL Greater knowledge of.NET classes An internship if possible

4. We just touched on concurrency, locks, and transactions. There is SO-O-O much more there – especially determining how to define transactions appropriately. Also transaction properties (ACID)

5. Data warehousing (never even covered in class) http://www.webopedia.com/TERM/D/d ata_warehouse.html Data marts http://www.webopedia.com/TERM/D/d ata_mart.html

6. Data mining: use of sophisticated statistical and mathematical techniques to perform what-if analyses, to make predictions, and to facilitate decision making. For example, data mining techniques can analyze past cell phone usage and predict which customers are likely to switch to a competing phone company (Kroenke)

7. http://www.webopedia.com/TERM/D/data_mining.h tml Retail application. If something is on sale, can you increase the price of something else to help offset the price reduction? And actually come out ahead? Data mining can help understand consumer buying patters. http://books.google.com/books?id=YAYAAAAAMBAJ&pg=PA 22&lpg=PA22&dq=data+mining+owen+bly&source=bl&ots=4 8XiJuNPGV&sig=MWd3oBV1NEUXoByQFyHZR0oMRNY&hl =en&ei=DXvlTsrBHYH2ggf4h5yKBQ&sa=X&oi=book_result& ct=result&resnum=1&ved=0CCAQ6AEwAA#v=onepage&q&f =false

8. Security: there is a class framework devoted solely to setting up security. Other databases? It can’t hurt. Oracle, MySQL, IBM’s DB2

9. Backup and recovery processes MUST NOT LOSE DATA