EDN Admin
Well-known member
I am pulling a set of unique rows from a data table in a sql server DB that are based on some parameters . I may have 500 rows, maybe 1000 rows returned of just unique ID values (one column of data) from this first data pull. I then need
to pull another dataset that is joined to the table of unique IDs. Normally, I would create a stored procedure on the server, submit the params to the sp, generate the first dataset of unique IDs and then generate the 2nd dataset that would be from a
join to the first dataset in the stored procedure. I was hoping to reduce overhead on the server by pulling the first dataset to a dataTable that is local to the app and then pulling the 2nd dataset from -- like a Linq join to the local dataTable
to the other table on the server. Would something like this be possible? Would this be advisable? Or should I stay with the SP routine? If yes on a Linq join -- how would this look -- the code that is? How would I join the contents
of the local dataTable to the DataTable on the server?
Thanks
<
Rich P
<br/>
<br/>
View the full article
to pull another dataset that is joined to the table of unique IDs. Normally, I would create a stored procedure on the server, submit the params to the sp, generate the first dataset of unique IDs and then generate the 2nd dataset that would be from a
join to the first dataset in the stored procedure. I was hoping to reduce overhead on the server by pulling the first dataset to a dataTable that is local to the app and then pulling the 2nd dataset from -- like a Linq join to the local dataTable
to the other table on the server. Would something like this be possible? Would this be advisable? Or should I stay with the SP routine? If yes on a Linq join -- how would this look -- the code that is? How would I join the contents
of the local dataTable to the DataTable on the server?
Thanks
<
Rich P
<br/>
<br/>
View the full article