Advantages and disadvantages depend on the situation. In the event there are many users generating thousands to hundreds of thousands of transactions, taking into account concurrency issues, response times and scalability, one would generally suggest a client/server system. However, if there is a small application used by one user, a non-distributed system may best suit ones needs.
Another constraining factor is staff, hardware, licensing and/or budget. The availability of these resources will have an impact on what kind of system is delivered.
To best answer this question I would need more information:
- How many users are expected to utilize the system?
- What type of solution is desired? It could be as simple as a phone book application to as complicated as a financial application.
- Is there or will there be staff on hand to deliver the solution?
- Is there staff available that has the necessary skill set to administer and maintain the system?
For More Information
- What do you think about this answer? E-mail us at editor@searchDatabase.com with your feedback.
- The Best Microsoft SQL Server Web Links: tips, tutorials, scripts, and more.
- The Best SQL Web Links
- Have a SQL Server tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical SQL Server questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, Oracle, SQL Server, DB2, metadata, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.