Extensible Storage Engine - Revision history

7kk: Adding local short description: "Microsoft embedded database engine", overriding Wikidata description "Microsoft embedded database engine"

2025-03-05T01:06:24Z

Adding local short description: "Microsoft embedded database engine", overriding Wikidata description "Microsoft embedded database engine"

← Previous revision		Revision as of 01:06, 5 March 2025
Line 1:		Line 1:
			{{Short description\|Microsoft embedded database engine}}
	{{For\|'''JET Red''' storage engine of [[Microsoft Access]]\|Access Database Engine}}		{{For\|'''JET Red''' storage engine of [[Microsoft Access]]\|Access Database Engine}}
	{{more footnotes\|date=February 2021}}		{{more footnotes\|date=February 2021}}

Frap: /* Comparison to JET Red */

2023-12-14T10:47:57Z

Comparison to JET Red

← Previous revision		Revision as of 10:47, 14 December 2023
Line 241:		Line 241:
	* JET Red is a file sharing technology, while ESE is designed to be embedded in a server application, and does not share files.		* JET Red is a file sharing technology, while ESE is designed to be embedded in a server application, and does not share files.
	* JET Red makes best effort file recovery, while ESE has write ahead logging and snapshot isolation for guaranteed crash recovery.		* JET Red makes best effort file recovery, while ESE has write ahead logging and snapshot isolation for guaranteed crash recovery.
	* JET Red before version 4.0 supports only page level locking, while ESE and JET Red version 4.0 supports record level locking.		* JET Red before version 4.0 supports only page-level locking, while ESE and JET Red version 4.0 supports record-level locking.
	* JET Red supports a wide variety of query interfaces, including [[ODBC]] and [[OLE DB]]. ESE does not ship with a query engine but instead relies on applications to write their own queries as [[C (programming language)\|C]] ISAM code.		* JET Red supports a wide variety of query interfaces, including [[ODBC]] and [[OLE DB]]. ESE does not ship with a query engine but instead relies on applications to write their own queries as [[C (programming language)\|C]] ISAM code.
	* JET Red has a maximum database file size of 2 [[Gibibyte\|GiB]], while ESE has a maximum database file size of 8 [[Tebibyte\|TiB]] with 4 [[Kibibyte\|KiB]] pages, and 16 TiB with 8 KiB pages.		* JET Red has a maximum database file size of 2 [[Gibibyte\|GiB]], while ESE has a maximum database file size of 8 [[Tebibyte\|TiB]] with 4 [[Kibibyte\|KiB]] pages, and 16 TiB with 8 KiB pages.

HeyElliott: WP:N'T

2023-12-12T23:35:02Z

WP:N'T

← Previous revision		Revision as of 23:35, 12 December 2023
Line 21:		Line 21:
	\| license = [[MIT License]]		\| license = [[MIT License]]
	}}		}}
	'''Extensible Storage Engine''' ('''ESE'''), also known as '''JET Blue''', is an [[ISAM]] (indexed sequential access method) data storage technology from [[Microsoft]]. ESE is the core of [[Microsoft Exchange Server]], [[Active Directory]], and [[Windows Search]]. It's also used by a number of Windows components including [[Windows Update]] client and [[Help and Support Center]]. Its purpose is to allow applications to store and retrieve data via indexed and sequential access.		'''Extensible Storage Engine''' ('''ESE'''), also known as '''JET Blue''', is an [[ISAM]] (indexed sequential access method) data storage technology from [[Microsoft]]. ESE is the core of [[Microsoft Exchange Server]], [[Active Directory]], and [[Windows Search]]. It is also used by a number of Windows components including [[Windows Update]] client and [[Help and Support Center]]. Its purpose is to allow applications to store and retrieve data via indexed and sequential access.

	ESE provides [[Transaction (database)\|transacted]] data update and retrieval. A crash recovery mechanism is provided so that [[data consistency]] is maintained even in the event of a system crash. Transactions in ESE are highly concurrent making ESE suitable for server applications. ESE caches data intelligently to ensure high performance access to data. In addition, ESE is lightweight making it suitable for auxiliary applications.		ESE provides [[Transaction (database)\|transacted]] data update and retrieval. A crash recovery mechanism is provided so that [[data consistency]] is maintained even in the event of a system crash. Transactions in ESE are highly concurrent making ESE suitable for server applications. ESE caches data intelligently to ensure high performance access to data. In addition, ESE is lightweight making it suitable for auxiliary applications.

Citation bot: Add: date. | Use this bot. Report bugs. | Suggested by Abductive | #UCB_webform 1041/3850

2022-10-31T01:22:52Z

Add: date. | Use this bot. Report bugs. | Suggested by Abductive | #UCB_webform 1041/3850

← Previous revision		Revision as of 01:22, 31 October 2022
Line 235:		Line 235:
	Cheen Liao, Stephen Hecht, Matthew Bellew, Ian Jose, Edward "Eddie" Gilbert, Kenneth Kin Lum, Balasubramanian Sriram, Jonathan Liem, Andrew Goodsell, Laurion Burchall, Andrei Marinescu, Adam Foxman, Ivan Trindev, Spencer Low and Brett Shirley.		Cheen Liao, Stephen Hecht, Matthew Bellew, Ian Jose, Edward "Eddie" Gilbert, Kenneth Kin Lum, Balasubramanian Sriram, Jonathan Liem, Andrew Goodsell, Laurion Burchall, Andrei Marinescu, Adam Foxman, Ivan Trindev, Spencer Low and Brett Shirley.

	In January 2021 Microsoft open sourced ESE.<ref>{{cite web\|url=https://petri.com/microsoft-open-source-ese-database \|title=Microsoft Open Sources ESE, the Extensible Storage Engine \|access-date=2021-02-05}}</ref> It was posted to GitHub with the permissive [[MIT License]].		In January 2021 Microsoft open sourced ESE.<ref>{{cite web\|url=https://petri.com/microsoft-open-source-ese-database \|title=Microsoft Open Sources ESE, the Extensible Storage Engine \|date=3 February 2021 \|access-date=2021-02-05}}</ref> It was posted to GitHub with the permissive [[MIT License]].

	==Comparison to JET Red==		==Comparison to JET Red==

Citation bot: Alter: title. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | #UCB_webform 1843/3804

2022-08-23T09:19:32Z

Alter: title. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | #UCB_webform 1843/3804

← Previous revision		Revision as of 09:19, 23 August 2022
Line 223:		Line 223:
	When an ESENT database is created, the physical [[disk sector]] size is stored with the database. The physical sector size is expected to remain consistent between sessions; otherwise, an error is reported. When a physical drive is cloned or restored from a drive image to a drive that uses a different physical sector size ([[Advanced Format]] Drives), ESENT will report errors.<ref>{{Cite web\|url=https://kb.acronis.com/content/36451\|title=Acronis Products: Applications Build on ESENT Running on Windows Vista, Windows Server 2008 and Windows 7 may not work correctly after restoring or cloning to a drive with different physical sector \| Knowledge Base\|website=kb.acronis.com}}</ref>		When an ESENT database is created, the physical [[disk sector]] size is stored with the database. The physical sector size is expected to remain consistent between sessions; otherwise, an error is reported. When a physical drive is cloned or restored from a drive image to a drive that uses a different physical sector size ([[Advanced Format]] Drives), ESENT will report errors.<ref>{{Cite web\|url=https://kb.acronis.com/content/36451\|title=Acronis Products: Applications Build on ESENT Running on Windows Vista, Windows Server 2008 and Windows 7 may not work correctly after restoring or cloning to a drive with different physical sector \| Knowledge Base\|website=kb.acronis.com}}</ref>

	This is a known issue and Microsoft has hot fixes available. For Windows Vista or Windows Server 2008 see KB2470478.<ref>{{Cite web \|url=http://support.microsoft.com/kb/2470478 \|title=~~Archived~~ ~~copy~~ \|access-date=2014-11-19 \|archive-date=2015-02-28 \|archive-url=https://web.archive.org/web/20150228070300/http://support.microsoft.com/kb/2470478 \|url-status=dead }}</ref> For Windows 7 or Windows Server 2008 R2 see KB982018.<ref>{{Cite web\|url=https://support.microsoft.com/en-us/topic/an-update-that-improves-the-compatibility-of-windows-7-and-windows-server-2008-r2-with-advanced-format-disks-is-available-004a02e4-7812-e14f-9dd7-d5e61c3ee20e\|title=An update that improves the compatibility of Windows 7 and Windows Server 2008 R2 with Advanced Format Disks is available\|website=support.microsoft.com}}</ref>		This is a known issue and Microsoft has hot fixes available. For Windows Vista or Windows Server 2008 see KB2470478.<ref>{{Cite web \|url=http://support.microsoft.com/kb/2470478 \|title=Applications that are built on ESENT and that run on a Windows Vista-based or Windows Server 2008-based computer may not work correctly after the reported physical sector size of the storage device changes \|access-date=2014-11-19 \|archive-date=2015-02-28 \|archive-url=https://web.archive.org/web/20150228070300/http://support.microsoft.com/kb/2470478 \|url-status=dead }}</ref> For Windows 7 or Windows Server 2008 R2 see KB982018.<ref>{{Cite web\|url=https://support.microsoft.com/en-us/topic/an-update-that-improves-the-compatibility-of-windows-7-and-windows-server-2008-r2-with-advanced-format-disks-is-available-004a02e4-7812-e14f-9dd7-d5e61c3ee20e\|title=An update that improves the compatibility of Windows 7 and Windows Server 2008 R2 with Advanced Format Disks is available\|website=support.microsoft.com}}</ref>

	==History==		==History==

InternetArchiveBot: Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.8.8) (Ost316 - 10300

2022-07-08T20:47:49Z

Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.8.8) (Ost316 - 10300

← Previous revision		Revision as of 20:47, 8 July 2022
Line 223:		Line 223:
	When an ESENT database is created, the physical [[disk sector]] size is stored with the database. The physical sector size is expected to remain consistent between sessions; otherwise, an error is reported. When a physical drive is cloned or restored from a drive image to a drive that uses a different physical sector size ([[Advanced Format]] Drives), ESENT will report errors.<ref>{{Cite web\|url=https://kb.acronis.com/content/36451\|title=Acronis Products: Applications Build on ESENT Running on Windows Vista, Windows Server 2008 and Windows 7 may not work correctly after restoring or cloning to a drive with different physical sector \| Knowledge Base\|website=kb.acronis.com}}</ref>		When an ESENT database is created, the physical [[disk sector]] size is stored with the database. The physical sector size is expected to remain consistent between sessions; otherwise, an error is reported. When a physical drive is cloned or restored from a drive image to a drive that uses a different physical sector size ([[Advanced Format]] Drives), ESENT will report errors.<ref>{{Cite web\|url=https://kb.acronis.com/content/36451\|title=Acronis Products: Applications Build on ESENT Running on Windows Vista, Windows Server 2008 and Windows 7 may not work correctly after restoring or cloning to a drive with different physical sector \| Knowledge Base\|website=kb.acronis.com}}</ref>

	This is a known issue and Microsoft has hot fixes available. For Windows Vista or Windows Server 2008 see KB2470478.<ref>http://support.microsoft.com/kb/2470478 ~~{{Dead~~ ~~link~~\|date=~~February~~ ~~2022~~}}</ref> For Windows 7 or Windows Server 2008 R2 see KB982018.<ref>{{Cite web\|url=https://support.microsoft.com/en-us/topic/an-update-that-improves-the-compatibility-of-windows-7-and-windows-server-2008-r2-with-advanced-format-disks-is-available-004a02e4-7812-e14f-9dd7-d5e61c3ee20e\|title=An update that improves the compatibility of Windows 7 and Windows Server 2008 R2 with Advanced Format Disks is available\|website=support.microsoft.com}}</ref>		This is a known issue and Microsoft has hot fixes available. For Windows Vista or Windows Server 2008 see KB2470478.<ref>{{Cite web \|url=http://support.microsoft.com/kb/2470478 \|title=Archived copy \|access-date=2014-11-19 \|archive-date=2015-02-28 \|archive-url=https://web.archive.org/web/20150228070300/http://support.microsoft.com/kb/2470478 \|url-status=dead }}</ref> For Windows 7 or Windows Server 2008 R2 see KB982018.<ref>{{Cite web\|url=https://support.microsoft.com/en-us/topic/an-update-that-improves-the-compatibility-of-windows-7-and-windows-server-2008-r2-with-advanced-format-disks-is-available-004a02e4-7812-e14f-9dd7-d5e61c3ee20e\|title=An update that improves the compatibility of Windows 7 and Windows Server 2008 R2 with Advanced Format Disks is available\|website=support.microsoft.com}}</ref>

	==History==		==History==

BrownHairedGirl: {{Dead link}} tag on bare URL refs which return HTTP 404 or 410

2022-02-23T11:49:31Z

{{Dead link}} tag on bare URL refs which return HTTP 404 or 410

← Previous revision		Revision as of 11:49, 23 February 2022
Line 1:		Line 1:
	{{For\|'''JET Red''' storage engine of [[Microsoft Access]]\|Access Database Engine}}		{{For\|'''JET Red''' storage engine of [[Microsoft Access]]\|Access Database Engine}}
	{{~~inline~~\|date=February 2021}}		{{more footnotes\|date=February 2021}}
	{{Infobox software		{{Infobox software
	\| name = Extensible Storage Engine		\| name = Extensible Storage Engine
Line 147:		Line 147:
	{\| style="width:8em; text-align:center; background:#f5f5f5; margin:auto;" class="wikitable"		{\| style="width:8em; text-align:center; background:#f5f5f5; margin:auto;" class="wikitable"
	\|-		\|-
	\|“I love JET”<br/>		\|“I love JET”<br />
	“ love JET ”<br/>		“ love JET ”<br />
	“love JET B”<br/>		“love JET B”<br />
	“ove JET Bl”<br/>		“ove JET Bl”<br />
	“ve JET Blu”<br/>		“ve JET Blu”<br />
	“e JET Blue”<br/>		“e JET Blue”<br />
	“ JET Blue”<br/>		“ JET Blue”<br />
	“JET Blue”<br/>		“JET Blue”<br />
	“ET Blue”<br/>		“ET Blue”<br />
	“T Blue”<br/>		“T Blue”<br />
	“ Blue”<br/>		“ Blue”<br />
	“Blue”<br/>		“Blue”<br />
	\|}		\|}
	Even though tuple indexes can be very large, they can significantly speed queries of the form: ''find all records containing “JET Blue”''. They can be used for sub-strings longer than the maximum tuple length by dividing the search sub-string into maximum tuple length search strings and intersecting the results. They can be used for exact matches for strings as long as the maximum tuple length or as short as the minimum tuple length, with no index intersection. For more information on performing index intersection in ESE see [[#Index intersection\|Index Intersection]]. Tuple indexes cannot speed queries where the search string is shorter than the minimum tuple length.		Even though tuple indexes can be very large, they can significantly speed queries of the form: ''find all records containing “JET Blue”''. They can be used for sub-strings longer than the maximum tuple length by dividing the search sub-string into maximum tuple length search strings and intersecting the results. They can be used for exact matches for strings as long as the maximum tuple length or as short as the minimum tuple length, with no index intersection. For more information on performing index intersection in ESE see [[#Index intersection\|Index Intersection]]. Tuple indexes cannot speed queries where the search string is shorter than the minimum tuple length.
Line 219:		Line 219:

	Restore can be used to apply a single backup, or it can be used to apply a combination of a single full backup with one or more incremental backups. Further, any existing log files can be replayed as well to recreate an entire data set all the way up to the last transaction logged as committed to transaction level 0. Restoration of a backup can be made to any system capable of supporting the original application. It need not be the same machine, or even the same machine configuration. Location of files can be changed as part of the restoration process.		Restore can be used to apply a single backup, or it can be used to apply a combination of a single full backup with one or more incremental backups. Further, any existing log files can be replayed as well to recreate an entire data set all the way up to the last transaction logged as committed to transaction level 0. Restoration of a backup can be made to any system capable of supporting the original application. It need not be the same machine, or even the same machine configuration. Location of files can be changed as part of the restoration process.

	==Backup and restore to different hardware==		==Backup and restore to different hardware==
	When an ESENT database is created, the physical [[disk sector]] size is stored with the database. The physical sector size is expected to remain consistent between sessions; otherwise, an error is reported. When a physical drive is cloned or restored from a drive image to a drive that uses a different physical sector size ([[Advanced Format]] Drives), ESENT will report errors.<ref>{{Cite web\|url=https://kb.acronis.com/content/36451\|title=Acronis Products: Applications Build on ESENT Running on Windows Vista, Windows Server 2008 and Windows 7 may not work correctly after restoring or cloning to a drive with different physical sector \| Knowledge Base\|website=kb.acronis.com}}</ref>		When an ESENT database is created, the physical [[disk sector]] size is stored with the database. The physical sector size is expected to remain consistent between sessions; otherwise, an error is reported. When a physical drive is cloned or restored from a drive image to a drive that uses a different physical sector size ([[Advanced Format]] Drives), ESENT will report errors.<ref>{{Cite web\|url=https://kb.acronis.com/content/36451\|title=Acronis Products: Applications Build on ESENT Running on Windows Vista, Windows Server 2008 and Windows 7 may not work correctly after restoring or cloning to a drive with different physical sector \| Knowledge Base\|website=kb.acronis.com}}</ref>

	This is a known issue and Microsoft has hot fixes available. For Windows Vista or Windows Server 2008 see KB2470478.<ref>http://support.microsoft.com/kb/2470478</ref> For Windows 7 or Windows Server 2008 R2 see KB982018.<ref>{{Cite web\|url=https://support.microsoft.com/en-us/topic/an-update-that-improves-the-compatibility-of-windows-7-and-windows-server-2008-r2-with-advanced-format-disks-is-available-004a02e4-7812-e14f-9dd7-d5e61c3ee20e\|title=An update that improves the compatibility of Windows 7 and Windows Server 2008 R2 with Advanced Format Disks is available\|website=support.microsoft.com}}</ref>		This is a known issue and Microsoft has hot fixes available. For Windows Vista or Windows Server 2008 see KB2470478.<ref>http://support.microsoft.com/kb/2470478 {{Dead link\|date=February 2022}}</ref> For Windows 7 or Windows Server 2008 R2 see KB982018.<ref>{{Cite web\|url=https://support.microsoft.com/en-us/topic/an-update-that-improves-the-compatibility-of-windows-7-and-windows-server-2008-r2-with-advanced-format-disks-is-available-004a02e4-7812-e14f-9dd7-d5e61c3ee20e\|title=An update that improves the compatibility of Windows 7 and Windows Server 2008 R2 with Advanced Format Disks is available\|website=support.microsoft.com}}</ref>

	==History==		==History==
Line 234:		Line 235:
	Cheen Liao, Stephen Hecht, Matthew Bellew, Ian Jose, Edward "Eddie" Gilbert, Kenneth Kin Lum, Balasubramanian Sriram, Jonathan Liem, Andrew Goodsell, Laurion Burchall, Andrei Marinescu, Adam Foxman, Ivan Trindev, Spencer Low and Brett Shirley.		Cheen Liao, Stephen Hecht, Matthew Bellew, Ian Jose, Edward "Eddie" Gilbert, Kenneth Kin Lum, Balasubramanian Sriram, Jonathan Liem, Andrew Goodsell, Laurion Burchall, Andrei Marinescu, Adam Foxman, Ivan Trindev, Spencer Low and Brett Shirley.

	In January of 2021 Microsoft open sourced ESE.<ref>{{cite web\|url=https://petri.com/microsoft-open-source-ese-database \|title=Microsoft Open Sources ESE, the Extensible Storage Engine \|access-date=2021-02-05}}</ref> It was posted to GitHub with the permissive [[MIT License]].		In January 2021 Microsoft open sourced ESE.<ref>{{cite web\|url=https://petri.com/microsoft-open-source-ese-database \|title=Microsoft Open Sources ESE, the Extensible Storage Engine \|access-date=2021-02-05}}</ref> It was posted to GitHub with the permissive [[MIT License]].

	==Comparison to JET Red==		==Comparison to JET Red==

Citation bot: Add: website. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | Linked from User:BrownHairedGirl/Articles_with_bare_links | #UCB_webform_linked 897/2189

2022-02-14T11:40:15Z

Add: website. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | Linked from User:BrownHairedGirl/Articles_with_bare_links | #UCB_webform_linked 897/2189

← Previous revision		Revision as of 11:40, 14 February 2022
Line 225:		Line 225:

	==History==		==History==
	JET Blue was originally developed by Microsoft as a prospective upgrade for the [[Jet Database Engine\|JET Red]] database engine in [[Microsoft Access]], but was never used in this role. Instead, it went on to be used by Exchange Server, Active Directory, [[File Replication Service]] (FRS), Security Configuration Editor, Certificate Services, [[Windows Internet Name Service]] (WINS) and a host of other Microsoft services, applications and Windows components.<ref>{{Cite web\|url=http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/distrib/dsbi_add_ttpn.mspx?mfr=true\|title=Extensible Storage Engine}}</ref> For years, it was a private API used by Microsoft only, but has since become a published API that anyone can use.		JET Blue was originally developed by Microsoft as a prospective upgrade for the [[Jet Database Engine\|JET Red]] database engine in [[Microsoft Access]], but was never used in this role. Instead, it went on to be used by Exchange Server, Active Directory, [[File Replication Service]] (FRS), Security Configuration Editor, Certificate Services, [[Windows Internet Name Service]] (WINS) and a host of other Microsoft services, applications and Windows components.<ref>{{Cite web\|url=http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/distrib/dsbi_add_ttpn.mspx?mfr=true\|title=Extensible Storage Engine\|website=[[Microsoft]]}}</ref> For years, it was a private API used by Microsoft only, but has since become a published API that anyone can use.

	Work began on Data Access Engine (DAE) in March 1989 when Allen Reiter joined Microsoft. Over the next year a team of four developers worked for Allen to largely complete the ISAM. Microsoft already had the BC7 ISAM (JET Red) but began the Data Access Engine (DAE) effort to build a more robust database engine as an entry in the then new client-server architecture realm. In the spring of 1990, BC7 ISAM and DAE teams were joined to become the Joint Engine Technology (JET) effort; responsible for producing two engines a v1 ([[Jet Database Engine\|JET Red]]) and a v2 (JET Blue) that would conform to the same API specification (JET API). DAE became JET Blue for the color of the flag of Israel. BC7 ISAM became JET Red for the color of the flag of Russia. While JET Blue and JET Red were written to the same API specification, they shared no ISAM code whatsoever. They did both support a common query processor, QJET, which later together with the BC7 ISAM became synonymous with JET Red.		Work began on Data Access Engine (DAE) in March 1989 when Allen Reiter joined Microsoft. Over the next year a team of four developers worked for Allen to largely complete the ISAM. Microsoft already had the BC7 ISAM (JET Red) but began the Data Access Engine (DAE) effort to build a more robust database engine as an entry in the then new client-server architecture realm. In the spring of 1990, BC7 ISAM and DAE teams were joined to become the Joint Engine Technology (JET) effort; responsible for producing two engines a v1 ([[Jet Database Engine\|JET Red]]) and a v2 (JET Blue) that would conform to the same API specification (JET API). DAE became JET Blue for the color of the flag of Israel. BC7 ISAM became JET Red for the color of the flag of Russia. While JET Blue and JET Red were written to the same API specification, they shared no ISAM code whatsoever. They did both support a common query processor, QJET, which later together with the BC7 ISAM became synonymous with JET Red.

Uzume: Jet Database Engine

2021-12-27T02:19:11Z

Jet Database Engine

Show changes

Uzume: /* top */ Access Database Engine dab

2021-12-26T01:29:04Z

top: Access Database Engine dab

← Previous revision		Revision as of 01:29, 26 December 2021
Line 1:		Line 1:
	{{For\|'''JET Red''' storage engine of [[Microsoft Access]]\|~~Microsoft Jet~~ Database Engine}}		{{For\|'''JET Red''' storage engine of [[Microsoft Access]]\|Access Database Engine}}
	{{inline\|date=February 2021}}		{{inline\|date=February 2021}}
	{{Infobox software		{{Infobox software
Line 15:		Line 15:
	\| latest preview version =		\| latest preview version =
	\| latest preview date =		\| latest preview date =
	\| repo = {{URL\|https://github.com/microsoft/Extensible-Storage-Engine}}
	\| programming language = [[C++]]		\| programming language = [[C++]]
	\| operating system = [[Microsoft Windows]]		\| operating system = [[Microsoft Windows]]

← Previous revision		Revision as of 01:06, 5 March 2025
Line 1:		Line 1:
			{{Short description\|Microsoft embedded database engine}}
	{{For\|'''JET Red''' storage engine of [[Microsoft Access]]\|Access Database Engine}}		{{For\|'''JET Red''' storage engine of [[Microsoft Access]]\|Access Database Engine}}
	{{more footnotes\|date=February 2021}}		{{more footnotes\|date=February 2021}}