upload online database SQL

[John Lerry]

Hi, I need your opinion.
Until now I have always created my MySQL database to make them read locally by applications created by me, but now I will try to upload my database so that they can use the database on any machine that starts the application from me created.
Do you know if I can do this?

[Jesper de Jong]

John Lerry wrote:Do you know if I can do this?

We don't know if you can do this, because we don't know your skills and knowledge.

Maybe you wanted to ask a different question, for example if this is a good idea? It depends on what application this is. Do you want to make the database accessible via the Internet? Then you should realize that anyone in principle has access to your database server. Normally people don't directly make databases accessible on the Internet, there's usually at least a web service in between.

If it's an application that runs on a local company network, then you might make the database directly accessible on the local network.

[John Lerry]

Actually I have not explained the problem well.
I would like to create an application that retrieves information from a database (written in SQL) but I would avoid having the database on my pc because I see a solution too trivial.
I'd like to know what is the best solution for to have a database but not locally

[Tapas Chand]

May be you can go for this.
SYSTEM 1: Application
SYSTEM 2: Database
SYSTEM 1 and SYSTEM 2 are connected by LAN.

[Tim Holloway]

MySQL is a database server-based system (unlike something like Microsoft Access, where the data access is direct). That means that any machine anywhere in the world can access the database as long as there's a tcp/ip route between the client machine and the MySQL server machine and that no firewalls block the channel.

However you generally don't want to work that way. The infamous "SQL Slammer" attack that crashes Microsoft Windows machines all over the world - including bank cash dispensers - took advantage of that sort of 2-tier approach to data access. Even 15 years later I repel multiple SQL Slammer attacks every day on my servers, and I don't even run Windows.

So normally, you'd have the database client application (which might be a web server application) and the database server both within the same LAN, if not on the same machine.

If you want a completely isolated client system that requires no external MySQL server, you can do that. It's quite easy to export a MySQL database and ship it over to some other MySQL server machine - which is more than I can say about certain major-name commercial DBMS's which are more limited.

However, the drawback there is that you must have a mechanism that will install and configure the MySQL server DBMS server product on the local machine. And since the database is entirely contained within that machine, no other machine can alter or reference any of the data within that database.

[John Lerry]

Tim Holloway wrote:
If you want a completely isolated client system that requires no external MySQL server, you can do that. It's quite easy to export a MySQL database and ship it over to some other MySQL server machine - which is more than I can say about certain major-name commercial DBMS's which are more limited.

so if I wanted to make the database independent of my pc I should upload the database on an external host, is it right?