The most up-to-date version of this file is available online at the
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 send your feedback in English.
To submit written feedback about this document, click here:
This file describes how to use Microsoft® SQL Server™ 2005 Express Edition (SQL Server Express) Service Pack 1 (SP1) to install new instances of SQL Server Express SP1 or to upgrade instances of SQL Server Express to SP1. SQL Server Express SP1 can also be used to upgrade instances of Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) to SQL Server Express SP1.
This service pack can be used to upgrade only the initial release version of SQL Server Express (or MSDE 2000) to SQL Server Express SP1. You must use Microsoft SQL Server 2005 Service Pack 1 (SP1) to upgrade all other editions of SQL Server 2005 to SP1. SQL Server 2005 SP1 can be obtained from the |
1.1 Overview of SQL Server Express SP1 Installation
During installation, SQL Server Express SP1 Setup will enumerate and let you select from an instance of SQL Server Express to upgrade to SP1. SQL Server Express SP1 can be reapplied to SQL Server Express instances that have already been upgraded to SP1. The general process for installing SP1 is as follows:
Download and extract the service pack installation files. Section 2.0 describes how to obtain the SP1 installation files.
Note: SQL Server Express SP1 requires the .NET Framework 2.0.
Prepare for upgrade to SP1. Section 3.1 describes the preparatory steps to take before you install SQL Server Express SP1.
Install SQL Server Express SP1. Section 3.2 details options for running SP1 Setup.
1.2 Installation Requirements
Before you install SQL Server Express SP1, review the SQL Server Express installation requirements at the
SQL Server Express requires the .NET Framework 2.0. If you do not have the .NET Framework 2.0 installed, you must download and install it before installing SQL Server Express SP1. You can download the .NET Framework 2.0 from the
|The .NET Framework 2.0 is installed automatically by both Microsoft Visual Studio 2005 and all other editions of SQL Server 2005.|
If you are upgrading an instance of MSDE 2000 to SQL Server Express SP1, you must ensure that the .NET Framework 2.0 is installed.
1.3 Uninstalling SQL Server Express SP1
A new instance of SQL Server Express SP1 can be uninstalled from Add or Remove Programs. However, when you use SQL Server Express SP1 to upgrade a SQL Server Express instance to SP1, the upgrade cannot be uninstalled.
In Add or Remove Programs, select Microsoft SQL Server 2005 from Currently installed programs, and then click Remove.
In the Components Selection dialog box, select the instance of SQL Server Express to remove.
Click Next, and then click Finish to complete the uninstallation wizard.
Reinstall an instance of the previous version of SQL Server Express.
Apply any hotfixes that were previously installed on the instance.
Note: Additional steps are required to ensure that you are able to revert to the previous version of SQL Server Express. For more information, see 3.1.1 Back Up Your SQL Server Express Databases.
1.4 Additional Information about SQL Server Express SP1
A list of the fixes that are contained in this service pack is provided in Microsoft Knowledge Base article
The Knowledge Base articles mentioned in this Readme are available in the
Under Advanced Search, in the For text box, type the number of the article you want.
Under Search Type, select Article ID.
Click the right arrow button.
All publicly issued SQL Server 2005 security bulletins that were released before March 2, 2006 have been addressed in SP1. If you received a SQL Server 2005 or SQL Server Express hotfix after March 2, 2006, that hotfix might not be included in this release of SP1. Contact your primary support provider about obtaining the same hotfix for SQL Server Express SP1.
1.5 Updates to SQL Server 2005 Books Online are Available
Starting with the April 2006 update of SQL Server 2005 Books Online, a separate Books Online for SQL Server Express is unavailable. SQL Server 2005 Books Online is the primary documentation for SQL Server Express. The April 2006 update of Books Online reflects all product upgrades that are included in this service pack, and also includes other improvements to the documentation. We strongly recommend that you install this update to keep the information in your local copy of the documentation current with SQL Server Express SP1. The April 2006 update is available at this
Updated SQL Server 2005 Samples Are Available
New and updated samples for SQL Server 2005 are available. You can download these updated samples from this
SQL Server 2005 Samples and Sample Databases
The sample databases are not installed with SQL Server Express. The AdventureWorks sample database can be installed from the
|Although the Northwind and pubs sample databases will work with SQL Server Express, the AdventureWorks sample database is recommended for use with SQL Server Express.|
2.0 Obtaining SQL Server Express SP1
SQL Server Express SP1 is available for download at the
3.0 Installing SQL Server Express SP1
This section details how to install SQL Server Express SP1, as well as any late-breaking information or setup issues that can impact successful installation of the service pack. The steps to install SQL Server Express SP1 are as follows:
Prepare for a SQL Server Express SP1 installation
Install SQL Server Express SP1
Restart services and applications
3.1 Prepare for a SQL Server Express SP1 Installation
This section only applies when upgrading an instance of SQL Server Express or MSDE 2000 to SP1. When you install a new instance of SQL Server Express SP1, you must also install the .NET Framework 2.0. This is the only preparation required. For more information, see 1.2 Installation Requirements. When you upgrade an instance of MSDE 2000, you must follow the steps in this section and install the .NET Framework 2.0.
We recommend that you run Microsoft SQL Server 2005 Upgrade Advisor against instances of MSDE 2000 before you upgrade them to SQL Server Express SP1. Upgrade Advisor identifies features and configuration changes that might affect your upgrade, and it provides links to documentation that describes each identified issue and how to resolve it. You can download Upgrade Advisor from the |
You must do the following before you upgrade an instance of SQL Server Express to SP1:
Back up your SQL Server Express databases
Verify that the system databases have enough free space
Verify that SQL Server Express service accounts are not disabled
Stop services and applications
3.1.1 Back Up Your SQL Server Express Databases
Before installing SQL Server Express SP1, back up the master, msdb, and model databases. Installing SQL Server Express SP1 modifies the master, msdb, and model databases, making them incompatible with pre-SP1 versions of SQL Server Express and MSDE. Backups of these databases are required if you decide to reinstall SQL Server Express or MSDE without SP1.
It is also prudent to back up your user databases.
|When you apply SQL Server Express SP1 to instances that participate in a replication topology, you must back up your replicated databases along with your system databases before you apply SQL Server Express SP1.|
3.1.2 Verify That the System Databases Have Enough Free Space
If the autogrow option is not selected for the master and msdb system databases, these databases must have at least 500 KB of free space each. To verify that the databases have sufficient space, run the sp_spaceused system stored procedure on the master and msdb databases. If the unallocated space in either database is less than 500 KB, increase the size of the database. For more information, see "Expanding a Database" in SQL Server 2005 Books Online.
3.1.3 Verify That SQL Server Express Service Accounts Are Not Disabled
Setup might fail if the service startup type for the SQLExpress service is set to Disabled.
In Control Panel, select Administrative Tools, and then select Services.
Locate the SQLExpress service in the list and note the value for Startup Type.
If the value for Startup Type is Disabled, double-click the service name and change Startup Type to either Manual or Automatic.
3.1.4 Stop Services and Applications
You should stop all applications and services that make connections to all instances of SQL Server Express being upgraded, including Control Panel and Add or Remove Programs, before installing SP1.
If you begin to apply SP1 without first shutting down applications and services, Setup will try to stop the SQL Server Express service. If Setup determines that other applications and services must be stopped, a warning displays the applications and services that must be stopped. After you stop these applications and services, click Try Again to resume Setup. If you cannot stop an application or service, click Continue. Setup will continue, but you might need to restart your computer after Setup finishes. If you click Cancel, the current component is not upgraded to SP1, but Setup continues.
|Setup cannot always determine which applications and services must be stopped. Stop all applications and services that make connections to SQL Server Express, including Control Panel, before installing SP1.|
3.2 Install SQL Server Express SP1
To install SQL Server Express SP1, simply run the self-extracting download package. Complete installation instructions for running Setup in both attended and unattended mode are detailed in the "Installing SQL Server Express" section in SQL Server 2005 Books Online. You should review the Setup documentation before you install SQL Server Express SP1. You can access the Setup documentation during Setup by pressing the F1 key or by clicking the Help button in a dialog box that contains online Help. This documentation is also available online at the
|SQL Server Express SP1 Setup must be run under an account with administrator privileges on the computer where SQL Server Express SP1 will be installed.|
3.3 Restart Services and Applications
This section only applies when upgrading an existing instance of SQL Server Express to SP1.
When Setup completes, it may prompt you to restart the computer. 3.1.4 Stop Services and Applications provides guidelines on when a restart is required. After the system restarts, or after Setup completes without requesting a restart, use the Services application in Control Panel to make sure that any services you stopped before applying the service pack are now running. This includes services like Microsoft Distributed Transaction Coordinator (MS DTC) and the Microsoft Search services, or instance-specific equivalents. Restart the applications that you closed before running the service pack Setup program. You should also back up the upgraded master, msdb, and model databases at this time.
3.4 Setup Issues
This section details setup issues for SP1.
|Unless otherwise noted, these issues apply only when installing a new instance of SQL Server Express.|
3.4.1 Existing SQL Native Client Installation May Cause Setup to Fail
Setup might fail and roll back with the following error message: "An installation package for the product Microsoft SQL Native Client cannot be found. Try the installation 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.
3.4.2 System Configuration Checker Fails with "Performance Monitor Counter Check Failed" Message
System Configuration Checker (SCC) verifies the value of the Performance Monitor Counter registry key before SQL Server installation begins. If SCC cannot verify 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.
Incorrectly editing the registry can severely damage your system. Before making changes to the registry, we recommend that you back up any valued data on the computer. For information about how to back up, restore, and edit the registry, see Microsoft Knowledge Base article |
On the taskbar, click Start, click Run, type regedit.exe in the Run text box, and then click OK.
Navigate to the following registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib]. Look up the following keys:
"Last Counter"=dword:00000ed4 (5276)
"Last Help"=dword:00000ed5 (5277)
- "Last Counter"=dword:00000ed4 (5276)
Verify the values of the Counter and Help keys in the following registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009].
The maximum value of Counter must be equal to the Last Counter value from the previous step, and the maximum value of Help must be equal to the Last Help value from the previous step.
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 Modify, click Base = Decimal, set the value in the Value data field, and then click OK. Repeat for the other key, if necessary, and then close the registry editor.
Run SQL Server Express Setup again.
3.4.3 If Cryptographic Services Are Disabled on Windows Server 2003, Setup Fails with Windows Logo Requirement Message
Windows Cryptographic Service Provider (CSP) is code that performs authentication, encoding, and encryption services that Windows-based applications access through CryptoAPI on Windows Server 2003. If the CSP service is stopped or disabled, SQL Server Setup fails and displays a Windows logo requirement message.
|Before you run SQL Server Setup on a Windows Server 2003 failover cluster, the CSP service must be started on all cluster nodes.|
In Control Panel, open Administrative Tools, and then double-click Services.
In the Name column, right-click Cryptographic Services, and then click Start.
3.4.4 MS DTC Is Not Fully Enabled on Windows
Because the Microsoft Distributed Transaction Coordinator (MS DTC) is not completely 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 transactions. To prevent such problems, you must fully enable MS DTC services on the server where SQL Server Express is installed.
In Control Panel, open Administrative Tools, and then double-click Component Services.
In the left pane of Console Root, click Component Services, and then expand Computers.
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.
3.4.5 "Force Encryption" Configuration Might Cause SQL Server Express Setup to Fail
Setup might fail if an existing SQL Server client installation is configured with the "force encryption" option enabled. To work around this issue, disable the option on any SQL Server clients. For Microsoft Data Access Components (MDAC) clients in SQL Server 2000, use the SQL Server 2000 Client Network Utility. For SQL Native Client, uninstall SQL Native Client by using Add or Remove Programs.
3.4.6 Installing a Default Instance of SQL Server 2000 May Disable SQL Server Express
If your computer has SQL Server 2000 Management Tools and a default instance of SQL Server Express is installed, SQL Server Setup permits you to install a SQL Server 2000 default instance. However, doing so disables the installed instance of SQL Server Express. Therefore, do not install a default instance of SQL Server 2000 when SQL Server 2000 Management Tools and a default instance of SQL Server Express already exist on the computer.
3.4.7 Installing SQL Server Express on a Windows Domain Controller
|We do not recommend running SQL Server Express on a domain controller.|
It is possible to install SQL Server Express on a Windows domain controller; however, 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 user 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 example, if you install SQL Server Express on a member server, do not use the Dcpromo tool to promote the server to a domain controller. Or, if you install SQL Server 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 Express can result in loss of functionality and is not supported.
3.4.8 Maintenance Mode Prompts for Path to Setup.exe
If you install a new SQL Server Express component in maintenance mode, you are prompted for the location of Setup.exe on the SQL Server Express installation media. When you specify the location, make sure that the path includes "Setup.exe." For example, the path "D:\" fails, but "D:\Setup.exe" succeeds.
3.4.9 Troubleshooting Failure of Setup Command Shell Scripts
Setup command shell scripts can generate Windows script errors when path variables contain parentheses. This occurs because command shell scripts do not support parentheses in path variables, which can occur when installing 32-bit components to the Windows on Windows (WOW64) 32-bit subsystem on a 64-bit computer. For example, the following script, with a path value of "C:\Program Files (x86)\", generates an error because the shell script interpreter misinterprets the parentheses 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 example:
IF "%SOME_PATH%" == "" set PATH=%PATH%;%PATH_A% IF NOT "%SOME_PATH%" == "" set PATH=%PATH%;%PATH_B%
Or remove the SQL entry that contains parentheses from the path.
3.4.10 Database Compatibility Level Setting When Upgrading from MSDE 2000
This issue only applies when upgrading an instance of MSDE 2000 to SQL Server Express SP1.
When an instance of MSDE 2000 is upgraded to SQL Server Express SP1, the database compatibility level remains at 80 to enable backward compatibility with existing MSDE 2000 applications. This backward compatibility level disables certain new functionalities of SQL Server Express . For more information, see the "sp_dbcmptlevel" reference topic in SQL Server 2005 Books Online.
3.4.11 Setup Might Fail If There Is a Single Quotation Mark in the System Database Directory
This issue only applies when upgrading an instance of SQL Server Express to SP1.
When you upgrade an instance of SQL Server Express to SP1, Setup might fail if the system databases are installed in a directory that has a single quotation mark in the directory name. If failure occurs, you must move the system databases to a directory without a single quotation mark in the directory name. For more information about moving system databases, see "Moving System Databases" in SQL Server 2005 Books Online.
3.4.12 Restrictions on ALTER DATABASE Might Cause Upgrade to Fail
This issue only applies when upgrading an instance of SQL Server Express to SP1.
When you apply SP1, Setup upgrades system databases. If you have implemented restrictions on the ALTER DATABASE syntax, upgrade might fail. Restrictions to ALTER DATABASE can include the following:
Explicitly denying the ALTER DATABASE statement.
A data definition language (DDL) trigger on ALTER DATABASE that rolls back the transaction containing the ALTER DATABASE statement.
If you have restrictions on ALTER DATABASE, and Setup fails to upgrade system databases to SP1, you must disable these restrictions and then re-run Setup.
3.4.13 Upgrade Might Fail When Using SQL Server Authentication with User Instances
This issue only applies when upgrading an instance of SQL Server Express to SP1.
When you apply SP1, Setup upgrades system databases. When you apply SP1 to upgrade an instance of SQL Server Express that has user instances enabled, you must use Windows Authentication. If you specify SQL Server authentication, the upgrade might fail.
3.4.14 SQL Server Express Cannot Be Upgraded When a User Instance Is Running.
This issue only applies when upgrading an instance of SQL Server Express to SP1.
When a user instance is running, a number of database files in the Template Data folder are locked, and you cannot make any upgrades. To upgrade the SQL Server Express installation, you must manually shut down the running user instances.
Connect to the parent instance of SQL Server Express, and then disable the user instance by running the following statement:
EXEC sp_configure 'user instances enabled',0; RECONFIGURE;
Determine the pipe name for any active user instance by running the following statement:
SELECT owning_principal_name, instance_pipe_name FROM sys.dm_os_child_instances WHERE heart_beat = 'alive';
Connect to each user instance by using the instanstance_pipe_name, and then manually shut down the instance by running the following statement:
SHUTDOWN WITH NOWAIT;
Apply the update.
Re-enable user instances by running the following statement:
EXEC sp_configure 'user instances enabled', 1; RECONFIGURE;
4.0 Additional Information
This section describes additional considerations for using SQL Server Express SP1. This section is intended primarily for users who are new to SQL Server Express.
4.1 Using SQL Server Express
After you install SQL Server Express, use the following command to connect to an instance of SQL 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 instance you want to connect to. If you have used the default named instance during setup, specify the instance as "SQLExpress".
For information about connecting to and managing a SQL Server Express database, see Microsoft Knowledge Base article
4.2 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 default installation, you cannot remotely connect to SQL Server Express. You will need to enable TCP/IP and check if the Windows firewall exception is enabled.
From the Start menu, choose All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.
Optionally, you can open Computer Manager by right-clicking My Computer and choosing Manage. In Computer Management, expand Services and Applications, expand SQL Server Configuration Manager.
Expand SQL Server 2005 Network Configuration, and then click Protocols for InstanceName.
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.
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 that SQL Server is listed, but not selected as an exception. If you select the check 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.
Locate drive:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\BINN
Add the file sqlservr.exe to the list of exceptions.
- Click Add Program.
|You might also need to configure any third-party hardware or software firewalls to enable connections to SQL Server Express.|
4.3 Getting SQL Server Express Assistance
There are three principal sources of information about SQL Server Express:
SQL Server Express documentation and the updated SQL Server 2005 Books Online documentation.
SQL Server sites on
Microsoft Developer Network (MSDN)and TechNet.
SQL Server community.
Do not use other Microsoft newsgroups for posting questions regarding SQL Server Express. For more information, see "Getting SQL Server Express Assistance" in SQL Server Books Online. The latest information from the SQL Server Express team can be found at the
4.4 Providing Feedback on SQL Server Express SP1
To provide suggestions and bug reports on SQL Server Express SP1:
Send suggestions and bug reports about the features and user interface of SQL Server Express SP1 at the
MSDN product feedback Web site.
Send suggestions and report inaccuracies about the documentation using the feedback functionality in SQL Server 2005 Books Online.
Choose to send error reports and feature usage data automatically to Microsoft for analysis. For more information, see "Error and Usage Report Settings (SQL Server Express)" in SQL Server Books Online.
For more information, see "Providing Feedback on SQL Server 2005" in SQL Server Books Online.
5.0 Documentation Notes
This section covers significant issues that can occur after applying SQL Server Express SP1 and any late-breaking items that are not reflected in the updated SQL Server 2005 Books Online documentation. For more information, see 1.5 Updates to SQL Server 2005 Books Online Are Available. This section does not describe all of the fixes that are provided in SP1. For a complete list of these fixes, see Microsoft Knowledge Base article
5.1 Database Engine
The notes in this section are issues for the Database Engine and Database Engine-specific command prompt utilities that also apply to SQL Server Express.
5.1.1 User Instance Functionality
SQL Server Express lets non-administrator users to copy or move databases without requiring DBCreator privileges. For more information, see “User Instances for Non-Administrators” in SQL Server 2005 Books Online.
5.1.2 Considerations for the Autorecovered Shadow Copy Feature of the Volume Shadow Copy Service
The autorecovered shadow copy feature of the Volume Shadow Copy Service (VSS) has the following limitations.
Multiple Persisted Autorecovered Shadow Copies
On Windows Server 2003 SP1 and later, you can create only a single persisted autorecovered shadow copy. To create an additional shadow copy, you must first apply the update described in Knowledge Base article
|If you have not applied this update, you can create a new persisted autorecovered 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 shadow copy, the full-text catalog remains offline permanently. All other data remains available in the attached database.
When a database that contains a full-text catalog is attached directly from an autorecovered shadow copy, the attach operation returns the following error message:
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 avoid this situation by copying the database files and full-text catalogs from the shadow copy to a regular drive letter-based volume, and then attaching the database from that location. If the attach command specifies the correct location of the copied full-text files, the full-text catalogs will work.
5.1.3 RC4 Encryption Should Not Be Used
Do not use RC4 encryption to protect your data in SQL Server Express. Use a block cipher such as AES 256 or Triple DES instead.
5.1.4 DBCC Error Reporting
Introduced in SQL Server Express SP1.
A mini-dump file (SQLDUMPnnnn.txt) is created in the SQL Server LOG directory whenever a DBCC CHECKDB, DBCC CHECKALLOC, DBCC CHECKFILEGROUP, or DBCC CHECKTABLE command detects a corruption error. When the Feature Usage data collection and Error Reporting features are enabled for the instance of SQL Server, the file is automatically forwarded to Microsoft. The collected data is used to improve SQL Server functionality. For more information, see "Error and Usage Report Settings" in SQL Server 2005 Books Online.
The dump file contains the results of the DBCC command and additional diagnostic output. The file has restricted discretionary access- control lists (DACLs). Access is limited to the SQL Server service account and members of the sysadmin role. By default, the sysadmin role contains all members of the Windows BUILTIN\Administrators group and the local administrator's group. The DBCC command does not fail if the data collection process fails.
5.1.5 Change to the Behavior of Uncommittable Transactions in a Batch
Introduced in SQL Server Express SP1.
When a batch is completed, the Database Engine automatically rolls back any active uncommittable transactions. Before the release of SQL Server Express SP1, uncommittable transactions had to be rolled back manually.
The notes in this section are late-breaking items for replication.
5.2.1 Replication is Disabled by Default
SQL Server Express can serve as a Subscriber for all types of replication, but replication is not installed by default for this edition.
On the Feature Selection page, expand Database Services.
Click Replication, and then click Entire feature will be installed on local hard drive.
On the Feature Selection page, click Client Components, and then click Entire feature will be installed on local hard drive.