Hello,
I have just noticed that this code is not aligned with the version of esent.dll shipped with windows 11.
At least some files created with the version of esent.dll shipped with Windows 11 cannot be opened with this code.
Is there a plan to align the code here with what ships with Windows?
Thanks,
Claudio

ESE is a complicated code base, but not all bugs or features in it are as complicated. Give a list of small features, or simple bugs that the community may want to develop.

Up-vote this issue if it is of interest.

I have seen previous ESE database reader applications do some scary things in terms of their settings and behavior in ways that could be very disruptive or even create inconsistent DBs that the native application for that DB may not be able to recover from.

This work item respresents creating some boilerplate JET API start code, that would attach a clean database read only, and with no logging, and thus have no affect on the persisted ESE files. Such that the DB is not left inconsistent if the application should crash, nor have the possibility of creating a logical inconsistency for the native application that uses this DB.

Up-vote this issue if it is of interest.

Happy to see microsoft opensource this good database engine.

Hope you guys continue opensource more and more project.

Very good move.
To open .for all developers.

We all can got benefit on your opensource codebase.

Thank you

When will the "Continuous Commit Push" begin?

How to use debug esent.dll for easier debugging of your ESE application ... this would cover our "Error Trap", some registry parameters that are only used in debug, common Assert()s that might help you, etc. This really could only be helpful for developing your own private ESE applications (i.e. it would not help you understand or debug any other ESE-based windows services, such a AD or Exchange Server).

Up-vote this issue if it is of interest.

There are many ESE-based services (Active Directory, Exchange Server, or even Windows client), and they report windows performance counters (that can be viewed through perfmon.exe) - but it might be helpful to glean more context from the code context(s) where those performance counters are updated.

Up-vote this issue if it is of interest.

There are many ESE-based services (Active Directory, Exchange Server, or even Windows client), and for the Application Log events that they report - it might be helpful to glean more context from the code context(s) where it can be reported from.

Up-vote this issue if it is of interest.

ostls in _TLS is a struct not a point so sizeof(_TLS) already contains sizeof(OSTLS). Why _TLS's instance ptls need duplicate OSTLS's memory? I tried to delete sizeof(OSTLS) and run the sample. Everything seems good.

Debugging your ESE application (or even - ESE-based Windows services) with the ESE debugger extension.

This could go on and on ... but to start we at least need to cover the basics of how to use windbg.exe/cdb.exe, what the ESE debugger extension is, and a few basic ESE debugger commands.

Then later we would cover more advanced ESE debugger commands, that accomplish specific purposes. You can inspect a great many things in a process with our debugger extensions - how our memory is being utilized, finding the longest running transaction, seeing if we have a hung IO operation (disk not returning), and many many more.

Feel free to respond to the issue to:

• Suggest specific debug scenarios,
• Or questions you might have of an active process.

This issue will be closed when basics and a few extra scenarios are documented, and I will spin anything left in comments into new issues.

Up-vote this issue if it is of interest.