VS2010 Database project deployment - Rows were detected error, specify table in message

VS2010 Database project deployment - Rows were detected error, specify table in message by Tom Hunter

Closed

as Fixed

Type:	Suggestion
ID:	678292
Opened:	7/4/2011 8:33:42 AM
Access Restriction:	Public

Workaround(s)

view

We often see the following error message when deploying our database projects (using VSDBCMD): .Net SqlClient Data Provider: Msg 50000, Level 16, State 127, Line 12 Rows were detected. The schema update is terminating because data loss might occur.

Seemingly the only way to find out which table schema change is causing the error is to open the generated script in management studio and run each if statement that raises this kind of error.

I think it would be pretty easy to include at least the name of the schema + table in the error message, if not a full summary of the schema update that it's attempting to implement. See expected result in details below for more information.

Details (expand)

Visual Studio 2010

Performance

Create a database project based on an existing database.
Make a schema change that may result in data loss (e.g. drop a column).
Deploy the project to the existing database.

English

Windows Server 2003

English

.Net SqlClient Data Provider: Msg 50000, Level 16, State 127, Line 12 Rows were detected. The schema update is terminating because data loss might occur.

As an example (the message would change based on the update occurring):
.Net SqlClient Data Provider: Msg 50000, Level 16, State 127, Line 12 Rows were detected IN TABLE [X].[Y]. THE SCHEMA UPDATE IS ATTEMPTING TO DROP THE COLUMN [Z]. The schema update is terminating because data loss might occur.

0 attachments

Posted by Microsoft on 10/24/2011 at 2:31 PM

CORRECTION: This bug is under consideration by the SQL Server team. We're tracking it in a different database abd because of that, we closed it as "External".

Thanks

Luiz Santos
ADO.NET PM

Posted by Microsoft on 10/20/2011 at 4:46 PM

Thanks for your feedback. After analyzing this issue, we decided to fix it in a future version of SQL Server (this message belong to the server). Due to infrastructure limitations, we are closing this issue and "External" in order to tarck it in a different database.

Luiz Santos
ADO.NET PM

Posted by Jamie Thomson on 7/4/2011 at 12:49 PM

This is a no-brainer. Please add the table name in. cheers.

Posted by Microsoft on 7/4/2011 at 9:12 AM

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)