Server side processing

Server side processing

tdktdk Posts: 26Questions: 14Answers: 0

The explanation of this states..
"There are many ways to get your data into DataTables, and if you are working with seriously large databases, you might want to consider using the server-side options that DataTables provides. With server-side processing enabled, all actions that DataTables performs (such as paging, searching and ordering) are handed off to a server where an SQL engine (or similar) can perform these actions on the large data set (after all, that's what the database engine is designed for!). As such, each draw of the table will result in a new Ajax request to get the required data."

This is just not true, when looking at the resulting SQL output it appears all records are returned to the client then sorted and paged?

Answers

  • kthorngrenkthorngren Posts: 3,998Questions: 19Answers: 877
    edited July 19

    This is just not true, when looking at the resulting SQL output it appears all records are returned to the client then sorted and paged?

    Either you haven't enabled the serverSide option or your server script doesn't use things like limit and order in the query to return only the current page data. Here is a working example of server side processing:
    https://datatables.net/examples/server_side/simple.html

    Also take a look at the SSP docs:
    https://datatables.net/manual/server-side

    Maybe you can provide more information about your setup like Datatables init code and what you are using for your server side script.

    Kevin

Sign In or Register to comment.