Home Dashboard Directory Help
Search

SSDT Schema Compare generates scripts for dtproperties table extended properties by Jairo Ramirez


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


2
0
Sign in
to vote
Type: Bug
ID: 788425
Opened: 5/22/2013 12:33:47 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description


We are currently migrating our database to SSDT in order to integrate VS2012 into TFS. When I run the schema compare tool in VS2012 SSDT (From Database to SSDT Project) it generates a extended properties file with the following SQL commands:

EXECUTE sp_addextendedproperty @name = N'MS_Description', @value = 'version';
GO
EXECUTE sp_addextendedproperty @name = N'MS_Description', @value = 'value';
GO
EXECUTE sp_addextendedproperty @name = N'MS_Description', @value = 'uvalue';
GO
EXECUTE sp_addextendedproperty @name = N'MS_Description', @value = 'property';
GO
EXECUTE sp_addextendedproperty @name = N'MS_Description', @value = 'objectid';
GO
EXECUTE sp_addextendedproperty @name = N'MS_Description', @value = 'lvalue';
GO
EXECUTE sp_addextendedproperty @name = N'MS_Description', @value = 'id';

The above commands makes the build/publish proccess to fail because the syntax is wrong. The first time I tried without luck to find which object had these properties to correct them. So I dedided to just erase these lines from the extended properties file. Now the problem is that when I try to update in the opposite way (From SSDT Project to Database) after making all my changes, the schema comparison generate the following lines:

PRINT N'Dropping [dbo].[dtproperties].[id].[MS_Description]...';
GO
EXECUTE sp_dropextendedproperty @name = N'MS_Description';
GO
PRINT N'Dropping [dbo].[dtproperties].[lvalue].[MS_Description]...';
GO
EXECUTE sp_dropextendedproperty @name = N'MS_Description';
GO
PRINT N'Dropping [dbo].[dtproperties].[objectid].[MS_Description]...';
GO
EXECUTE sp_dropextendedproperty @name = N'MS_Description';
GO
PRINT N'Dropping [dbo].[dtproperties].[property].[MS_Description]...';
GO
EXECUTE sp_dropextendedproperty @name = N'MS_Description';
GO
PRINT N'Dropping [dbo].[dtproperties].[uvalue].[MS_Description]...';
GO
EXECUTE sp_dropextendedproperty @name = N'MS_Description';
GO
PRINT N'Dropping [dbo].[dtproperties].[value].[MS_Description]...';
GO
EXECUTE sp_dropextendedproperty @name = N'MS_Description';
GO
PRINT N'Dropping [dbo].[dtproperties].[version].[MS_Description]...';
GO
EXECUTE sp_dropextendedproperty @name = N'MS_Description';

These lines of course generates errors when I try to run the generated script in the Database, but this time It shows me that apparently the problems is the system table dtproperties. We have created several db diagrams but we are not interested in sync them to the SSDT project. Is there any way to ignore system tables or Database diagrams in schema compare? This error are making our transition to SSDT with TFS a nightmare. For me the option to exclude extended properties from the comparison is not a solution because all of our tables have extended properties for column descriptions. Thanks in advance for your help.
Details
Sign in to post a comment.
Posted by Microsoft on 8/13/2013 at 12:02 AM
Hi Jairo,

Thank you for the feedback. There is a way to ignore database level extended properties in Schema Compare, which should address your issue. In the Options dialog for Schema Compare, go to the "Object Types" tab and expand the "Non-Application-scoped" objects. In that list, uncheck the box for "Database Options, Permissions and Extended Properties".

In the latest version of SSDT, this is disabled by default. You can download the latest version at http://msdn.microsoft.com/en-us/data/hh297027.

Thanks,

Martin
Sign in to post a workaround.