Comments on: Handling Recursive Relates with SubSonic and LINQ http://briannoyle.wordpress.com/2009/01/14/handling-recursive-relates-with-subsonic-and-linq/ Rants on GIS, .NET, and life in general Mon, 21 Sep 2009 12:56:28 +0000 http://wordpress.com/ hourly 1 By: homebrutrout http://briannoyle.wordpress.com/2009/01/14/handling-recursive-relates-with-subsonic-and-linq/#comment-172 homebrutrout Fri, 16 Jan 2009 17:07:30 +0000 http://briannoyle.wordpress.com/?p=109#comment-172 Dylan, Good catch. Probably not appropriate at all for large data pulls. Basically this solution works well for us because there will be three to 5 parent menus each with 3-5 items and no users (admin or otherwise) can edit those settings. I just wanted the schema in place for use elsewhere or otherwise I wouldn't even pull it from the DB in favor of an XML in the web project. CTEs are an excellent choice in your case because it keeps the load in the DB where it belongs...and where the optimization for such things is. We have a similar scenario for "project" related records which can return many thousands of records...for that we are using your CTE solution via an SP...the first option I mentioned above. Dylan,

Good catch. Probably not appropriate at all for large data pulls. Basically this solution works well for us because there will be three to 5 parent menus each with 3-5 items and no users (admin or otherwise) can edit those settings. I just wanted the schema in place for use elsewhere or otherwise I wouldn’t even pull it from the DB in favor of an XML in the web project. CTEs are an excellent choice in your case because it keeps the load in the DB where it belongs…and where the optimization for such things is.

We have a similar scenario for “project” related records which can return many thousands of records…for that we are using your CTE solution via an SP…the first option I mentioned above.

]]> By: Dylan http://briannoyle.wordpress.com/2009/01/14/handling-recursive-relates-with-subsonic-and-linq/#comment-171 Dylan Fri, 16 Jan 2009 03:37:52 +0000 http://briannoyle.wordpress.com/?p=109#comment-171 Nice find on the hierarchy building. I still think it's highly dependent upon the size of the dataset and the environment in which you are using the final data. For example today I had to crunch 14K records in to a hierarchy - needless to say I didn't want to grab all that data from the server and LINQ-ify it so I just went with a CTE than ran in under 1 second. I prefer one large hit to the database vs. tens or hundreds of smaller ones (even AJAX-y) to respond to user actions just like you do, so I suppose there's a place for both CTEs and LINQ hierarchies. Nice post. Nice find on the hierarchy building. I still think it’s highly dependent upon the size of the dataset and the environment in which you are using the final data. For example today I had to crunch 14K records in to a hierarchy – needless to say I didn’t want to grab all that data from the server and LINQ-ify it so I just went with a CTE than ran in under 1 second.

I prefer one large hit to the database vs. tens or hundreds of smaller ones (even AJAX-y) to respond to user actions just like you do, so I suppose there’s a place for both CTEs and LINQ hierarchies.

Nice post.

]]>