Skip to main content

Return top N rows from datatable

Normally to return top N rows we use an SQL statement similar to the one below

Select top N * from table

but How can we achieve the same thing in DataTable
I have seen many examples, using different methods. Most of the methods centered around the idea of creating new columns with automatic values increment and using them as index 

There is better method using LINQ 

public  DataTable GetTopNFromDataTable(int TopRowCount, DataTable dtSource)

            var dtTrec = from item in dtSource.AsEnumerable()
                         select item;
            var topN = dtTrec.Take(TopRowCount);
            DataTable dtNew = new DataTable();
            dtNew = dtSource.Clone();

            foreach (DataRow drrow in topN.ToArray())


            return dtNew;

var dtTrec - stores the item in datatable, Using the Take function of Linq the first N rows is filtered

            var topN = dtTrec.Take(TopRowCount);

Now how to retrieve the rows between N1 & N2, just use the skip function along with Take as shown below

public DataTable GetTopBetweenFromDataTable(int intFrom, int intTo, DataTable dtSource)

   var topN = dtTrec.Skip(intFrom).Take(intFrom);




Anonymous said…
Dim query = From c In dt.AsEnumerable _
Order By c.Field(Of Decimal)("list_order") Descending, _
c.Field(Of DateTime)("insert_date") Descending

Dim query1 = From c In query.Take(5).AsEnumerable
rptNews.DataSource = query1

Popular posts from this blog

SCRUM- Who should write a user story

Traditionally user stories (or requirements) were written by Business analysts. They used to prepare big documents after months of study. It was a herculean task. I used to get such UI/Functional specification documents. I have fixed a lot of bugs because I missed few text in such 1000 + pages document. This is not the only interesting part. Some of the requirements were so weird that I often wondered why I am creating the features which no one is going to use. If I had the option I would have recommended a better option. If the BA’s misunderstood some requirements & customers failed to correct those few words in the epic requirement then we will have a nice situation.
In the agile world the story is different. Product Owners are primarily responsible for user stories. But can anyone else also contribute? Yes. Definitely yes In actual environment many users write user stories. The first requirement may come from end user. The PO, tech architect, scrum master, BA’s... anyone can upd…

What are the rules of scrum?

A relatively new person to scrum asked me this question last day. My answer to that person was yes. But really does the scrum have any rules? Scrum is a framework which helps us in developing software. It has very few rules and apart from those basic rules rest of them are guidelines like best practices.

Some of the rules 

The roles of Scrum
•Scrum Master -
•Product Owner
•Feature TeamThe PDCA cycle ( )  frequent communication about risks (daily)
•Plan – Sprint planning
•Do – Actual engineering sprint – deliver a potential shippable code
•Check – Sprint review
•Act – Retrospective 
The scrum guide @ will be a good guideline for teams/companies planning to start scrum. If you are following the recommendation in these then you are following scrum.
Apart from these rest of the ceremonies and artifacts are there…

PDCA & SCRUM (or Agile); Why is it important?

The PDCA (Plan DO Check Act) cycle was made popular by Dr. W. Edwards Deming. This is a scientific cyclic process which can be used to improve the process (or product). This is cyclic in nature and usually time boxed.

This is the first stage of the process. During this step the team discusses the objectives, the process and the clear conditions of exit (conditions of acceptance). This stage sets the measurable and achievable goals for the team.

Team works together to achieve the objective set in the planning phase. Team works with the set of agreed process.

Once the implantation is done team regroups and verifies the output and compares it to the agreed conditions of acceptance decided during the planning phase. The deviation, if any, is noted down.

If any deviation in planned tasks is observed during the Check stage, a root cause analysis is conducted. Team brainstorms and identifies the changes required to prevent such deviations in future. Team also brainstorms idea…