My problem is this:
We have a very large Legacy DB with many SPROCs, Views & Tables.
The Designer is a "NO GO" b/c of the size.
I've configured SQL Metal to build the data context, but the resulting code file is so big (12MB) visual studio 2008 will not open it.
If SQLMetal would generate a new file for each class type (Table, View, SPROC_Result), I would be okay.
But as it works currently, I'm hosed.
Ideas??
Best Answer
You could do this:
In your filter phase (step 2) you could also create other arbitrary divisions of your .dbml file based on other requirements. Perhaps filter out some unnecessary tables or views. Or break the tables into logical components with separate DataContexts.