split datatable and send it to ajax response one by one

<center>
<input type="button" id="btn" value="Get Data" />
<div>
<table id="tbl">
<tr>
<th>Idth>
<th>Nameth>
<th>Addressth>
<th>Phoneth>
<th>Emailth>
<th>Projectth>
<th>Roleth>
<th>Statusth>
<th>Completionth>
tr>
table>
div>
center>

"text/javascript">
$(document).ready(function () {
// var myjson = JSON.stringify(Employee);
$('#btn').on('click', function () {
$.ajax({
type: 'Post',
url: "/api/com_serialize_data",
// data: myjson,
//dataType: 'json',
contentType: "application/json; charset=utf-8;Content-Encoding=gzip",
// ContentEncoding: gzip,
success: function (response) {
var employees = JSON.parse(response);
var tr;
for (var i = 0; i < employees.length; i++) {
tr = $('');
tr.append("" + employees[i].Id + "");
tr.append("" + employees[i].Name + "");
tr.append("" + employees[i].Address + "");
tr.append("" + employees[i].Phone + "");
tr.append("" + employees[i].Email + "");
tr.append("" + employees[i].Project + "");
tr.append("" + employees[i].Role + "");
tr.append("" + employees[i].Status + "");
tr.append("" + employees[i].Completion + "");
$('#tbl').append(tr);
$('tr')
}
},
error: function (errorThrown) {
alert(errorThrown);
}
});
});
});

public class com_serialize_dataController : ApiController
{
[HttpPost]
public async Task <string> Employee()
{
DataTable dt = new DataTable();
dt.Columns.AddRange(new DataColumn[9] {
new DataColumn("Id", typeof(int)),
new DataColumn("Name", typeof(string)),
new DataColumn("Address",typeof(string)),
new DataColumn ("Phone",typeof(string)),
new DataColumn ("Email", typeof(string)),
new DataColumn ("Project", typeof(string)),
new DataColumn("Role",typeof(string)),
new DataColumn ("Status",typeof(string)),
new DataColumn("Completion",typeof(string))
});
for (int i = 0; i < 1000; i++)
{
dt.Rows.Add(i, "Ashok We've also got a Draw counter. This is important, because DataTables ke var j = 1;eps a count of the number of times it 00redraws the table. Every time you interact with thej++table, DataTables fetches the data again from the server. It also increments that counter. When the call comes back with the data, the Draw parameter needs to be there with that same value or we'll get an error. You can read more about the parameters here: DataTables: Server Side", "Faridabad We've also got a Draw counter. This is important, because DataTables keeps a count of the number of times it redraws the table. Every time you interact with the table, DataTables fetches the data again from the server. It also increments that counter. When the call comes back with the data, the Draw parameter needs to be there with that same value or we'll get an error. You can read more about the parameters here: DataTables: Server Side", "0654546644 We've also got a Draw counter. This is important, because DataTables keeps a count of the number of times it redraws the table. Every time you interact with the table, DataTables fetches the data again from the server. It also increments that counter. When the call comes back with the data, the Draw parameter needs to be there with that same value or we'll get an error. You can read more about the parameters here: DataTables: Server Side", "[email protected] We've also got a Draw counter. This is important, because DataTables keeps a count of the number of times it redraws the table. Every time you interact with the table, DataTables fetches the data again from the server. It also increments that counter. When the call comes back with the data, the Draw parameter needs to be there with that same value or we'll get an error. You can read more about the parameters here: DataTables: Server Side", "Signage We've also got a Draw counter. This is important, because DataTables keeps a count of the number of times it redraws the table. Every time you interact with the table, DataTables fetches the data again from the server. It also increments that counter. When the call comes back with the data, the Draw parameter needs to be there with that same value or we'll get an error. You can read more about the parameters here: DataTables: Server Side", "Devloper We've also got a Draw counter. This is important, because DataTables keeps a count of the number of times it redraws the table. Every time you interact with the table, DataTables fetches the data again from the server. It also increments that counter. When the call comes back with the data, the Draw parameter needs to be there with that same value or we'll get an error. You can read more about the parameters here: DataTables: Server Side", "Progress We've also got a Draw counter. This is important, because DataTables keeps a count of the number of times it redraws the table. Every time you interact with the table, DataTables fetches the data again from the server. It also increments that counter. When the call comes back with the data, the Draw parameter needs to be there with that same value or we'll get an error. You can read more about the parameters here: DataTables: Server Side", "02/12/2019 We've also got a Draw counter. This is important, because DataTables keeps a count of the number of times it redraws the table. Every time you interact with the table, DataTables fetches the data again from the server. It also increments that counter. When the call comes back with the data, the Draw parameter needs to be there with that same value or we'll get an error. You can read more about the parameters here: DataTables: Server Side");
}
var totalRows = dt.Rows.Count;
var halfway = totalRows / 2;
var firstHalf = dt.AsEnumerable().Take(halfway).CopyToDataTable();
var secondHalf = dt.AsEnumerable().Skip(halfway).Take(totalRows - halfway).CopyToDataTable();
if ()
{
return JsonConvert.SerializeObject(firstHalf);
}
await Task.Delay(1000);
return JsonConvert.SerializeObject(secondHalf);
}
}