Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Architecture> Dependency graph between DAL and SQL Objects?
 

Pages: 1
Architecture
Dependency graph between DAL and SQL Objects?
Page:1/1 

  Print all messages in this thread  
Poster Message
Emmanuel
User



Location:
Ottawa, Canada
Joined on:
13-Jan-2006 23:14:31
Posted:
167 posts
# Posted on: 09-Feb-2010 19:15:24.  
I need a solution for an enterprise environment with 100s of applications and SQL databases. A current architecture standard requires that all applications implement DALs using SPROCs. One reason for this is that, when performing ongoing migration, obsolescing or modifications to databases, dependency graphs between these SPROCs and database objects (including dependencies to objects on linked servers) indicate what applications will be impacted by migrating, removing or modifying a database.

If one were to change the architectural standard to allow ORMs (e.g. LLBLGen), producing dependency graphs this way would not be possible anymore.

Any ideas on how we can produce dependency graphs between DALs implemented using LLBLGen? The solution needs to work statically (i.e. mustn't rely on 'mionitoring' db access during runtime).

Without a solution to this need, I can't propose LLBLGen to the organization.

  Top
Emmanuel
User



Location:
Ottawa, Canada
Joined on:
13-Jan-2006 23:14:31
Posted:
167 posts
# Posted on: 11-Feb-2010 17:33:34.  
bump

  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37879 posts
# Posted on: 11-Feb-2010 19:12:57.  
(If you need an answer from our support staff quickly, don't post in architecture as it's seen as a lower priority forum).

Dependency from entity onto table, you mean? What dependency are you looking for exactly? For example, if you have 400 tables / views and 30 entities mapped onto them, there are a lot of tables/views which aren't mapped and therefore the application doesn't depend on them, is this what you're after?

This is easy to generate from a template into whatever output you want. Using a .lpt template you can traverse the EntityDefinition instances in the project object and emit to the output the target they're mapped on. This gives you a list of targets the project depends on. This can be done statically, on the command line using the command line generator. See the SDK for details about writing templates. Of cource you can also do this in a plugin (as it also has access to the entire object graph) and for example export it to excel in your plugin by opening a form and bind it to a grid which supports exporting to Excel. In v3, this is build into the designer, you can then query the project using any query you want (using Linq, inside the designer) and export the output to excel or other formats.

Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Emmanuel
User



Location:
Ottawa, Canada
Joined on:
13-Jan-2006 23:14:31
Posted:
167 posts
# Posted on: 16-Feb-2010 22:08:17.  
Yes, dependency from entity to table/view/sproc etc.

I'll experiment with the template idea. Indeed having a way to pull LLBLGen projects from version control, running this tools from the command line and generate a dependency report would be perfect.

Thanks.


  Top
Emmanuel
User



Location:
Ottawa, Canada
Joined on:
13-Jan-2006 23:14:31
Posted:
167 posts
# Posted on: 16-Feb-2010 22:08:22.  
Yes, dependency from entity to table/view/sproc etc.

I'll experiment with the template idea. Indeed having a way to pull LLBLGen projects from version control, running this tools from the command line and generate a dependency report would be perfect.

Thanks.
  Top
MTrinder
User



Location:
London by day, Milton Keynes by night.
Joined on:
08-Oct-2008 17:55:47
Posted:
1461 posts
# Posted on: 16-Feb-2010 23:43:39.  
No prob, happy to help. Let us know how you get on.

Matt


  Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.