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 |
||
(33 intermediate revisions by 27 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]]
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 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 |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)
Line 10 ⟶ 12:
}}</ref>
[[SQL Server Management Studio Express]] can be used to connect to an instance of Windows Internal Database using <code>\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query</code> (2003–2008) or <code>\\.\pipe\MICROSOFT##WID\tsql\query</code> (2012) as instance name. But this will only work locally, as Remote Connections cannot be enabled for this edition of SQL Server. ''Also note that "Windows Authentication" should be used (as opposed to SQL Server Authentication), and administrators seem to have the best results of authenticating successfully when logged on using the same administrative account that was created when Windows was installed.''
==References==
Line 16 ⟶ 18:
==External links==
* [http://go.microsoft.com/fwlink/?LinkId=79600 Planning and Architecture for Windows SharePoint Services 3.0 Technology]
* [http://go.microsoft.com/fwlink/?LinkId=71220 Release Notes for Microsoft Windows Server Update Services 3.0]
* [http://www.mssqltips.com/tip.asp?tip=1577 http://www.mssqltips.com/tip.asp?tip=1577]
{{database-software-stub}}
Line 25 ⟶ 27:
[[Category:Windows Server 2008]]
[[Category:Windows components]]
|