Microsoft SQL Server 2005 Express Edition The SQL Server documentation team cannot answer technical support

questions, but welcomes your suggestions and comments about this readme documentation. You can quickly and directly send e-mail feedback by using the link provided. Please se nd your feedback in English. To submit written feedback about this document, click here: Submit feedback. Contents 1.0 Introduction 2.0 Downloading and Installing SQL Server Express 2.1 .NET Framework 2.0 2.2 SQL Server Express 2.3 Tools to Manage SQL Server Express 2.4 Accessing Setup Documentation 2.5 SQL Server 2005 Readme 3.0 Setup Issues 4.0 Additional Information 4.1 Service Account and Network Protocol 4.2 User Instance Functionality 4.3 WMI Provider and User Instance Functionality 4.4 Books Online 4.5 Getting SQL Server Express Assistance 4.6 Newsgroup Support 4.7 Providing Feedback on SQL Server Express 5.0 Database Engine 6.0 Replication [Top] 1.0 Introduction Microsoft SQL Server 2005 Express Edition (SQL Server Express) is a free and eas y-to-use version of SQL Server 2005 that replaces the Microsoft Desktop Engine ( MSDE). Integrated with Microsoft Visual Studio 2005, SQL Server Express makes it easy to develop powerful, secure, data-driven applications and deploy them quic kly. SQL Server Express can be redistributed (subject to agreement), and can fun ction as the client database as well as a basic server database. SQL Server Expr ess is an ideal choice for independent software vendors (ISVs), server users, no n-professional developers, Web application developers, Web site hosters, and hob byists building client applications.

Any information relevant to SQL Server Express that was not available in time to be included in this Readme file will be published in Microsoft Knowledge Base a rticle 907284. For information about providing feedback using the SQL Server Express newsgroup, see 4.6 Newsgroup Support. [Top] 2.0 Downloading and Installing SQL Server Express This section covers information about installing .NET Framework 2.0, SQL Server Express, and tools that can be used to connect to SQL Server Express. 2.1 .NET Framework 2.0 You must install the .NET Framework 2.0 before installing SQL Server Express. SQL Server Express depends on a specific 2.0 version of the .NET Framework. If y ou have a different version, your SQL Server Express installation might function unpredictably. You can download the .NET Framework 2.0 from this Microsoft Web site. Note: The .NET Framework 2.0 is installed automatically by both Microsoft Visual Studi o 2005 and all editions of SQL Server 2005.

[Top] 2.2 SQL Server Express SQL Server Express is available for download at this Microsoft Web site. Note: Be sure to follow the instructions provided at the download site for downloading and extracting the product.

After you install SQL Server Express, use the following command to connect to SQ L Server Express by using the command prompt: sqlcmd -S Server\Instance Where Server is the name of the computer and Instance is the name of the instanc e you want to connect to. If you have used the default named instance during set up, specify the instance as "SQLExpress". [Top] 2.3 Tools to Manage SQL Server Express For information about connecting to and managing a SQL Server Express database, see Microsoft Knowledge Base article 907716. [Top] 2.4 Accessing Setup Documentation Hardware and software requirements are summarized in the Installation Requiremen ts for SQL Server Express document. [Top]

2.5 SQL Server 2005 Readme SQL Server 2005 readme file is available online at this Microsoft Web site. Note: Any information relevant to SQL Server 2005 and SQL Server Express that was not available in time to be included in the Readme file will be published in Microso ft Knowledge Base article 907284.

[Top] 3.0 Setup Issues This section details Setup issues in this release. 3.1 Existing SQL Native Client Installation May Cause Setup to Fail Setup might fail and roll back with the following error message: "An installatio n package for the product Microsoft SQL Native Client cannot be found. Try the i nstallation again using a valid copy of the installation package 'sqlncli.msi'." To work around this problem, uninstall SQL Native Client by using Add or Remove Programs. On a cluster, uninstall SQL Native Client from all nodes. Then, run S QL Server Setup again. [Top] 3.2 System Configuration Checker Fails with "Performance Monitor Counter Check F ailed" Message System Configuration Checker (SCC) verifies the value of the Performance Monitor Counter registry key before SQL Server installation begins. If SCC cannot verif y the existing registry key, or if SCC cannot run the Lodctr.exe system program, the SCC check fails, and Setup is blocked. To complete setup, you must manually increment the registry key. Caution: Incorrectly editing the registry can cause serious problems that might require y ou to reinstall your operating system. Microsoft cannot guarantee that problems resulting from editing the registry incorrectly can be resolved. Before editing the registry, back up any valuable data. For information about how to back up, r estore, and edit the registry, see Microsoft Knowledge Base article 256986. To manually increment the counter registry key: On the taskbar, click Start, click Run, type regedit.exe in the Run text box, an d then click OK. Navigate to the following registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\W indows NT\CurrentVersion\Perflib]. Look up the following keys: "Last Counter"=dword:00000ed4 (5276) "Last Help"=dword:00000ed5 (5277) Verify the values. The Last Counter value from the previous step (5276) must be equal to the maximum value of the Counter key from Perflib\009 in the following registry key, and the Last Help value from the previous step (5277) must be equa l to the maximum value of the Help key from Perflib\009 in the following registr y key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\

009]. Note: "009" is the key used for the English (United States) language.

If necessary, modify the value for the Last Counter and Last Help values in the \Perflib key. Right-click Last Counter or Last Help in the right pane, select Mo dify, click Base = Decimal, set the value in the Value data field, and then clic k OK. Repeat for the other key, if necessary, and then close the registry editor . Run SQL Server 2005 Express Edition Setup again. [Top] 3.3 SQL Server Express Books Online Has Incorrect Information on Operating Syste m Support The "Hardware and Software Requirements (SQL Server Express)" topic in SQL Serve r Express Books Online does not have an accurate list of operating systems. The following operating systems are supported by SQL Server Express. Windows Server 2003 SP1 Windows Server 2003 Enterprise Edition SP1 Windows Server 2003 Datacenter Edition SP1 Windows Small Business Server 2003 Standard Edition SP1 Windows Small Business Server 2003 Premium Edition SP1 Windows XP Professional SP2 Windows XP Home Edition SP2 Windows XP Tablet Edition SP2 Windows XP Media Edition SP2 Windows 2000 Professional Edition SP4 Windows 2000 Server Edition SP4 Windows 2000 Advanced Edition SP4 Windows 2000 Datacenter Server Edition SP4

[Top] 3.4 If Cryptographic Services Are Disabled on Windows Server 2003, Setup Fails w ith Windows Logo Requirement Dialog Windows Cryptographic Service Provider (CSP) is code that performs authenticatio n, encoding, and encryption services that Windows-based applications access thro ugh CryptoAPI on Windows Server 2003. If the CSP service is stopped or disabled, SQL Server Setup fails and displays a Windows Logo Requirement message. Note: Before running SQL Server Setup on a Windows Server 2003 failover cluster, the C SP service must be started on all cluster nodes. To enable the Windows CSP service on Windows Server 2003: In Control Panel, open Administrative Tools, and double-click Services. In the Name column, right-click Cryptographic Services, and then click Start. Close Services. Run Setup. [Top] 3.5 MSDTC Is Not Fully Enabled on Windows Because the Microsoft Distributed Transaction Coordinator (MS DTC) is not comple tely configured in Windows, applications might fail to enlist SQL Server Express resources in a distributed transaction. This problem can affect linked servers, distributed queries, and remote stored procedures that use distributed transact ions. To prevent such problems, you must fully enable MS DTC services on the ser ver where SQL Server Express is installed. To fully enable MS DTC: In Control Panel, open Administrative Tools, and then double-click Component Ser vices. In the left pane of Console Root, click Component Services, and then expand Comp uters. Right-click My Computer, and then click Properties. On the MSDTC tab, click Security Configuration. Under Security Settings, select all of the check boxes. Verify that the DTC Logon Account name is set to NT AUTHORITY\NetworkService. [Top] 3.6 Sample Databases Are Not Installed by Default The sample databases are not installed by default in SQL Server Express. The Nor thwind and pubs sample databases can be downloaded from this Microsoft Web site. The Adventureworks sample database can be installed from this Microsoft Web sit e. [Top]

3.7 "Force Encryption" Configuration Might Cause SQL Server Express Setup to Fai l Setup might fail if an existing SQL Server client installation is configured wit h the "force encryption" option enabled. To work around this issue, disable the option on any SQL Server clients. For Microsoft Data Access Components (MDAC) cl ients in SQL Server 2000, use the SQL Server 2000 Client Network Utility. For SQ L Native Client, uninstall SQL Native Client by using Add or Remove Programs. On a cluster, uninstall SQL Native Client from all nodes. Then run SQL Server 2005 Setup again. [Top] 3.8 Settings For sp_configure Might Cause Setup to Fail When Upgrading System Da tabases Setup from the command prompt might fail when you uninstall an earlier Community Technology Preview (CTP) release of SQL Server Express using SAVESYSDB and then install this release using USESYSDB, if the sp_configure options SMO and DMO XP s are disabled on the earlier instance. To resolve this issue, ensure that these options are enabled before using Setup to upgrade system databases. For more in formation, see "Setting Server Configuration Options" in SQL Server Books Online at this Microsoft Web site. [Top] 3.9 Installing a Default Instance of SQL Server 2000 May Disable SQL Server Expr ess If your computer has SQL Server 2000 Management Tools and a default instance of SQL Server Express is installed, SQL Server Setup will permit you to install a S QL Server 2000 default instance. However, doing so will disable the installed in stance of SQL Server Express. Therefore, do not install a default instance of SQ L Server 2000 when SQL Server 2000 Management Tools and a default instance of SQ L Server Express already exist on the computer. [Top] 3.10 Installing SQL Server Express on a Windows Domain Controller Security Note: We recommend against running SQL Server Express on a domain controller.

It is possible to install SQL Server Express on a Windows domain controller; how ever, it cannot run on a Windows Server 2003 domain controller as Local Service or Network Service. SQL Server service accounts should run as Windows domain use r accounts. It is also possible to install SQL Server service accounts to run as Local System, but this option is not recommended. Do not change the role of the server after you install SQL Server Express. For e xample, if you install SQL Server Express on a member server, do not use the Dcp romo tool to promote the server to a domain controller. Or, if you install SQL S erver Express on a domain controller, do not use Dcpromo to demote the server to a member server. Changing the role of a server after you install SQL Server Exp ress can result in loss of functionality and is not supported. [Top] 3.11 Existing SQL Native Client Installation May Cause Setup to Fail Setup might fail and roll back with the following error message: "An installatio n package for the product Microsoft SQL Native Client cannot be found. Try the i nstallation again using a valid copy of the installation package 'sqlncli.msi'."

To work around this problem, uninstall SQL Native Client by using Add or Remove Programs. On a cluster, uninstall SQL Native Client from all nodes. Then, run S QL Server Setup again. [Top] 3.12 Uninstalling Pre-release Versions SQL Server Express and Visual Studio 2005 You must remove all previous builds of SQL Server Express, Visual Studio 2005, a nd the .NET Framework 2.0 before installation. Because both products depend on t he same version of the .NET Framework, they must be uninstalled in the following order: SQL Server Express Visual Studio 2005 .NET Framework 2.0 [Top] 3.13 Maintenance Mode Prompts for Path to Setup.exe If you install a new SQL Server 2005 component in maintenance mode, you will be prompted for the location of Setup.exe on the SQL Server 2005 installation media . When specifying the location, make sure that the path includes "Setup.exe." Fo r example, the path "D:\" will fail, but "D:\Setup.exe" will succeed. [Top] 3.14 Troubleshooting Failure of Setup Command Shell Scripts Setup command shell scripts can generate Windows script errors when path variabl es contain parentheses. This occurs because command shell scripts do not support parentheses in path variables, which can occur when installing 32-bit component s to the Windows on Windows (WOW64) 32-bit subsystem on a 64-bit computer. For e xample, the following script, with a path value of "C:\Program Files (x86)\", ge nerates an error because the shell script interpreter misinterprets the parenthe ses in the expanded PATH variable as part of the IF/ELSE statement: IF "%SOME_PATH%" == "" ( SET PATH=%PATH%;%PATH_A% ) ELSE ( SET PATH=%PATH%;%PATH_B% ) To work around this issue, change the script to remove the parentheses. For exam ple: IF "%SOME_PATH%" == "" set PATH=%PATH%;%PATH_A% IF NOT "%SOME_PATH%" == "" set PATH=%PATH%;%PATH_B% Or remove the SQL entry containing parentheses from the path. [Top]

4.0 Additional Information 4.1 Service Account and Network Protocols For SQL Server Express, the Local System Account is Network Service Account. SQL Server Express listens on local named pipes and shared memory. With a defaul t installation, you cannot remotely connect to SQL Server Express. You will need to enable TCP/IP and check if the firewall is enabled. To enable TCP/IP: From the Start menu, choose All Programs, point to Microsoft SQL Server 2005, po int to Configuration Tools, and then click SQL Server Configuration Manager. Optionally, you can open Computer Manager by right-clicking My Computer and choo sing Manage. In Computer Management, expand Services and Applications, expand SQ L Server Configuration Manager. Expand SQL Server 2005 Network Configuration, and then click Protocols for Insta nceName. In the list of protocols, right-click the protocol you want to enable, and then click Enable. The icon for the protocol will change to show that the protocol is enabled. To enable the firewall: Click Start, click Control Panel, and then click Network Connections. From the navigation bar on the left, click Change Windows Firewall settings. On the Exceptions tab, in the Programs and Services box, you will probably see t hat SQL Server is listed, but not selected as an exception. If you select the ch eck box, Windows will open the 1433 port to let in TCP requests. Alternatively, if you do not see SQL Server listed, do the following: Click Add Program. Click Browse. Navigate to drive:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\BINN Add the file sqlservr.exe to the list of exceptions. [Top] 4.2 User Instance Functionality SQL Server Express allows non-administrator users to copy or move databases (usi ng Xcopy deployment) without requiring DBCreator privileges. For more informatio n, see User Instances for Non-Administrators in SQL Server Express Books Online at this Microsoft Web site.

[Top] 4.3 WMI provider and User Instance functionality WMI Provider for Server Events will not be supported on the dynamically spawned user instances. This should still work on the parent SQL Server Express instance . [Top] 4.4 Books Online SQL Server Express Books Online is available for download from this Microsoft We b site. Note: Because SQL Server Express is a limited version of SQL Server 2005, the document ation in SQL Server Express Books Online is heavily dependent on the content pre sent in SQL Server 2005 Books Online.

SQL Server 2005 Books Online is available for download from this Microsoft Web s ite. Microsoft periodically publishes downloadable updates to SQL Server Express Book s Online and SQL Server 2005 Books Online. We recommend installing these updates to keep the information current in your local copy of the documentation. [Top] 4.5 Getting SQL Server Express Assistance There are four principal sources of information from Microsoft about SQL Server Express: SQL Server Express documentation and samples SQL Server 2005 documentation SQL Server sites on Microsoft Developer Network (MSDN) and TechNet SQL Server information on additional Microsoft Web sites You can also get help from others either through the SQL Server community or dir ectly from Microsoft support. For more information, see "Getting SQL Server Expr ess Assistance" in SQL Server Express Books Online. [Top] 4.6 For Web SQL Newsgroup Support newsgroup support, visit the SQL Server Express newsgroup at this Microsoft site. Do not use other Microsoft newsgroups for posting questions regarding Server Express.

The latest information from the SQL Server Express team can be found at the SQL Server Express Weblog.

Note: Newsgroups are supported in English only.

[Top] 4.7 Providing Feedback on SQL Server Express To provide suggestions and bug reports on SQL Server Express: Send suggestions and bug reports about the features and user interface of SQL Se rver Express at this Microsoft Web site. Send suggestions and report inaccuracies about the documentation using the feedb ack functionality in SQL Server Express Books Online. Choose to send error reports and feature usage data automatically to Microsoft f or analysis. For more information, see "Providing Feedback on SQL Server 2005" in SQL Server Books Online. [Top] 5.0 Database Engine The notes in this section are late-breaking items for the SQL Server 2005 Databa se Engine and Database Engine-specific command prompt utilities that also apply to SQL Server Express. [Top] 5.1 Connections May Be Forcibly Closed When Running on Windows Server 2003 SP1 If TCP/IP networking is turned on, client connections to an instance of the SQL Server Express Database Engine running on Windows Server 2003 Service Pack 1 mig ht fail with the following error: "ProviderNum: 7, Error: 10054, ErrorMessage: " TCP Provider: An existing connection was forcibly closed by the remote host"." This might occur when you are testing scalability with a large number of client connection attempts. To resolve this issue, use the regedit.exe utility to add a new DWORD value named SynAttackProtect to the registry key HKEY_LOCAL_MACHINE\S YSTEM\CurrentControlSet\Services\Tcpip\Parameters\ with value data of 00000000. Security Note: Setting this registry key might expose the server to a SYN flood denial-of-servi ce attack. Remove this registry value when testing is complete. Caution: Incorrectly editing the registry can cause serious problems that might require y ou to reinstall your operating system. Microsoft cannot guarantee that problems resulting from editing the registry incorrectly can be resolved. Before editing the registry, back up any valuable data. For information about how to back up, r estore, and edit the registry, Microsoft Knowledge Base article 256986.

[Top]

5.2 Secure Service Broker Dialogs Require a Database Master Key SQL Server 2005 Books Online incorrectly states that when a conversation using d ialog security spans databases, SQL Server creates a session key encrypted with the master key for the database. Actually, the session key is encrypted with the master key for the database for all conversations that use dialog security. If a database master key is not available, messages for the conversation remain in the transmission_queue with an error until a database master key is created or t he conversation times out. Either use the ENCRYPTION = OFF parameter to create a n unencrypted dialog, or use the following command to create a database master k ey: CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<password>' [Top] 5.3 Common Language Runtime User-Defined Types Should Have Only One Serializatio n Each instance of a byte-ordered user-defined type (UDT) object can have only one serialized representation. If the serialize or de-serialize routines recognize more than one representation of a particular object, you may see errors in the f ollowing cases: During validation of a byte-ordered UDT passed through RPC, UDT validation perfo rms de-serialization/re-serialization of the UDT and requires that the resulting bytes be exactly the same as the original. If the validation fails, you will se e the error: "System.Data.SqlClient.SqlException, Incoming TDS RPC protocol stre am is incorrect. Parameter 1 ("<ParameterName>"): The supplied value is not a va lid instance of data type <TypeName>. Check the source data for invalid values."

During DBCC, the bytes stored in a byte-ordered UDT column must be equal to the computed serialization of the UDT value. If this is not true, the DBCC CHECKTABL E routine will report a consistency error. [Top] 5.4 Network Connectivity Not Enabled by Setup To enhance security, SQL Server Express disables network connectivity for some n ew installations. Network connectivity using TCP/IP is not disabled if you are u sing SQL Server Enterprise, Standard, or Workgroup Edition, or if a previous ins tallation of SQL Server is present. Named Pipes connectivity is available only f or local connections unless a previous installation of SQL Server is present. Fo r all installations, the shared memory protocol is enabled to allow local connec tions to the server. The SQL Browser service might be stopped, depending on inst allation conditions and installation options. [Top] 5.5 Considerations for Assemblies That Contain User-Defined Types The following limitations apply to common language runtime (CLR) assemblies that contain user-defined types. Common Language Runtime User-Defined Types Should Have Only One Serialization Each instance of a byte-ordered user-defined type object can have only one seria lized representation. If the serialize or de-serialize routines recognize more t

han one representation of a particular object, you may see errors in the followi ng cases: During validation of a byte-ordered user-defined type passed through RPC, user-d efined type validation performs de-serialization/re-serialization of the user-de fined type and requires that the resulting bytes be exactly the same as the orig inal. If the validation fails, you will see the error: "System.Data.SqlClient.Sq lException, Incoming TDS RPC protocol stream is incorrect. Parameter 1 ("<Parame terName>"): The supplied value is not a valid instance of data type <TypeName>. Check the source data for invalid values." During DBCC CHECKTABLE, the bytes stored in a byte-ordered user-defined type col umn must be equal to the computed serialization of the UDT value. If this is not true, the DBCC CHECKTABLE routine will report a consistency error. Updated Restrictions on Updating Assemblies That Hold User-Defined Type Classes ALTER ASSEMBLY can be used to update CLR user-defined types in the following way s: To modify public methods of the user-defined type class, as long as signatures o r attributes are not changed. To add new public methods. To modify private methods in any way. Fields that are contained within a native-serialized user-defined type, includin g data members or base classes, cannot be changed by using ALTER ASSEMBLY. All o ther changes are unsupported. [Top] 5.6 SQL Server does not Guarantee Data Consistency when Updating Assemblies If WITH UNCHECKED DATA is not specified, SQL Server attempts to prevent ALTER AS SEMBLY from executing if the new assembly version affects existing data in table s, indexes, or other persistent sites. SQL Server does not guarantee, however, t hat computed columns, indexes, indexed views or expressions will be consistent w ith the underlying routines and types when the common language runtime (CLR) ass embly is updated. Use caution when executing ALTER ASSEMBLY to ensure that there is not a mismatch between the result of an expression and a value based on that expression stored in the assembly. [Top] 5.7 Considerations for the Autorecovered Shadow Copy Feature of the Volume Shado w Copy Service The autorecovered shadow copy feature of the Volume Shadow Copy Service (VSS) ha s the following limitations. Multiple Persisted Autorecovered Shadow Copies On Windows Server 2003 Service Pack 1 (SP1) and later, you can create only a sin gle persisted autorecovered shadow copy. To create an additional shadow copy, yo u must first apply the update described in Knowledge Base article 891957. Note:

If you have not applied this update, you can create a new persisted autorecovere d shadow copy by deleting the existing one first, and then creating the new one.

Autorecovered Shadow Copies and Full-Text Catalogs The autorecovered shadow copy feature does not support full-text catalogs. When an autorecovered shadow copy is created, any full-text catalogs in the database on the shadow copy are taken offline. When the database is attached from the sha dow copy, the full-text catalog remains offline permanently. All other data rema ins available in the attached database. When a database that contains a full-text catalog is attached directly from an a utorecovered shadow copy, the attach operation returns the following error messa ge: Server: Msg 7608, Level 17, State 1, Line 1 An unknown full-text failure (0xc000000d) occurred during "Mounting a full-text catalog". If you do not need to attach a database directly from the shadow copy, you can a void this issue by copying the database files and full-text catalogs from the sh adow copy to a regular drive-letter based volume, and then attaching the databas e from that location. As long as the attach command specifies the correct locati on of the copied full-text files, the full-text catalogs will work. [Top] 5.8 Restrictions for Registering Common Language Runtime Assemblies SQL Server does not allow registering different versions of an assembly with the same name, culture, and public key. If you plan to retain databases from a vers ion of SQL Server Express earlier than the September CTP release, you must drop all but one instance of an assembly that has multiple registrations before you i nstall this release. [Top] 5.9 Creating EXTERNAL_ACCESS and UNSAFE Assemblies To create an EXTERNAL_ACCESS or UNSAFE assembly in SQL Server, or to load an ass embly, one of the following two conditions must be met: The assembly is strong name signed or authenticode signed with a certificate. Th is strong name (or certificate) is created inside SQL Server as an asymmetric ke y (or certificate) and has a corresponding logon with EXTERNAL ACCESS ASSEMBLY p ermission (for external access assemblies) or UNSAFE ASSEMBLY permission (for un safe assemblies). The database owner (DBO) has EXTERNAL ACCESS ASSEMBLY (for EXTERNAL ACCESS assem blies) or UNSAFE ASSEMBLY (for UNSAFE assemblies) permission, and the database h as the TRUSTWORTHY database property set to ON. We recommend that the TRUSTWORTHY property on a database not be set to ON only t o run common language runtime (CLR) code in the server process. Instead, we reco mmend that an asymmetric key be created from the assembly file in the master dat abase. A logon mapped to this asymmetric key must then be created, and the logon must be granted EXTERNAL ACCESS ASSEMBLY or UNSAFE ASSEMBLY permissions.

The following Transact-SQL statements perform the steps that are required to cre ate an asymmetric key, map a logon to this key, and then grant EXTERNAL_ACCESS A SSEMBLY permission to the logon. You must execute the following Transact-SQL sta tements before executing the CREATE ASSEMBLY statement. USE master GO CREATE ASYMMETRIC KEY HelloWorldKey FROM EXECUTABLE FILE = 'C:\HelloWorld.dll' CREATE LOGIN HelloWorldLogin FROM ASYMMETRIC KEY HelloWorldKey GRANT EXTERNAL ACCESS ASSEMBLY TO HelloWorldLogin GO [Top] 5.10 Application Role Compatibility with Metadata Visibility Restrictions and Dy namic Management Views The behavior of programs that run under an application role might change because , by default, SQL Server Express limits the visibility of master database metada ta to application roles. As a temporary workaround, you can enable trace flag #4 616. For more information, see Knowledge Base article 906549. [Top] 5.11 SUPPLEMENTAL_LOGGING Database Option Is Not Implemented The SUPPLEMENTAL_LOGGING database option is not implemented in this release of S QL Server. This option can be set but has no effect. [Top] 5.12 sys.dm_clr_loaded_assemblies Shows Assemblies That Failed to Load Assemblies that fail to load into the server address space for any reason will s till appear in the sys.dm_clr_loaded_assemblies dynamic management view. [Top] 5.13 XQuery Changes The following aspects of the SQL Server Express XQuery implementation are not do cumented in Books Online: Characters that are generated by CDATA sections are not considered to be white-s pace characters. For example, select cast(''as xml).query('<a> <![CDATA[ ]]> {"a bc"}</a>') returns <a> abc</a>. Construction of empty elements and attributes is supported. The namespace prefix xmlns identifies a namespace declaration attribute and cann ot be redeclared in an XQuery expression. This behavior is required by the XQuer y specification. Using 'for' with source expression () yields a static error. In an XML document that is constructed by using the query() method on the xml da

ta type, a carriage return within a CDATA section becomes a line feed. The line feed is used instead of the earlier carriage-return entity reference (&#x0d;) fo r uniformity with text XML parsing. Transact-SQL user-defined functions that contain local-name() and namespace-uri( ) are deterministic. [Top] 5.14 Conversion From xsd:dateTime is Less Restrictive Than Documented A string representation of an xs:dateTime value that does not contain a date and time separator T or a time zone can be converted to an SQL datetime type in a v alue() method, as in the following example: declare @aaa xml set @aaa = '<AAA MyDate="2005/1/1 00:00:00"/>' select @aaa.value('(//AAA)[1]/@MyDate', 'datetime') [Top] 5.15 XML Schema Support The following aspects of the SQL Server 2005 support for XML Schema are not docu mented in SQL Server 2005 Books Online: The XML schema for Reporting Services (RDL) can be loaded into an XML schema col lection. Values of type xs:dateTime and xs:time that contain second values that have more than three fractional digits do not return an error. Instead they are rounded o ff. An XML schema is rejected if maxInclusive is redefined in a derived type when ba se type has fixed="true". Trailing spaces in minInclusive, minExclusive, maxInclusive, and maxExclusive fa cets are ignored in derived types that restrict the xs:dateTime, xs:data, and xs :time data types. [Top] 5.16 RC4 Encryption Should Not Be Used Do not use RC4 encryption to protect your data in SQL Server 2005. Use a block c ipher such as AES 256 or Triple DES instead. [Top] 6.0 Replication The notes in this section are late-breaking items for replication. [Top] Replication is Disabled by Default

Microsoft SQL Server 2005 Express Edition can serve as a Subscriber for all type s of replication, but replication is not installed by default for this edition. To install replication components: On the Feature Selection page, expand Database Services. Click Replication, and then click Entire feature will be installed on local hard drive. To install connectivity components and Replication Management Objects (RMO): On the Feature Selection page, click Client Components, and then click Entire fe ature will be installed on local hard drive. [Top] 2005 Microsoft Corporation. All rights reserved.