Database

DECLARE @sqlStatement NVARCHAR(1000)
 
SET @sqlStatement='SELECT AgentsSubGroupID 
                   FROM Agent_Markup_Fare 
                   WHERE AgentsSubGroupID IN(INVARIABLES)'
 
SET @sqlStatement = REPLACE(@sqlStatement,'INVARIABLES',@AgentPreferencesIDS)
 
CREATE TABLE #tmpTbl (AgentsSubGroupId INT NOT NULL)
 
INSERT INTO #tmpTbl
EXEC(@sqlStatement)
 
SELECT 
    @adultmarkup=SUM(dbo.CalculateMarkup(@fareprice,adultMarkup)),
    @childmarkup=SUM(dbo.CalculateMarkup(@fareprice,childMarkup)),
    @infantmarkup=SUM(dbo.CalculateMarkup(@fareprice,infantMarkup)),
    @studentmarkup=SUM(dbo.CalculateMarkup(@fareprice,studentMarkup))
FROM 
    Agent_Markup_Fare 
WHERE 
    fareid=@fareid AND 
    AgentsSubGroupID IN (SELECT AgentsSubGroupID FROM #tmpTbl)
 
DROP TABLE #tmpTbl

DECLARE @Id int;
SELECT @Id = 1;
WHILE @Id IS NOT NULL
BEGIN
    -- Do stuff you need to do here.
 
    -- The next line moves to the next item in the linked list.
    SELECT @Id = NextId FROM MyTable WHERE Id = @Id;
END

Rob Philpott wrote:

Why do you say this isn't really what Sql is designed to do? It seems perfectly acceptable, desirable even (well to me at least!) to have an abstraction where a database can maintain a linked list of data. My operations would be 'return in order', 'delete item in list', 'insert item in list'.

Rob Philpott wrote:

What's the weather like in Scotland? It's been a bit stormy down in London over the past few days.