On Thu, 2010-08-19 at 10:21 -0700, sam wrote: > From looking at the dbmetal command line options, there is no way of > defining or limiting which tables should exported into the dbml.
You could probably use `DbMetal /c CONNECTION_STRING`, and within your Connection String use "Initial Catalog" to restrict yourself to a specific database instead of processing every table in the DB. This has the downside that it won't help if the catalog is still gigantic, and I believe it'll fail if you have an assocoation referencing a table in a different catalog/schema. > Q1: Is there some 3rd party tool that will read in the dbml and allow > me to delete the tables I don't want in the dbml files? Any XML editor should work. ;-) > Q2: Has there ever been any thought and/or discussion on adding an -- > includetable or --excludetable option to dbmetal? Not particularly. I suspect using separate catalogs/schemas is the normal answer to this kind of problem. - Jon -- You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/dblinq?hl=en.
