SQL Server Performance

Data Tables in Client Memory for fast Access

Discussion in 'Analysis Services/Data Warehousing' started by alisalman, Dec 19, 2006.

  1. alisalman New Member

    We are working on an stock market application to buy and sell stock market shares. Our application working good on local network.
    We are planing to use our applicaion from dailup connection, but we getting a problem of slow performance (due to using database operation like insert/delete/update table queries, which are taking time on internet) while our application requiment is real time operation.

    We are supposing that client system does not have any access to database like sql or oracle etc. we want to create data tables in client memory so that our application read/update data from/to memory data tables (like read/update from database table) to save time without going to server database, we known that there would be requirement of loading data in clinet memory in each time the client application start or connect with server (like - we have to do synchronize all ServerData and client MemoryData at start of application).

    My question is that how can we create these memory tabels like tables in databse to query the data from memory table, or how do we load server database table data in client memory, is there any API available to create these things, or we have to create
    our own API, or any other solution for that problem.


  2. Chappy New Member

    Depends what your client language is I guess, and also what sort of size dataset were talking about.

    ADO.NET allows you to create disk or memory based XML datasets, which you can then query to a limited degree.
    Alternatively simply populate the results into memory in your own custom structs.

    What Id be more worried about is whether it matters if changes made locally arent synced back to the main server.
    What if the client crashes, or their net connection goes down? If this is an issue then Id really consider some sort of ransactional database client side (maybe MSDE/SQL Express).

    You could also then think about merge replication as a way to reliably sync the changes back up to server

Share This Page