What is a Microsoft Jet Database and is it suitable for a small application with sensitive information?

I am planning a new ASP.NET project that will be a product that is installed by technical staff who work in different companies. The program will store confidential information that should not be easily accessible to staff, including technical staff.

I need to balance light, straight-line installation with safety and reliability. The default db seems to be MS SQL for C # developers these days, but some of the companies that will be installing this may not have their own SQL server, so someone suggested I use a Microsoft JET database. What is MS JET - is it a product or a technology? The database will be pretty simple with only a few tables, I don't need all the power of SQL, is there any db that doesn't require installation like SQL (i.e. a simple file)?

Thanks J

+2


source to share


7 replies


The preferred way of running a serverless database in .NET these days is using SQL Server Compact - it has the database in the -file and doesn't require any backend processes - all the code runs directly inside your process as a simple DLL.



Using Jet as primary storage is not recommended. It used to be a sensible default choice, but now Jet is exclusively owned by the Microsoft Access team and will continue to evolve and adapt for its own purposes.

+8


source


Looks like SQLite might be a good option, very easy to install. You can implement security independent of your db platform through authentication, encryption, etc.



+3


source


I'm a big fan of Access and Jet / ACE, but for sensitive data, Jet / ACE is not a good choice as it can't really be secure the way a server database server can work.

However, many people who think their data is sensitive and need the highest level of security technology are simply kidding themselves.

Security is almost always a human issue, as it is a technology issue, and even with the most secure technology, you still need to trust people to give them access to the data they need to do their job. Your database may be completely locked, but if you can trust your system administrator, you are not protected at all.

Jet / ACE can be reasonably secure for a particular application.

And in terms of cost-benefit ratio, it might be the best choice, considering everything.

But since the original question was framed and didn't know anything about the application, I would definitely recommend not using Jet / ACE.

+2


source


The default mechanism for an MS Access application is known by the generic term "Engine Database Engine".

'Jet' refers specifically to versions of the database access engine prior to Access2007. For what it is important, for Access2007, the version-specific option is "ACE".

I will not advise whether the Access Database Engine is appropriate, other than to say that it is good for small standalone applications with very few users.

0


source


Microsoft JET ODBC drivers are used when connecting to a Microsoft Access database (* .mdb). This is one way to support an embedded database.

I would recommend against using Access in favor of something like SQLLite or SQL Server Compact Edition . By using either of these, you will get more robust SQL syntax support and more than likely improve performance.

0


source


Microsoft JET database is a technology used by Microsoft Access. I would highly recommend using something like SQL Server Express (free download from Microsoft - http://www.microsoft.com/express/sql/default.aspx ). SQL Server Express has several limitations (maximum number of concurrent connections, 2GB database size, etc.), but I think it is much better than JET. Also, if your application is getting a lot of value and needs a "serious" database, you can always upgrade to the regular version of SQL Server.

0


source


I would stay away from Jet. It has performance issues compared to almost any other database. Plus, it uses a non-standard version of SQL (Jet-SQL), which means it's hard for you to port your application to another database once you decide to stop hammering yourself in the head. It is true that even T-SQL is not universal across databases, but Jet-SQL is really different.

Plus it's Access, which means your peers will laugh at you every time you mention it. This may not be entirely fair, but it will happen.

0


source







All Articles