• I don't think there's a need to use ROW_NUMBER(), unless something like this doesn't get it for you:

    ;WITH ModuleHieararchy AS (

    SELECT [SModuleId], [ModuleId], [SMName]

    ,[SDate]

    ,[EDate]

    ,[Status]

    ,[ToolTip]

    ,[ParentId]

    ,n=1

    ,SM1=[SModuleId]

    ,SM2=[SModuleId]

    FROM ES_SubModuleMaster1

    WHERE [ParentId] = 0

    UNION ALL

    SELECT a.[SModuleId], a.[ModuleId], a.[SMName]

    ,a.[SDate]

    ,a.[EDate]

    ,a.[Status]

    ,a.[ToolTip]

    ,a.[ParentId]

    ,n+1

    ,SM1

    ,SM2=a.[SModuleId]

    FROM ES_SubModuleMaster1 a

    JOIN ModuleHieararchy b ON a.ParentID = b.sModuleID

    )

    SELECT [SModuleId], [ModuleId], [SMName]

    ,[SDate]

    ,[EDate]

    ,[Status]

    ,[ToolTip]

    ,[ParentId]

    FROM ModuleHieararchy

    ORDER BY SM1, SM2, n

    Ignoring your CONVERTs on date of course.


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    My thought question: Have you ever been told that your query runs too fast?

    My advice:
    INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
    The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

    Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
    Since random numbers are too important to be left to chance, let's generate some![/url]
    Learn to understand recursive CTEs by example.[/url]
    [url url=http://www.sqlservercentral.com/articles/St