What is the difference between mysql and access

Get started with 80GB free. The modern database for enterprise applications. Build fast. Scale Big. Save more. Sign in. By signing up, you agree to our Terms of Use and Privacy Policy. Enter the email address associated with your account. We'll send a magic link to your inbox. Email Address. All Sign in options.

Enter a Email Address. Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox. Newsletter Topics Select minimum 1 topic. Patrick Harren Posted June 10, 0 Comments. Mike Walker Posted June 10, 0 Comments.

Anonymous Posted June 11, 0 Comments. I have been asked to assist on a new project. The overall purpose is to organize a large number of recordings so that they can be searched. I have an enormous music library but my songs are several hours long. I need to include things like time, date and location of the recording. I don't have a problem with the general database design.

I have two primary questions:. Much more important is how you store the audio. While you could technically use a blob type column, it's really not ideal to be storing audio files which are "several hours long" in a database row. Instead consider storing the audio files in an object store hosted options include backblaze b2 or aws s3 and persisting the key which references that object in your database column.

Hi Erin, Chances are you would want to store the files in a blob type. Can you explain a little more about your need to store the files in the database? I may be more effective to store the files on a file system or something like S3. To answer your qustion based on what you are descibing I would slighly lean towards PostgreSQL since it tends to be a little better on the data warehousing side.

Hi Erin! First of all, you'd probably want to go with a managed service. If you are on AWS, thet have different offerings for database services. Standard RDS vs. Aurora would be my preferred choice given the benefits it offers, storage optimizations it comes with Such managed services easily allow you to apply new security patches and upgrades, set up backups, replication Doing this on your own would either be risky, inefficient, or you might just give up.

Other database services exist, I'd recommend you also explore Dynamo DB. Regardless, you'd certainly only keep high-level records, meta data in Database, and the actual files, most-likely in S3, so that you can keep all options open in terms of what you'll do with them. Hey Erin! I would recommend checking out Directus before you start work on building your own app for them.

I just stumbled upon it, and so far extremely happy with the functionalities. If your client is just looking for a simple web app for their own data, then Directus may be a great option. It offers "database mirroring", so that you can connect it to any database and set up functionality around it!

Hi everyone! I am a high school student, starting a massive project. I'm building a system for a boarding school to be better connected to their students and be more efficient with information. In the meantime, I am developing a website and an android app.

What's the best datastore I can use? I need to be able to access student data on the app from the main database and send push notifications. Also feed updates. What's the best approach? What's the best tool I can use to deploy the website and the database?

One for testing and prototyping, and an official one Thanks in advance!!!! Firebase has Android, iOS, and Web SDKs; and a console where you can develop, manage, and monitor all the data and analytics from one place. Firebase real-time database is good for online presence and instant feed updates, while Firebase Firestone is good for user profile and other relational data records.

Firebase has a UI SDK which makes it easy to interface with the resources in the project, and with tons of tutorials and starter projects it should be easy to quickly have a decent prototype to iterate upon. Since you said Massive, use their pricing calculator to figure if your expected scale will be covered by the free quota or if you go for the pay-as-you-go that the price is reasonable for your project.

It sounds like a server-client relationship central database and while SQLite is probably the simplest, note that its performance is probably the worst of the top 20 or so choices you have. It is different from Firebase and MySQL and most other databases in that it is embedded in the product, although it could be embedded in your server itself.

But architecturally, they are in the same category as MySQL, a separate db server that your application server would get its data from. Firebase is different yet again, in that it is a service that is already hosted by a company, providing many integrated features such as authentication and storage of user account info. However it does take care of many of the concerns with running a server, such as performance, scalability and management.

There are some negatives that you should be aware of though: any investment of time and coding with Firebase is pretty much non-portable, in that you are stuck with Firebase going forward.

If you needed to switch to a different service, not only would it be a different API, but it would be a different architecture and much of your coding would need to be discarded. Second, it's owned and run by Google now, so you have a large corporation backing it, but that also means they could decide to discontinue it without any real effect on the Google bottom line. Also some folks would have concerns with storing data on Google servers.

That said, I think if you are aware of these in advance, and especially if you are a high school student, that Firebase is a fairly easy winner here. The server is already set up for you, the documentation is very complete and rich, with lots of examples, and Google is not going away.

The main concern would be if it really is massive, there could be a rising cost to the service. I suspect though that it is not massive, even if everyone in a school used it.

The number of concurrent connections would not be huge probably not even into the hundreds, even if there are thousands of users. I'd go with Firebase even though you will need to learn their API, because you'll need to learn something one way or another. SQLite is a bit of a toy database, and MySQL is a real one but you or someone would need to manage that server on top of needing to develop the server and client app.

With Firebase, much of the server already exists, including a professionally hosted database. There are tons of high-level features provided and initial cost is somewhere between very low and zero. Part of this is dependent on what language you want to write this in. Javascript for a cross-platform client app I'd use Vue. ObjectDB is very very fast and can be separated out into a scalable server if this became truly massive.

But you would probably never need to go that far. All of this is a lot of work. I hope this isn't for something like an assignment. It is in the order of 6 months of work if you know what you're doing, all year if you're learning as you go. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Learn more. MySQL vs. Microsoft Access [closed] Ask Question. Asked 7 years, 7 months ago. Active 7 years, 7 months ago. Viewed 71k times. Improve this question. You might consider re-posting this topic as multiple questions.

This question needs additional information such as the front-end to be used for the database.