Get all nested subcategories or data from a table in sql server

Get all nested subcategories or data from a table in sql server


Consider the situation-
ID      Name                 PID
1       a                         0        
2       -a.a                     1
3       --a.a.a                2
4       --a.a.b               2
5       ---a.a.b.a           4
6       ---a.a.b.b           4
7       ----a.a.b.b.a       6
8       -a.b                   1
9       -a.c                   1
10      --a.c.a              9
11      --a.c.b              9
12      b                      0
13      -b.a                 12
14      -b.b                 12
15      --b.b.a             14

and you want to select all the subcategories to n level under any category i.e.
if you want that all subcategories under "b" will be selected -
Result-
12      b                       0
13      -b.a                  12
14      -b.b                  12
15      --b.b.a              14

or

All subcategories under category "a" -
result-
1       a                        0        
2       -a.a                    1
3       --a.a.a                2
4       --a.a.b               2
5       ---a.a.b.a           4
6       ---a.a.b.b           4
7       ----a.a.b.b.a      6
8       -a.b                   1
9       -a.c                   1
10      --a.c.a              9
11      --a.c.b              9

-- =============================================
CREATE PROCEDURE [dbo].[Sp_SubCategoryListings]
    -- Add the parameters for the stored procedure here
    @ID int
    AS
    BEGIN
    WITH childCatagories(oids,name, child_oids,RecursionLevel) AS
   (
    SELECT b.ID,b.Name, b.PID, 0 AS RecursionLevel
    FROM dbo.tbl_category AS b
   WHERE b.PID = @ID -- 'everything for the home' oid
   UNION ALL
   SELECT bom.ID, bom.Name,bom.PID, RecursionLevel + 1
   FROM dbo.tbl_category AS bom
   INNER JOIN childCatagories AS p
  ON bom.PID = p.oids
   )
  SELECT * FROM childCatagories AS p ORDER BY RecursionLevel
  OPTION (MAXRECURSION 1000);
  END

Comments

Post a Comment

Popular posts from this blog

Google to FTS Syntax Cheat Sheet

Image
OPERATOR EXAMPLE DESCRIPTION   nut Searches for inflectional forms of the word nut crank arm crank AND arm Searches for documents containing inflectional forms of the words crank AND arm crank and ann. The keyword AND is optional. tire OR air Searches for documents containing inflectional forms of the words tire or air, “reflector bracket” Performs a phrase search for the phrase "reflector bracket". hardware -bracket Searches for documents containing inflectional forms of the word hardware but not the word bracket. +clamp Searches for the word darn') without generating inflectional forms. ~seat Searches for thesaurus forms of the word seat Assemb* Searches for words that begin with the prefix assemb . <washer nut> Searches for documents that contain the words washer in close proximity to the word nut
Read more

@@rowcount

@@rowcount is a global variable reports the number of affected rows in the most recently executed statement. Just like @@error you need to save it in a local variable if you want to use the value later, since @@rowcount is set after each statement. Since with SET you can only assign variable at a time, you must use SELECT if you need to save both @@error and @@rowcount into local variables: SELECT @err = @@error, @rowc = @@rowcount (For this reason, I prefer to always use SELECT for variable assignment, despite Microsoft's recommendations to use SET.) In T-SQL it is not an error if, for instance, an UPDATE statement did not affect any rows. But it can of course indicate an error in your application, as it could be an error if a SELECT returns more that one row. For these situations, you can check @@rowcount and raise an error and set a return value, if @@rowcount is not the expected value.
Read more

Sql Index

Image
Indexes help us retrieve data from tables quicker. Let's use an example to illustrate this point: Say we are interested in reading about how to grow peppers in a gardening book. Instead of reading the book from the beginning until we find a section on peppers, it is much quicker for us to go to the index section at the end of the book, locate which pages contain information on peppers, and then go to these pages directly. Going to the index first saves us time and is by far a more efficient method for locating the information we need. The same principle applies for retrieving data from a database table. Without an index, the database system reads through the entire table (this process is called a 'table scan') to locate the desired information. With the proper index in place, the database system can then first go through the index to find out where to retrieve the data, and then go to these locations directly to get the needed data. This is much faster.
Read more