An Overview of the New Database Project Wizard
You can use the New Database Project Wizard as an easy way to create the database project, optionally import a schema from a database, and configure your build settings. Although you can follow these steps manually, the wizard guides you through the steps until you become more familiar with them or until you have to adjust advanced settings that are not available in the wizard.
For information about how to access the wizard, see How to: Create Database Projects.
Specify Project Properties
You use this page of the wizard to specify properties about the database project that you want to create.
| Field | Default Value | Notes |
|---|---|---|
Project organization |
Organize my project by object type |
This field indicates whether the files in the database project are organized primarily by schema or by object type. If your database contains multiple schemas that include logical groupings of database objects, you might want to organize them by schema. Important You cannot change the automatic file organization after the project is created. You can manually rearrange files after they are added to the solution, but they will always be added according to the specified project organization. |
Default schema for new objects |
dbo |
This field indicates in which schema objects should be put when you add objects to the database project. |
Include Schema name in the file name |
Yes |
This check box indicates whether the schema name should be included as part of the file name for database objects. For example, if the dbo schema contains a table that is named Orders and this check box is selected, the file name is dbo.Orders.table.sql. If this check box is cleared, the file name is Orders.table.sql. |
Enable full text search |
Yes |
This check box indicates whether full text search support should be enabled in the target database. |
Enable SQLCLR |
No |
This check box indicates whether SQLCLR integration should be turned on for the target database. |
Set Database Options
You use this page of the wizard to specify options on the database. You can later adjust these options in the project properties. For more information, see How to: Configure Database Projects for Build and Deployment.
| Field | Default Value |
|---|---|
ANSI padding |
Yes |
ANSI nulls |
Yes |
ANSI warnings |
Yes |
Arithmetic abort |
Yes |
Numeric round abort |
No |
Concat nulls yields null |
Yes |
Quoted identifier |
Yes |
Database Collation |
SQL_Latin1_General_CP1_CS_AS |
For more information about these settings, see An Overview of Database Project Settings.
Import Database Schema
You can use this page of the wizard to specify a source database from which to import the database schema. In addition, you can set options that configure aspects of the import operation.
| Field | Default Value | Notes |
|---|---|---|
Import existing schema |
No |
If you select this check box, you can specify a database from which to import a database schema and settings. If you clear this check box, you will create an empty database project into which you can later import a database schema or into which you can add objects. Note The other fields in this section are enabled only if you select this check box. |
Source database connection |
None |
You use this field to specify the source database from which you want to import the database schema. If no connection is available, you can create one. For more information, see How to: Create a Database Connection. If you do not specify a source database connection, no schema will be imported, but you can import other project settings. This strategy is useful, for example, if you create a database and want to use the wizard to configure the project properties, database options, and build and deployment settings. |
Script the column collation only if it is different from the database collation |
Yes |
If you select this check box, the build script will set the collation for only those columns whose collation does not match the database collation. If you clear this check box, database columns will always have their collation scripted, even if it matches the database collation. |
Ignore extended properties |
No |
If you select this check box, extended properties will not be imported. If you clear this check box, extended properties will be imported. Extended properties can specify a caption for a table or view or an input mask for a column. For more information, see Using Extended Properties on Database Objects. |
Override database configuration with imported schema settings |
No |
If you select this check box, the database settings in the source database will override the settings that you specified on the Set Database Options page. If you clear this check box, the database settings in the source database will be ignored in favor of the settings that you specified on the Set Database Options page. |
Note
By design, the Trustworthy database setting is not imported when you import a database schema. A setting of this nature requires sysadmin permissions and should be set explicitly. You can enable the Trustworthy setting in your database project if you are a sysadmin in the design-time validation database.
Configure Build/Deploy
You can use this page of the wizard to specify how the database project should be built and deployed.
| Field | Default Value |
|---|---|
Build output path |
.\sql\ |
Target connection |
None |
Target database name |
The name that you specified for the project in the New Project dialog box. |
Default location for target database files |
The default location is retrieved from the target server that you specified in the target connection. |
Default deployment collation |
None |
Always re-create database |
No |
Block incremental deployment if data loss might occur |
Yes |
Back up database before deployment |
No |
For more information about these settings, see An Overview of Database Project Settings.
See Also
Tasks
How to: Create Database Projects
How to: Create Empty Database Projects
Concepts
An Overview of Database Creation and Deployment in a Team Environment
An Overview of Database Build and Deployment
Terminology Overview of Team Edition for Database Professionals