
October 13th, 2011, 07:56 AM
|
|
Registered User
|
|
Join Date: Sep 2011
Posts: 2
Time spent in forums: 26 m 10 sec
Reputation Power: 0
|
|
XML inside the database has too much (server-side) overhead to support transaction processing, it's mainly appropriate for batch/offline processing and infrequent bulk transfers (import/export) between different databases/products/systems. When XML is running in the SQLServer, the SQLServer will begin to get slower and slower as more and more concurrent users are added, so that all connected users (not just the most recent connections) receive miserable performance.
The alternative is to always interact with SQLServer using its high-speed binary ODBC interface (or one of its proprietary APIs). You can do that remotely from the iPhone using an SDK, or you can custom code a web-service that translates your own GET/PUT requests into ODBC/proprietary database calls (so that when you hit the tipping point, the most recent transactions will have to wait to get on the database, but the already connected users will not suddenly slow to a crawl trying to get their result set).
Quote: | Originally Posted by wyandavidson Hey guys:
Do you guys know any iphone app which interact with SQL Server through XML. which can give me the idea how to interact with SQL Server through XML? |
|