Edit Values Dialog Box

Important

To create and manage databases using the latest version of Data Tier Applications (DACPAC), install the most recent release of SQL Server Data Tools from Get Started with Microsoft SQL Server Data Tools.

Use this dialog box to configure the values for a selected Server Selection facet property or a hyperlinked value in the Edit the condition (click links to edit values) box.

To access this dialog box, follow these steps:

  1. In Solution Explorer, expand the Properties folder for the data-tier application project.

  2. Right-click ServerSelection.sqlpolicy, and then click Open.

  3. On the ServerSelection.sqlpolicy property page, do either of the following:

    • In the Facet properties list, select a check box next to a facet property.

    • If you have already added facet properties and their values to the condition, in the Edit the condition (click links to edit values) box, click a hyperlinked value.

Options

  • Facet property
    Is the facet property for which you want to modify the values.

  • Comparison operator
    Use this list to select the desired comparison operator, such as "is equal to" or "is not equal to." The available comparison operators vary, depending on the selected facet property.

  • Value
    Use to set the string, numeric or Boolean value for the facet property. If the facet property requires a string value, make sure that string constants are enclosed in single quotation marks.

    The facet properties are listed in the following table, together with their descriptions and sample values. If a value that you need is not listed, you can do either of the following:

    • Use the xp_msver extended stored procedure, or the SELECT SERVERPROPERTY command on an instance of SQL Server that matches the policy requirement that you want to set. The method that you can use is included in the Description column of the table.

    • View the facet property values on an instance of SQL Server that matches the policy requirement that you want to set. To do this, follow these steps:

      1. From a SQL Server 2008 R2 version of SQL Server Management Studio, start Object Explorer, right-click an instance, and then click Facets.

      2. In the Facet list, click Server Selection.

      3. Locate the facet property that matches the Server Selection facet property that you want to configure, and then view its value.

    Facet Property

    Description

    Build Number

    The build number part of the SQL Server version information on the target instance. This value depends on the service pack or cumulative update that is installed. For example, the RTM version of SQL Server 2008 has build number 1600. SQL Server 2008 with Service Pack 1 has build number 2531.

    If you can connect to a target instance, the following Transact-SQL command will return the version, which includes the build number:

    EXEC master.dbo.xp_msver

    The version is returned in the ProductVersion row, in the format 'major.minor.build_number'.

    Collation

    The default collation of the target instance of SQL Server. For example, 'SQL_Latin1_General_CP1_CI_AS'.

    If you can connect to a target instance, the following Transact-SQL query will return the collation:

    SELECT SERVERPROPERTY('Collation')

    For a list of collations in SQL Server 2008, see SQL Server Collation Name (Transact-SQL) in SQL Server Books Online.

    Edition

    The edition of SQL Server that must be running on the target instance. For example, 'Enterprise Edition', or 'Developer Edition (64-bit)'.

    If you can connect to a target instance, the following Transact-SQL query will return the edition:

    SELECT SERVERPROPERTY('Edition')

    IsCaseSensitive

    True or False, depending on whether the target instance of SQL Server is case-sensitive.

    Language

    The default language that is used by the target instance of SQL Server. For example, 'English (United States)'.

    If you can connect to a target instance, the following Transact-SQL query will return the language value:

    EXEC master.dbo.xp_msver

    For a list of supported languages in SQL Server 2008, see sys.syslanguages (Transact-SQL) in SQL Server Books Online.

    NamedPipesEnabled

    True or False, depending on whether the target instance of SQL Server has the Named Pipes protocol enabled.

    OSVersion

    The operating system version of the target SQL Server. For example:

    • The RTM versions of Windows Server 2008 R2 and Windows 7 have an operating system version of '6.1 (7600)'.

    • Windows Server 2008 with Service Pack 2 (SP2) and Windows Vista with SP2 have an operating system version of '6.0 (6002)'.

    If you can connect to a target instance, the following Transact-SQL query will return the operating system value (in the WindowsVersion row):

    EXEC master.dbo.xp_msver

    Platform

    The hardware platform of the target SQL Server. For example, 'NT INTEL X86', or 'NT X64'.

    If you can connect to a target instance, the following Transact-SQL query will return the platform value:

    EXEC master.dbo.xp_msver

    TcpEnabled

    True or False, depending on whether the target instance of SQL Server has the TCP/IP protocol enabled.

    VersionMajor

    The major SQL Server version number for the target instance of SQL Server. For example, a value of 10 corresponds to SQL Server 2008.

    If you can connect to a target instance, the following Transact-SQL command will return the version:

    EXEC master.dbo.xp_msver

    The version number is returned in the ProductVersion row, in the format 'major.minor.build_number'.

    VersionMinor

    The minor SQL Server version number for the target instance of SQL Server. For example, for the major version 10, a minor version of 50 corresponds to SQL Server 2008 R2.

    If you can connect to a target instance, the following Transact-SQL command will return the version:

    EXEC master.dbo.xp_msver

    The version number is returned in the ProductVersion row, in the format 'major.minor.build_number'.

See Also

Reference

ServerSelection.sqlpolicy Property Page

Concepts

Configuring the Server Selection Policy