Microsoft's Extensible Storage Engine (JET Blue) source code arrives on GitHub – sadly comments not included Microsoft has made the source code for its Extensible Storage Engine (aka JET Blue) available on GitHub. The Extensible Storage Engine (ESE) is an advanced indexed and sequential access method (ISAM) storage technology and has been a fixture in Windows for more than a quarter of a century. It first appeared in Windows NT 3.51 …
To me "is for use in applications that require fast and/or light structured data storage, where raw file access or the registry does not support the application's indexing or data size requirements." is a good description of sqlite.
Any comment from people working with this kind of tool ?
Any comment from people working with this kind of tool ? ..... sw guy
Yes. Although not essential, it is extremely convenient for both stealthy security and safe speedy deployment of Networks InterNetworking JOINT* Applications. … NINJApps
* JOINT ..... Joint Operations Internetworking Novel Technologies
And no matter how deep one may delve and/or attempt to cajole, one will never hear or read a great a deal about such things from the likes of an almighty Microsoft, because of the rather sensitive and strategically important nature of the advantages delivered in advanced fields of its operations in IT and AI Quantum Communications Systems.
Spilling some of those crown jewel gems would cost one more than just trillions whenever it guarantees one losing any future war invented or even contemplated as a necessary current evil for defence of present distressed and bankrupt of novel proprietary intellectual property registering realms.
I use ESE a lot to create mobile applications and right now am writing a WinRT/UWP component library DLL to allow interfacing between UWP apps and ESE. As a database, it's fast, super reliable, ACID, and free given it ships with every Windows release (ESENT.DLL). It's best for fixed database designs without the need for an ad-hoc query capability since there's no query language facility. Essentially is a very good ISAM database engine with some really cool features like "tagged" columns that take up no room if left empty. I write in C++, but there's a well-documented C# API as well.
ESE is fundamental to Active Directory and a host of other Microsoft built-in functions, so it's well maintained and continuously tweaked. If you have a fixed schema with a manageable number of tables and few complex joins, it's a viable alternative to MySQL, SQLIte, Mongo, and other database engines.
And a shout-out to Microsoft for posting the source. I've been waiting for *years* to get a better insight into the code behind the API.
Right now? No. ESE isn't a relational system, but ISAM. I've never heard of anyone bolting on ESE support to Access. Unfortunately, you have to pay the price in time/effort if you want to reap the benefits of ESE. The only two language projections that I know are supported by ESE are C/C++ and C#. There might be a COM-based set of ESE components out there callable from Visual Basic, but I haven't seen any. That's why I'm writing my own (well, actually WinRT). I'm going to look like an idiot if MS introduces something similar in the near future. ;^)
Stripping comments is antisocial at best. Oh, yes... Microsoft.
Corporations dicking with comments have been a sore spot with me, ever since <now dead> company stripped out a programmer's dedication to his parents. Many 1000s lines of system-level code, when his side project program became a money-generating product, they made it look commercial, and stripped out some comments to be "on the safe side". Reducing the appearance of quality to _their_ usual level was not a good move.
If you had been watching Dave's garage regularly you would realize just _why_ the comments were stripped (albeit temporarily) and why your post looks foolish.
That said, if the code is well written, with meaningful function names, comments are not all that important. Those who use JET are better off now than they were only a week ago.
Third party tools to look at Active Directory / WINS / Certificate Authority databases?
If you can understand the data structure, you can load the data directly from the DB without having to use the Microsoft libraries. This would be required if you wanted an implementation to load the Active Directory database under SAMBA for example?
Maybe a backup product no longer needs to use other APIs to get into these databases and do item level restores? This would absolutely be required if you're running a cross platform backup product like commvault...
"Jet Blue" and JOINT in the same thread seem almost too much of a coincidence.
Jet Blue is a long established brand of sealing compound for pipe threads and gas fittings!
Example (not an advert, just the first link with a picture that I found on google).
http://sespipeline.co.uk/Jet-blue-jointing-compound-steam-water-oil-gas-bss-wolseley
There again, Microsoft have always seemed to make a habit of leaving security holes in applications - sealing compound may be a good idea!
Nowt wrong with JET.
Nowt wrong with Access either. Have used it with great success for quite complex jobs.
Unless, of course, you develop either of them them into Humungo_Apps more suited for mainframe D/B tech.
If you go where No Man Was Meant To Go expect to see the error conditions No Man Was Meant To See.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
