How SharePoint is not a database

Part of the problem is that business users to design the lists are not familiar with the basic concepts of databases - that only need to store your information. Part of the problem is false advertising consultants & / or Microsoft SharePoint is a miracle that platform can do anything - it does some things well, but to replace the SQL Server or Access database is not five of them. The other problem is that no nice way for bi-directional coating data from a SharePoint database - the Business Data Catalog only works in read-only mode & does not permit updates back to the underlying data store .
Here is a list of some of the features that have a SharePoint database is not compatible with - the moment that need these features will have a real database.

• Principal and foreign keys: one of the most basic concepts in a database is the application of a unique identifier (either system generated or supplied by the user) that can identify a record and on the link in the table relations of the child's parents.
  
• Transactions: if two changes are needed to go hand in hand and second hand does not want the first change to get rid (canceled).
  
• SQL language: complex queries can be written in the code myself using a standard language. Queries can be saved and purposes.
  
• Stored procedures: the database programmers can write complex routines can be called as the blocks of reusable code.
  
• Indexing and query optimization: is used to improve performance, the index allows the database designer pre-specific index fields that are frequently used in queries to improve performance. In addition, most engine optimization databases must be based on what they are trying to seek to optimize the way data is retrieved.
  
• Data from large binary fields: modern databases allow storing large binary files such as video files, large text books, images, etc in the database. SharePoint can do to get large files like documents, but you only get one per record and a spot of wine.
  
• Access beyond SharePoint: the lists are accessible outside of SharePoint, but only through XML or programming interfaces. Lists are not stores of data to be used for line of business applications made independently of SharePoint because integration is relatively poor compared with the execution of a SQL query in a database.
  
• Cascade Delete: If you delete a registry of parents, their children will also be deleted. In most databases, this can be configured to automatically pass or reject the removal of the parents until the children are deleted first. This eliminates the risk of children orphaned records.

These features are considered basic in databases - that have existed for decades and even more primitive databases such as Access or FileMaker Pro have most of these features.