Windows Internal Database: Difference between revisions

Revision as of 16:44, 7 December 2022

Latest revision as of 12:03, 9 May 2024

(One intermediate revision by one other user not shown)

Line 3:

Windows Internal Database is not available as a standalone product for use by end-user applications; Microsoft provides SQL Server Express and [[Microsoft SQL Server]] for this purpose. Additionally, it is designed to only be accessible to [[Windows Service]]s running on the same machine.

Several components of Windows Server 2008 and 2012 use Windows Internal Database for their data storage: [[Active Directory Rights Management Services]], [[Windows System Resource Manager]], [[Universal Description Discovery and Integration|UDDI Services]], [[Active Directory Federation Services]] 2.0, Remote Desktop (standalone) Connection Broker, [[Windows_Server_2012#IP_address_managementIP address management (IPAM)|IPAM]]<ref>{{cite web|url=https://technet.microsoft.com/en-US/library/jj878342.aspx|title=IPAM Architecture

|work=TechNet|date=31 August 2016

|work=TechNet|publisher=Microsoft}}</ref> and Windows SharePoint Services. On Windows Server 2003, SharePoint and [[Windows Server Update Services]] will install Windows Internal Database and use it as a default data store if a retail SQL Server database instance is not provided. A Knowledge Base article published by Microsoft states that Windows Internal Database does not identify itself as a removable component, and provides instructions how it may be uninstalled by calling [[Windows Installer]] directly.<ref>{{cite web

|url=http://support.microsoft.com/kb/920277

|title=Windows Internal Database is not listed in the Add or Remove Programs tool and is not removed when you remove Windows SharePoint Services 3.0 from the computer (MSKB920277)