Windows Internal Database: Difference between revisions

Content deleted Content added
No edit summary
Citation bot (talk | contribs)
Added date. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | #UCB_webform 1136/3458
 
(7 intermediate revisions by 7 users not shown)
Line 1:
'''Windows Internal Database''' (codenamed WYukon, sometimes referred to as SQL Server Embedded Edition) is a variant of [[SQL Server Express]] 2005–2014 that is included with [[Windows Server 2008]] (SQL 2005), [[Windows Server 2008 R2]] (SQL 2005), [[Windows Server 2012]] (SQL 2012), [[Windows Server 2012 R2]] (SQL 2012), [[Windows Server 2016]], [[Windows Server 2019]] and [[Windows Server 20122022]] (SQL 2014)<ref>{{Cite web |last=Marshall |first=Adam J. |date=2022-06-02 |title=WSUS Post-deployment Configuration Failed - Windows Server 2022 |url=https://www.ajtek.ca/wsus/wsus-post-deployment-configuration-failed-windows-server-2022/ |access-date=2022-12-07 |website=AJ Tek Corporation |language=en-US}}</ref> and is included with other free [[Microsoft]] products released after 2007 that require an SQL Server database backend. [[Windows SharePoint Services]] 3.0 and [[Windows Server Update Services]] 3.0 both include Windows Internal Database, which can be used as an alternative to using a retail edition of SQL Server. WID was a 32-bit application, even as a component of Windows Server 2008 64-bit, which installs in the path {{code|C:\Windows\sysmsi\ssee\}}<ref> In Windows Server 2012 and later, it is a 64-bit application, installed in {{cite webcode|C:\Windows\WID}}.
url=http://koobarspoint.blogspot.com/2008/10/moving-windows-internal-database.html
|title=Moving the Windows Internal Database
|work=Blog
|publisher=JAKOB MACIOLEK
}}</ref> In Windows Server 2012 and later, it is a 64-bit application, installed in {{code|C:\Windows\WID}}.
 
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)