Add database size and auto-growth settings to Visual Studio database projects - by Phil Austin

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


4
0
Sign in
to vote
ID 601532 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 9/19/2010 2:37:40 AM
Access Restriction Public

Description

As described in my blog post here: http://phil-austin.blogspot.com/2010/08/data-dude-erroring-on-deployment-over.html only some database properties are available in VS database projects. In particular size and autogrowth settings are missing. This can cause deployment errors when the settings in the target database are different to the project being deployed. I often opt for non-default options and altering these settings requires some digging around for .sql files on the filesystem which is hardly ideal.

If the intention is to leave this up to the DBA I'd argue that a) the DBA should use the project as well and b) there are already settings in the project that might be regarded as DBA territory (such as collation settings). In any case the project will try to overwrite those settings - regardless of how they are set in the target database!

My suggestion would be to simply add auto-growth and size to the advanced property dialogue along with the other database settings.
Sign in to post a comment.
Posted by Microsoft on 10/1/2010 at 2:08 PM
Hi Phil,

Thank you for submitting this issue. We have been unable to reproduce this issue. We are closing this issue out, but if you continue to experience the same issue, please resubmit this issue.

The error you are getting is caused by file contention. The name of the file is being compared differently, but the path of the file is the same. This causes a file clash. If you set the file names to be the same you avoid this issue. You can also remove the files from the database project altogether and we will create them as needed. It is typically only recommended you model the files in your project in the case you have custom file paths and groups.


Thanks,

Barclay Hill

Sr. Program Manager | Visual Studio Product Team (Data Tools) | Microsoft Corporatio
Posted by Microsoft on 9/19/2010 at 5:03 PM
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)