- Joined
- Jun 27, 2012
What's up everyone? My trainer at the gym is looking to go and make his own gym. He is in need of a database and network system to run the gym. This setup would be responsible for keeping and updating a list of things such as gym memberships, members names, addresses, paid or unpaid subscription, etc.
The catch is he wants 3 computers to be able to do this from. So I've been rolling ideas around in my head. So far I've come up with the following.
1 central server running windows server 2008 r2. File server and network printer roles installed. Administration account access only, password protected of course
3 other computers. Probably amd a series itx builds. I was thinking of having these itx builds be very light on the hardware. Dual cores, 4gb ram, 120gb ssds so everything is snappy. All running windows 7.
I would have the 3 computers all have the information from the server be mapped as a network drive using 3 separate accounts and passwords. All with limited rights amd only specific folders for them to access.
As for the database itself, keeping the needs he has in mind I mentioned earlier, would several excel spreadsheets imported into an access database be sufficient? All changes made to the access file from any 1 of the "terminals" would auto update for the other terminals right? Unless I'm thinking about this wrong.
As for how they're connected, I am leaning towards hardwire, but if that's not possible, a really good wireless router with a 3rd party firewall and turning off wifi broadcast.
The server would have the primary drive being auto backed up to a backup drive.
To give some insight into my expertise, I'm definitely not a beginner when it comes to building a pc, and I know enough to hook up my own file server in my house using a hardwire setup and 5 port switch. I would have to look into the excel/access route some more, but am I wrong to think this would this simple?
Input is greatly appreciated.
The catch is he wants 3 computers to be able to do this from. So I've been rolling ideas around in my head. So far I've come up with the following.
1 central server running windows server 2008 r2. File server and network printer roles installed. Administration account access only, password protected of course
3 other computers. Probably amd a series itx builds. I was thinking of having these itx builds be very light on the hardware. Dual cores, 4gb ram, 120gb ssds so everything is snappy. All running windows 7.
I would have the 3 computers all have the information from the server be mapped as a network drive using 3 separate accounts and passwords. All with limited rights amd only specific folders for them to access.
As for the database itself, keeping the needs he has in mind I mentioned earlier, would several excel spreadsheets imported into an access database be sufficient? All changes made to the access file from any 1 of the "terminals" would auto update for the other terminals right? Unless I'm thinking about this wrong.
As for how they're connected, I am leaning towards hardwire, but if that's not possible, a really good wireless router with a 3rd party firewall and turning off wifi broadcast.
The server would have the primary drive being auto backed up to a backup drive.
To give some insight into my expertise, I'm definitely not a beginner when it comes to building a pc, and I know enough to hook up my own file server in my house using a hardwire setup and 5 port switch. I would have to look into the excel/access route some more, but am I wrong to think this would this simple?
Input is greatly appreciated.