Tuesday, January 29, 2013

UNINSTALL SQL Server


Uninstall SQL

Start Registry Editor, and then locate the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallIn the left pane, click each GUID. For each GUID that you click, look for a display name in the right pane that matches the name of the redistributable file. When you see a display name that matches the name of the redistributable file, note the GUID that you clicked in the left pane.For each GUID that you noted in the previous step, run the following command at a command prompt:start /wait msiexec /x {GUID} SKIPREDISTPREREQS=1 /l*v c:\sqlredist_uninstall.log In this command, replace GUID with the GUID that you noted in the previous step.Open the file at C:\Sqlredist_uninstall.log. At the bottom of the file, locate a line that resembles the following line:MSI (s) (EC:F8) [12:52:18:007]: Product: Microsoft SQL Server 2005 Backward compatibility -- Removal completed successfully.If the uninstallation failed, note the component name and the GUID, and then save the Sqlredist_uninstall.log file.If all the other steps were successful, uninstall the SQL Server Native Client component by using Add or Remove Programs.Do not uninstall the SQL Server Native Client component if you have SQL Server components installed.If all the other steps were successful, uninstall the SQL Server Setup Support Files component by using Add or Remove Programs.If these steps did not uninstall all the components and all the files that are related to the instance of SQL Server, contact product support. For a complete list of product support telephone numbers, see the Microsoft Help and Support Web site.

----**-----------

On a computer that is running SQL Server 2005 along with previous SQL Server versions, Enterprise Manager and other programs that depend on SQL-DMO might be disabled. This can occur in the following situations:Side-by-side installations of any combination of SQL Server 2005, SQL Server 2000, and SQL Server 7.0, where any one or more of these instances is uninstalled.Side-by-side installations of SQL Server 2000 with SQL Server 2005, where SQL Server 2000 is installed after SQL Server 2005.This issue is due to removal of the registration for the SQL Server 2005 SQL-DMO COM library. To re-enable Enterprise Manager and other programs that have SQL-DMO dependencies, register SQL-DMO by running regsvr32.exe sqldmo.dll at the command prompt. For more information, see Troubleshooting an Installation of the SQL Server Database Engine.Before you remove SQL Server 2005 components from a computer that has the minimum required amount of physical memory, you must make sure that the page file size is equal to two times the amount of physical memory. Sometimes, insufficient virtual memory can cause an incomplete removal of SQL Server 2005.If you receive the following error message during SQL Server 2005 Setup, a SQL Server 2005 component was not uninstalled from the computer:A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component. Before you remove SQL Server 2005, follow these steps:Back up your data. You might have databases that you want to save in their present state. You might also want to save changes that were made to the system databases. If either situation is true, make sure that back up the data before you uninstall SQL Server 2005. Alternatively, save a copy of all the data and log files in a folder other than the MSSQL folder. The MSSQL folder is deleted during uninstallation.The files that you must save include the following database files. These files are installed as part of SQL Server 2005:Distmdl.*Master.*Mastlog.*Model.*Modellog.*Msdbdata.*Msdblog.*Mssqlsystemresource.*Northwind.* (This database is an optional installation.)Pubs.*Pubs_log.*Tempdb.*Templog.*ReportServer[$InstanceName] (This is the Reporting Services default database.)ReportServer[$InstanceName]TempDB (This is the Reporting Services default temporary database.)Delete the local security groups. Before you uninstall SQL Server 2005, delete the local security groups for SQL Server 2005 components.Save or rename SQL Server Reporting Services folders. If you use the SQL Server installation together with Reporting Services, save or rename the following folders and subfolders:<drive>\Microsoft SQL Server\Reporting Services<drive>\Microsoft SQL Server\MSSQL\Reporting Services<drive>\Microsoft SQL Server\<SQL Server instance name>\Reporting Services<drive>\Microsoft SQL Server\90\Tools\Reporting ServicesNote:If you used the SSRS configuration tool to configure the installation, the names might differ from the names in this list. Additionally, the databases might be located on a remote computer that is running SQL Server.Delete the Reporting Services virtual directories. Use Microsoft Internet Information Services (IIS) Manager to delete the following virtual directories:ReportServer[$InstanceName]Reports[$InstanceName]Delete the ReportServer application pool. Use IIS Manager to delete the ReportServer application pool.Stop all SQL Server services. We recommend that you stop all SQL Server services before you uninstall SQL Server 2005 components. Active connections can prevent successful uninstallation.Use an account that has the appropriate permissions. Log on to the server by using the SQL Server service account or by using an account that has equivalent permissions. For example, you can log on to the server by using an account that is a member of the local Administrators group.Caution: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.Note:You must perform the uninstallation steps listed here in the exact order given.To manually uninstall an instance of SQL Server 2005Make sure that the SQL Server Setup Support Files component is installed.In Add or Remove Programs, make sure that Microsoft SQL Server Setup Support Files appears in the list of installed programs. If Microsoft SQL Server Setup Support Files appears in the list, go to step 2.If Microsoft SQL Server Setup Support Files does not appear in the list, install this component before you continue. To do this, from the SQL Server 2005 installation media, double-click the Servers\setup\sqlsupport.msi file. In step 5 of this procedure, you will uninstall the Microsoft SQL Server Setup Support Files component.At the command prompt, run the following command to uninstall the SQL Server components:%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\ARPWrapper.exe /Remove Uninstall the SQL Server components one at a time until all the SQL Server components are uninstalled.Note:Add or Remove Programs also runs the ARPWrapper.exe program by using the /Remove option. However, the reference to the ARPWrapper.exe program might have been deleted.If you receive any of the following error messages, see the "If you experience problems" section that follows.Registry Enumeration FailedIf you have an instance of SQL Server that has more than one server component, such as the Database Engine and Analysis Services installed, setup will fail, and you receive the following error message:The setup has encountered an unexpected error in datastore. The action is RestoreSetupParams.This error is expected because of refcounting. A refcount is used to track how many programs use the same .dll file or the same .msi file. When a program is uninstalled, the program decrements the refcount for an .msi file by one. When the last program is uninstalled, the .msi file is deleted. In this case, the .msi file is the SQL Server Setup Support Files component (SqlSupport.msi). If you receive this error message, use one of the following methods to resolve the error:Reinstall the SQL Server Setup Support Files component (SqlSupport.msi) before you uninstall each component in the instance.Temporarily refcount the SqlSupport.msi file to itself. To do this, follow these steps:Obtain the GUID for the Microsoft SQL Server Setup Support Files component. To obtain the GUID, follow steps 1 and 2 from the "If you experience problems" section.Use Registry Editor to create or to modify the following registry key with these values:Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap\MSIRefCountValue: UninstallType: REG_SZ Data: {11111111-1111-1111-1111-111111111111},{GUID}Note   GUID is a placeholder for the GUID of the SQL Server support files. For example, the GUID of the English x86 SQL Server support files is as follows:Data: {11111111-1111-1111-1111-111111111111},{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}If you experience problemsIf you experience problems when you try to uninstall the SQL Server components, follow these steps:Start Registry Editor, and then locate the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallIn the left pane, click each GUID. For each GUID that you click, look for a display name in the right pane that includes "Microsoft SQL Server 2005." For example, look for the following names:Microsoft SQL Server 2005Microsoft SQL Server 2005 Analysis ServicesMicrosoft SQL Server 2005 Reporting ServicesMicrosoft SQL Server 2005 Notification ServicesMicrosoft SQL Server 2005 Integration ServicesMicrosoft SQL Server 2005 ToolsMicrosoft SQL Server 2005 Books OnlineWhen you see a display name that includes "Microsoft SQL Server 2005," note the GUID that you clicked in the left pane.For each GUID that you noted in the previous step, run the following command at the command prompt:start /wait msiexec /x {GUID} /l*v c:\sql_uninstall.log Notes:In this command, replace GUID with the GUID that you noted in the previous step.If you receive the following error message, contact product support.The setup has encountered an unexpected error in datastore. Please contact a Customer Support representative.For a complete list of product support telephone numbers and for information about support costs, see the support contact information Microsoft Web site.Open the file at C:\Sql_uninstall.log. Approximately 15 lines from the bottom of the file, locate a line that resembles the following:MSI (s) (EC:F8) [12:52:18:007]: Product: Microsoft SQL Server 2005 Tools -- Removal completed successfully.If the uninstallation failed, note the component name and the GUID, and then save the Sql_uninstall.log file.Use Add or Remove Programs to uninstall the support components in the following order:MSXML 6.0 ParserSQLXML4SQL Server VSS WriterSQL Server 2005 Backward CompatibilityAnything else that is related to SQL Server 2005, except for the SQL Server Native Client component and for the SQL Server Setup Support Files component.If the uninstallation fails for any one of the support components, you might receive the following error message:Setup failed due to missing prerequisitesIf you receive this error message, follow these steps:Start Registry Editor, and then locate the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallIn the left pane, click each GUID. For each GUID that you click, look for a display name in the right pane that matches the name of the redistributable file. When you see a display name that matches the name of the redistributable file, note the GUID that you clicked in the left pane.For each GUID that you noted in the previous step, run the following command at a command prompt:start /wait msiexec /x {GUID} SKIPREDISTPREREQS=1 /l*v c:\sqlredist_uninstall.log In this command, replace GUID with the GUID that you noted in the previous step.Open the file at C:\Sqlredist_uninstall.log. At the bottom of the file, locate a line that resembles the following line:MSI (s) (EC:F8) [12:52:18:007]: Product: Microsoft SQL Server 2005 Backward compatibility -- Removal completed successfully.If the uninstallation failed, note the component name and the GUID, and then save the Sqlredist_uninstall.log file.If all the other steps were successful, uninstall the SQL Server Native Client component by using Add or Remove Programs.Do not uninstall the SQL Server Native Client component if you have SQL Server components installed.If all the other steps were successful, uninstall the SQL Server Setup Support Files component by using Add or Remove Programs.If these steps did not uninstall all the components and all the files that are related to the instance of SQL Server, contact product



----------

tup Configuration Checker (SCC) in Microsoft SQL Server Setup verifies the value of the 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 will fail, and Setup will be blocked.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.To manually set the increment for the counter registry keyOn the Microsoft Windows 2003 or Windows XP desktop, click Start, click Run, type regedit.exe in Open, and then click OK. On Windows 2000, use regedt32.exe The Registry Editor launches.Navigate to the following registry key:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib]"Last Counter"=dword:00000ed4 (5276)"LastHelp"=dword:00000ed5 (5277)The "Last Counter" value from the previous step (5276) must match 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 match the maximum value of the "Help" key from "Perflib\009" in the following registry key:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009]Note that 009 is an example from the English language. The "Last Counter" and "Last Help" values are dynamically assigned by Windows; they will vary from machine to machine.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-hand pane, click Modify, click Base = "Decimal," set the value in Value data, and then click OK. Repeat for the other key, if necessary, and then close the Registry Editor.Run SQL Server Setup again.See Also

----
Microsoft SQL Server 2005 Setup checks that COM+ is properly configured. If configuration errors are found, Setup will continue, but the following warning appears in the System Configuration Check (SCC) report:"If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup."COM+ errors can result when Microsoft Distributed Transaction Coordinator (MS DTC) is not running or, in the case of Microsoft Cluster Server, if MS DTC is not a clustered resource. COM+ depends upon MS DTC, and the Message Queue Task in Integration Services depends upon COM +. If COM+ errors occur, the Message Queue Task in Integration Services will not be available until the COM+ system is properly configured.To use Message Queuing (also known as MSMQ), ensure that MS DTC is running and properly configured. If SQL Server is installed on a cluster, MS DTC must be a cluster resource.Use the following procedures to reinstall COM+.To install the Component Services snap-inFrom the Windows desktop, click Start and then click Run.In Open, type MMC, and then click OK.In the Console window, click File on the menu bar, and then click Add/Remove Snap-in.In the Add/Remove Snap-in window, click Add.In the Add Standalone Snap-in window, select Component Services from the list of snap-ins, and then click Add.Click Close to close the Add Stand-alone Snap-in window, and then click OK to close the Add/Remove Snap-in window.In the Console Root\Component Services window, expand the Component Services tree. This is where any error message would occur if there was a problem with COM+.Run SQL Server 2005 Setup again. If you get an error message, reinstall COM+.To reinstall COM+From Add or Remove Programs in Control Panel, click Add/Remove Windows Components.In the Windows Components Wizard, click Next without making any selection changes.Click through to complete the wizard, and then run SQL Server 2005 Setup again.See Also


Changing SQL Server Services Accounts After InstallationAfter you have installed SQL Server 2005, use SQL Server Configuration Manager to change the assigned password or other properties of any SQL Server–related service. Each service must be changed individually. The new user account takes effect when the service is restarted.Important:You should not change the passwords for any of the SQL Server service accounts when a failover cluster node is down or offline. If you have to do this, you will need to reset the password again using Configuration Manager when all nodes are back online.The following rights are granted to the accounts:SeServiceLogonRight, which allows the account to run as a service.SeLockMemoryPrivilege, which allows the account to use the AWE memory feature of SQL Server.SeTcbPrivilege, which allows the account to impersonate other accounts.If you are running SQL Server in a failover cluster configuration, permissions are also set for all files in the binary and data installation locations for all nodes in the cluster. Permission is also granted for the service account on the Cluster Object.Caution:If you are running Microsoft Windows 2000 and want to use the Windows 2000 Encrypted File System to encrypt any SQL Server files, you must unencrypt the files before you can change the SQL Server service accounts. If you do not unencrypt the files and then reset the SQL Server service accounts, you cannot unencrypt the files.Changing the current service account for SQL Server to a non-administrator account causes existing full-text catalogs to become inaccessible. Either rebuild and perform a full population of all catalogs belonging to this instance of SQL Server, or switch back to an account with administrator permissions.You can change the SQLServerAgent service account to a non Windows NT 4.0 administrator account. However, the Windows NT 4.0 account must be a member of the sysadmin fixed server role to run SQL Server Agent.For more information, see Setting Up Windows Service Accounts. For information about using the Services add-in for Windows to change SQL Server service accounts, see How to change the SQL Server or SQL Server Agent service account without using SQL Enterprise Manager in SQL Server 2000 or SQL Server Configuration Manager in SQL Server 2005.Windows Passwords ChangesIf your Windows password changes after SQL Server 2005 is installed – e.g., your password expires - you must also revise the user account information for SQL Server services in Windows.To change SQL Server services login account information (Windows 2000)After changing the SQL Server service account information in Control Panel, you must also change the SQL Server service account in SQL Server Configuration Manager. This allows the service account information for Microsoft Search service to remain synchronized as well.Security Note:Setting strong passwords is essential to the security of your system. Always use strong passwords.Important:Although the Microsoft Search service is always assigned to the local system account, the full-text search engine tracks the SQL Server service account in Windows. Full-text search and failover clustering are not available if Windows password changes are not reset.For more information about creating Windows user accounts, granting advanced user rights, setting password expiration, and managing group memberships, see the Windows documentation or User Manager for Domains Help. For Microsoft Windows 2000 users, see Computer Management or Group Policy Editor in the Windows 2000 documentation.See Also

-_-_-----_-

http://msdn.microsoft.com/en-US/library/ms143693(v=sql.90).aspx

Changing SQL Server Services Accounts After InstallationAfter you have installed SQL Server 2005, use SQL Server Configuration Manager to change the assigned password or other properties of any SQL Server–related service. Each service must be changed individually. The new user account takes effect when the service is restarted.Important:You should not change the passwords for any of the SQL Server service accounts when a failover cluster node is down or offline. If you have to do this, you will need to reset the password again using Configuration Manager when all nodes are back online.The following rights are granted to the accounts:SeServiceLogonRight, which allows the account to run as a service.SeLockMemoryPrivilege, which allows the account to use the AWE memory feature of SQL Server.SeTcbPrivilege, which allows the account to impersonate other accounts.If you are running SQL Server in a failover cluster configuration, permissions are also set for all files in the binary and data installation locations for all nodes in the cluster. Permission is also granted for the service account on the Cluster Object.Caution:If you are running Microsoft Windows 2000 and want to use the Windows 2000 Encrypted File System to encrypt any SQL Server files, you must unencrypt the files before you can change the SQL Server service accounts. If you do not unencrypt the files and then reset the SQL Server service accounts, you cannot unencrypt the files.Changing the current service account for SQL Server to a non-administrator account causes existing full-text catalogs to become inaccessible. Either rebuild and perform a full population of all catalogs belonging to this instance of SQL Server, or switch back to an account with administrator permissions.You can change the SQLServerAgent service account to a non Windows NT 4.0 administrator account. However, the Windows NT 4.0 account must be a member of the sysadmin fixed server role to run SQL Server Agent.For more information, see Setting Up Windows Service Accounts. For information about using the Services add-in for Windows to change SQL Server service accounts, see How to change the SQL Server or SQL Server Agent service account without using SQL Enterprise Manager in SQL Server 2000 or SQL Server Configuration Manager in SQL Server 2005.Windows Passwords ChangesIf your Windows password changes after SQL Server 2005 is installed – e.g., your password expires - you must also revise the user account information for SQL Server services in Windows.To change SQL Server services login account information (Windows 2000)After changing the SQL Server service account information in Control Panel, you must also change the SQL Server service account in SQL Server Configuration Manager. This allows the service account information for Microsoft Search service to remain synchronized as well.Security Note:Setting strong passwords is essential to the security of your system. Always use strong passwords.Important:Although the Microsoft Search service is always assigned to the local system account, the full-text search engine tracks the SQL Server service account in Windows. Full-text search and failover clustering are not available if Windows password changes are not reset.For more information about creating Windows user accounts, granting advanced user rights, setting password expiration, and managing group memberships, see the Windows documentation or User Manager for Domains Help. For Microsoft Windows 2000 users, see Computer Management or Group Policy Editor in the Windows 2000 documentation.See Also



SQL Server Agent is a Microsoft SQL Server 2005 component that lets you automate some administrative tasks. SQL Server Agent runs jobs, monitors SQL Server, and processes alerts.The Microsoft Windows account types that are supported and that you can use to run the SQL Server Agent service are listed in the table in the "More information" section. Use SQL Server Configuration Manager to set the service account for SQL Server Agent. For more information, see the "How to set the service startup account for SQL Server Agent (SQL Server Configuration Manager)" topic in SQL Server 2005 Books Online (December 2005 update).To obtain SQL Server 2005 Books Online (December 2005 update), visit the following Microsoft Web site:http://technet.microsoft.com/en-us/sqlserver/bb428874.aspxBack to the top | Give Feedback

MORE INFORMATION

Supported service account types

The following table lists the Windows account types that are supported and that you can use to run the SQL Server Agent service.Service account typeNonclustered serverClustered serverDomain controller (nonclustered)Windows domain account (member of the Windows Administrators group)SupportedSupportedSupportedWindows domain account (nonadministrative)Supported (see limitation 1)Supported (see limitation 1)Supported (see limitation 1)Network Service account (NT AUTHORITY\NetworkService)Supported (see limitations 1, 4, and 5)Not supportedNot supportedLocal user account (nonadministrative)Supported (see limitations 1 and 3)Not supportedNot applicableLocal System account (NT AUTHORITY\System)Supported (see limitation 2)Not supportedSupported (see limitation 2)Local Service account (NT AUTHORITY\LocalService)Not supportedNot supportedNot supported

Limitation 1: When you use a nonadministrative account for multiple-server administration

When you use a nonadministrative account for multiple-server administration, you cannot enlist target servers to a master server, and the following error message may be logged:"The enlist operation failed."To resolve this problem, restart both the SQL Server service and the SQL Server Agent service. For more information, see the following topics in SQL Server 2005 Books Online (December 2005 update):"How to restart an instance of SQL Server (SQL Server Management Studio)""How to restart the SQL Server Agent service (SQL Server Management Studio)"

Limitation 2: When you use the Local System account for multiple-server administration

Multiple-server administration is supported when the SQL Server Agent service runs under the Local System account only when both the master server and the target server reside on the same computer. If you use this configuration, you receive the following message when you enlist target servers to the master server:Ensure the agent start-up account for <target_server_computer_name> has rights to log on as targetServer.You can safely ignore this informational message. The enlistment operation should successfully finish. For more information, see the "Creating a multiserver environment" topic in SQL Server 2005 Books Online (December 2005 update).

Limitation 3: When you use a local user account

Jobs that use proxies will fail if the SQL Server Agent service runs under a local user account and the SQL Server service runs under a different account.To resolve this problem, configure the SQL Server Agent service and the SQL Server service to run under the same local account, and then restart both services. For more information, see the following topics in SQL Server 2005 Books Online (December 2005 update):"How to change the service startup account for SQL Server (SQL Server Configuration Manager)""How to set the service startup account for SQL Server Agent (SQL Server Configuration Manager)""Setting up Windows service accounts"Note Limitation 3 does not apply to Microsoft SQL Server 2005 Service Pack 1 (SP1). For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:913089 How to obtain the latest service pack for SQL Server 2005

Limitation 4: When you use the Network Service account and the Network Service account is a SQL Server user

SQL Server Agent may not start if the following conditions are true:You configure the SQL Server Agent service to run under the Network Service account.The Network Service account was explicitly granted access to log in to an instance of SQL Server as a SQL Server user.To resolve this problem, restart the computer that is running SQL Server. You only have to restart the computer one time.

Limitation 5: When you use the Network Service account and SQL Server Reporting Services is running on the same computer

SQL Server Agent may not start if the following conditions are true:You configure the SQL Server Agent service to run under the Network Service account.SQL Server Reporting Services is also running on the same computer.To resolve this problem, restart the computer that is running SQL Server, and then restart both the SQL Server service and the SQL Server Agent service. You only have to do this one time.Back to the top | Give Feedback





-----

http://msdn.microsoft.com/en-US/library/ms143693(v=sql.90).aspx


http://msdn.microsoft.com/en-US/library/ms183753(v=sql.90).aspx


http://msdn.microsoft.com/en-US/library/ms188980(v=sql.90).aspx

http://msdn.microsoft.com/en-us/library/ms173764(v=sql.90).aspx

No comments:

Post a Comment