Commented Issue: Designer: __RefactorLog table should not show up on tables to import [147]

"Create a Database Project
Create a few tables with some default column names and publish
Now rename a few of the columns
Republish

You end up with a table on the DB called __RefactorLog which supports our refactoring operations.

Now create a separate project and create a new EDMX by referencing the DB you just published (I couldn't get DB Project to work at this point in time - so did ""Generate from Database"" directly).

When you get to page three of the wizard which asks you which objects to import expand the Tables ad schema nodes. You will see __RefactorLog listed. Don't think we should offer to import this as it is a table solely there for our own benefit?



We should _not_ in Entity Designer (or any other designer) offer to import _any_ object marked with the microsoft_database_tools_support extended property.

Query for these objects is as follows:

[c].[object_id] NOT IN (SELECT [major_id] FROM [sys].[extended_properties] WHERE [minor_id] = 0 AND [class] = 1 AND [name] = N'microsoft_database_tools_support'))

Question: is there any situation in which you might want to import these objects?"

This item was migrated from the DevDiv work item tracking system [ID=353484].

Comments: That's a pretty dismissive answer. It's highly irritating to have crap added to the database. If EF needs to add working tables while it does it's thing that's fine but it should clean up after itself.