Any thoughts on this process?

Question

Any thoughts on this process?

curious_sqldba

SSC-Dedicated

Points: 36494
More actions
February 16, 2013 at 11:12 pm

#274166

This is more of generic programming question. We have a stored procedure which is used on many of our applications built using asp.net. The sp basically first gives total count of pages and then displays the records. I would like to NOT include the count in the sp because it is most expensive ( very bad design, i will tried my best to optimize didnt find much luck). Is there any other way this can be calculated like in asp.net or somewhere else?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

ChrisM@Work SSC Guru Points: 186127 More actions · Answer 1

sqldba_newbie (2/16/2013)
This is more of generic programming question. We have a stored procedure which is used on many of our applications built using asp.net. The sp basically first gives total count of pages and then displays the records. I would like to NOT include the count in the sp because it is most expensive ( very bad design, i will tried my best to optimize didnt find much luck). Is there any other way this can be calculated like in asp.net or somewhere else?

Please post the actual plan for the stored procedure.

^{“Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw}

For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden

Orlando Colamatteo SSC Guru Points: 182279 More actions · Answer 2

The sp basically first gives total count of pages and then displays the records.

Please define "total count of pages."

There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato

Steve Thompson-454462 SSCrazy Points: 2624 More actions · Answer 3

I'm assuming that total number of pages is a presentation-level metric indicating that at a rate of x records per page, you'll need to link to, and maybe display a label that indicates there are, y total pages. In other words if you show 10 records per page and the data set has 100 rows, you'll have 10 pages.

If so, this can very easily be done in your .NET layer. If you're using ADO objects to extract the data you can easily do something like Datatable.Rows.Count to calculate the total number of rows returned (I believe you can use a similar Count function if you're using Linq). Divide the row count by number of rows per page (adjusting for any remainder, of course) and you should be good to go.

If my assumption of what you meant by page count is off, I apologize.

curious_sqldba SSC-Dedicated Points: 36494 More actions · Answer 4

Steve Thompson-454462 (2/19/2013)
I'm assuming that total number of pages is a presentation-level metric indicating that at a rate of x records per page, you'll need to link to, and maybe display a label that indicates there are, y total pages. In other words if you show 10 records per page and the data set has 100 rows, you'll have 10 pages.
If so, this can very easily be done in your .NET layer. If you're using ADO objects to extract the data you can easily do something like Datatable.Rows.Count to calculate the total number of rows returned (I believe you can use a similar Count function if you're using Linq). Divide the row count by number of rows per page (adjusting for any remainder, of course) and you should be good to go.
If my assumption of what you meant by page count is off, I apologize.

This is EXACTLY what i was looking for.Would you have a article for reference which will define the steps which you have mentioned?

Steve Thompson-454462 SSCrazy Points: 2624 More actions · Answer 5

sqldba_newbie (2/19/2013)
Steve Thompson-454462 (2/19/2013)
I'm assuming that total number of pages is a presentation-level metric indicating that at a rate of x records per page, you'll need to link to, and maybe display a label that indicates there are, y total pages. In other words if you show 10 records per page and the data set has 100 rows, you'll have 10 pages.
If so, this can very easily be done in your .NET layer. If you're using ADO objects to extract the data you can easily do something like Datatable.Rows.Count to calculate the total number of rows returned (I believe you can use a similar Count function if you're using Linq). Divide the row count by number of rows per page (adjusting for any remainder, of course) and you should be good to go.
If my assumption of what you meant by page count is off, I apologize.
This is EXACTLY what i was looking for.Would you have a article for reference which will define the steps which you have mentioned?

I'm not sure how your Data Access Layer is constructed. If you use the SQLClient library to talk to your SQL Server back-end, you can create a SQLDataAdapter and use that to fill a DataTable or DataSet (a container that holds multiple DataTables). Once you have a DataTable filled with the results of your SQLCommand, you can get the row count with DataTable.Rows.Count.

Here's a link to the MSDN page on using SQLDataAdapters: http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqldataadapter%28v=vs.71%29.aspx.

Here's the page on System.Data.DataTable: http://msdn.microsoft.com/en-us/library/system.data.datatable.aspx

Note that if you're using a firehose-type construct to consume your data (e.g. a DataReader) you would not be able to get the row count without cursoring through the result set.