Best way to store database file on a NAS and run the server on a computer

databaseMySQLnetwork-attached-storagenetworkingnosql

I have a txt file more than 250go
I want to create a database with that and access it by a python program that I'll be coding.

I have a NAS server on my local network ( 1gbit network )
And I would want to :
Store the database on the NAS
Run the server on my computer

Run my python program on a distant computer, this program will ask my computer ( that is run as the server ) data that are stored on my NAS

So questions :
its possible ?
its worse ?
And what is the best technology to do that ? SQL ? NoSql ? ect.

I'm a beginner on computing. Thanks !

Best Answer

Some notes:

NAS is fine for a database. There could be some surprises in performance, etc.
NAS is mostly indistinguishable from the disk on your computer.
Depending on a lot of details that you have not provided, the 260GB of data may expand to 800GB when it is put into the database. That is, it might all fit in 1TB. Or it might not.
(I do not know what it takes to configure the NAS; quite possibly that is "automatic" and will simply show up when you use "file manager" or "mount". You have not even mentioned what OS you are using.)
250GB may take days to copy into the database. If at all possible, use a tool, not simplistic python code. (I have answered questions about people who have a python loop: read a line, INSERT into database, loop. That's not efficient.)

Related Solutions

Ftp – NAS – Do i need to Run Samba

I would enable SMB. If the data doesn't need any access control and you don't have a domain set up (which I doubt you do for only 5 machines) you can create a logon script and put it in the user's startup folder to map in on startup. If you wanted to map the drive as X: every time a user logs in you would do it like this:

net use x: \\RemoteDeviceName\ShareName

This is assuming that there is no access control on the device.

Mysql – the best option to set up a quick and easy-to-manage database for the small office

It's a small office. That sounds like datasheet import / report generation. I'd say don't bother with concurrency problems, high availability and such, but with how to integrate existent base. I don't think you need all the available SQL power more than you need good integration/migration tools.

My 2 cents is: go and see if the features of OpenBase meet your current requirements. If so, go with it. If you really know you need the SQL power of mysql or postgresql you can start using OpenBase as a frontend with either one as a backend. As far as I can tell, mysql/postgresql aren't exactly seen/used as office solutions so in your case you may not get all the help you need when asking for it on the community forums. I advise against using these directly for implementing office solutions. On the other hand I vouch for OpenBase to be used at least as a frontend, if not together with its "native" sql backend, hsqldb. You will be able to easily integrate current solutions and/or migrate existent data. OpenBaseis a good alternative to microsoft office solutions so I won't bother talking about the latter here.

Best Answer

Related Solutions

Ftp – NAS – Do i need to Run Samba

Mysql – the best option to set up a quick and easy-to-manage database for the small office

Related Topic