CREATE PROCEDURE LimitSelect
	@query CHAR (128),	-- SQL query, it'd better be a SELECT!
	@limit INT,		-- limit the result set of the query
	@offset INT		-- start result set from offset
AS
	-- Execute call to declare a global cursor (node_cursor) for the query passed to the SP
	EXEC ('DECLARE node_cursor CURSOR GLOBAL SCROLL READ_ONLY FOR ' + @query)

	-- open the global cursor declared above
	OPEN node_cursor

	-- tweak the starting values of limit and offset for use in the loop
	SET @offset = @offset + 1
	SET @limit = @limit - 1

	-- advanced the cursor to the offset in the result set
	FETCH ABSOLUTE @offset FROM node_cursor 

	-- counter i
	DECLARE @i INTEGER
	SET  @i = 0

	-- loop until limit reached by counter i
	WHILE (@i < @limit)
	BEGIN
		-- fetch the next row in the result set and advance counter i
		FETCH NEXT FROM node_cursor 
		SET @i = @i + 1
	END

	-- clean finish
	CLOSE node_cursor
	DEALLOCATE node_cursor

LimitSelect '
        SELECT * FROM news 
           WHERE 
             cat_id in(10, 11) AND 
             is_disabled=0 AND 
             (news_date BETWEEN 978328800 AND 1009864799 )
           ORDER BY news_date DESC
     ', 5, 1

LimitSelect '
        SELECT * FROM news 
           WHERE 
             cat_id in(10, 11) AND 
             (news_date BETWEEN 978328800 AND 1009864799 )
           ORDER BY news_date DESC
     ', 5, 1

quote:

---

The LimitSelect stored procedure works really well for creating a pagescrolling interface to a table.

---

Duhhhhhhhhhhhhh! Man I hate it when I don't pay attention!

You could declare @query as varchar(8000), just in case you use much more complex SQL statements in the future. That way you won't have to worry about chasing the same problem months or years from now.