So your SharePoint list or perhaps lists are very slow to response or a custom solution that accesses your lists takes a long to complete its processes. What could be the problem? Old, dilapidated hardware? Poor database configuration? Slow network? How about the fact that many SharePoint solutions are designed as if they are a relational database.
After a long hiatus, I would like to start things off with something I brought forward to one of my clients the other day. Even though SharePoint looks like a fantastic place to build easy database solutions (like a replacement for MS Access) it simply is not built to do that. To the user SharePoint lists look completely separate from each other. So why can’t we simply create DB table like lists and have them reference each other, like having columns that are basically foreign keys to other lists just like a DB table?