Need to set up DB with API, considering SQL, need your expert advice
 

basically, we need to have a database where people can drop of files through an API into our system.

so primarily we need a database/database server where people can drop of files through an API. We then need to have to be able to access this data at some point. secondly, we eventually want to have a secure public interface where people can run reports. but this is not a priority

as i have some experience(years ago) with managing SQL database through MS access, i think that basically, it will take the following steps:

get a Windows SQL database server
hire somebody to set up the database/API on it
once its working, use MS Access to pull the data that was put in through the API

obviously, im new at this will the above work, what do i need to be careful with? any advice would be appreciated

It would be helpful to know what the whole setup is... why are people dropping files through an api to your server? are they backing up files? uploading content they created?

ahh, thanks for the response, they (or their system) is dropping off data that we would process, so its just one-way.

we are setting up a system to process affiliate data and do the payouts for 2 clients, so they are dropping off check name, amount, memo field, etc so we need to store that and maybe 5-6 other data points

bumparoo

I cringed a bit while reading this.

From what you described, can't you just do away with a web interface for those 2 clients rather than an API?

haha @cringe, i think

they are big clients and want an API, mostly i just need a way to have them connect to a web DB and drop off their data. im assuming we can create queries through an MS access connection and get the data we need that way.

obviously im trying to do this at the most cost-effective way possible, but yea, i understand im over my head here and i know there are some brilliant people on this board, so thats why im here