2 replies
I want this 100 points.
Figure this nightmare:
Suppose you have a big great Company. You develop client /server Visual Basic program to manage your order, stock, etc. Your clients are constantly making transactions, queries, etc and they are hitting hard your SQL server. More tham 1000 employes are connected from inside and outside your office. Suddenly the SQL stops responding and every client loose it?s connection. Your C/S main app. is down! (...and you too!)
Why???? -C/S app and SQL can?t hold much connections. Each connection eat as 8Kb of RAM, and a few cycles of CPU just to keep them alive (that is, without any traffic!)
* Holding many connections Kill a SQL server c/s app. (...so they create the transaction server...)
* C/S app relays on ODBC technologies to connect to their DB server. Think about having 1000 Pc?s all around the world having ODBC failures and modem problems?, What about and ODBC upgrade every 6 month?
and App upgrade, say once a year?
How can you avoid ALL this kind of problems???
Internet. Single client!, no ODBC! integrated with the S.O. (in W9x)! No software deployment, centralized management, descentralized databases all over the world
Standart connection all over the world
You can continue from here...
Thank?s for rating my time.
edt@bancobgn.com
by jimbob404
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending