By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,364 Members | 1,341 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,364 IT Pros & Developers. It's quick & easy.

Getting record position in sql server 2000

P: n/a
hi

i am using SQL server 2000. I want to know the record position while
retrieving records. its like row_number() in sql server 2005

Is it possible?
Mar 25 '08 #1
Share this Question
Share on Google+
5 Replies


P: n/a
On Tue, 25 Mar 2008 05:24:49 -0700 (PDT), sh************@gmail.com
wrote:

There rarely is a good reason for needing a row number. What is yours?
-Tom.

>hi

i am using SQL server 2000. I want to know the record position while
retrieving records. its like row_number() in sql server 2005

Is it possible?
Mar 25 '08 #2

P: n/a
Tom van Stiphout (no*************@cox.net) writes:
There rarely is a good reason for needing a row number. What is yours?
The row_number() function is one of the absolutely most useful additions
to SQL 2005. The only thing that can compete is the new error handling.
There are so many problems which are solved easily and efficiently with
the row_number function.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Mar 25 '08 #3

P: n/a
On Mar 26, 3:47 am, Erland Sommarskog <esq...@sommarskog.sewrote:
Tom van Stiphout (no.spam.tom7...@cox.net) writes:
There rarely is a good reason for needing a row number. What is yours?

The row_number() function is one of the absolutely most useful additions
to SQL 2005. The only thing that can compete is the new error handling.
There are so many problems which are solved easily and efficiently with
the row_number function.

--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se

Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
thanks to all.
the solutions are pretty good. But not feasible to me. is any other
solution available. If so then plz help
Mar 26 '08 #4

P: n/a
(sh************@gmail.com) writes:
thanks to all.
the solutions are pretty good. But not feasible to me. is any other
solution available. If so then plz help
If they are not feasible to you, it would be a good thing if you could
provide more details the problem you are trying to solved, and why the
suggested solutions will not work for you.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Mar 26 '08 #5

P: n/a
sh************@gmail.com wrote:
On Mar 26, 3:47 am, Erland Sommarskog <esq...@sommarskog.sewrote:
>Tom van Stiphout (no.spam.tom7...@cox.net) writes:
>>There rarely is a good reason for needing a row number. What is yours?
The row_number() function is one of the absolutely most useful additions
to SQL 2005. The only thing that can compete is the new error handling.
There are so many problems which are solved easily and efficiently with
the row_number function.

--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se

Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

thanks to all.
the solutions are pretty good. But not feasible to me. is any other
solution available. If so then plz help
Why aren't they feasible to you? Can you give an example with a small
amount of sample data, and explain in conceptual terms what you would
want to do with that sample data?
Mar 26 '08 #6

This discussion thread is closed

Replies have been disabled for this discussion.