The right back-end database
One of the apps that I am researching as a possible project, will be a database application that allows clients to access the data on a hosted platform. We will initially be using a C# Desktop front-end, but I could really do with some additional advice as to the back-end. We will be seeking professional guidance on this - but I would really like a little heads-up first.
The type of application means that each client could have multiple, individual databases of between 1k and 10k records (average), which although are initially based on a standard template are slightly altered for each project (there could be in excess of 100 projects (although not all will be used at the same time)). Also, there could be up to 50 users (working on the various projects). In addition to this, the aim will be to get multiple clients....who may need the same type of setup.
So my question is - would you initially have one instance of a server such as Microsoft SQL / PostgreSQL (other suggestions greatly appreciated) for all of the clients, or would you need to set-up a separate instance/server for each one?
As mentioned, we will be seeking help on this - I'd just also like some EE help first.
Thank you.
The type of application means that each client could have multiple, individual databases of between 1k and 10k records (average), which although are initially based on a standard template are slightly altered for each project (there could be in excess of 100 projects (although not all will be used at the same time)). Also, there could be up to 50 users (working on the various projects). In addition to this, the aim will be to get multiple clients....who may need the same type of setup.
So my question is - would you initially have one instance of a server such as Microsoft SQL / PostgreSQL (other suggestions greatly appreciated) for all of the clients, or would you need to set-up a separate instance/server for each one?
As mentioned, we will be seeking help on this - I'd just also like some EE help first.
Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
![Avatar of Alex [***Alex140181***]](https://filedb.experts-exchange.com/files/public/2022/11/13/8257e912-ee3c-4a93-9df0-fe9a8a1515cf.jpeg){kind=small}
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
MySQL is free up to a certain level - And yes you are correct a TABLE contains the records (you win the prize).
MySQL is free for your use, like development, but you will pay a extremely low fee if you use it in a production environment for the purpose to make money.
Is this post still open? There is no point in arguing about fees here. I could point out you can use the open source implementation of MySQL, called mariaDB with no costs at all if you want to. Most people and companies pay gladly the fees because of the support they have; otherwise MS Sql server would be a dead product.
ASKER
All great advice - very much appreciated.
Thank you.
Thank you.
I am confused by your statement here:
"The type of application means that each client could have multiple, individual databases of between 1k and 10k records (average)..."
I a database doesn't have "records", a table has. And a database can have multiple tables.
Anyway, any of the recommended platforms would work so you should look to free platforms.