Multi-User SQL Server Question

I have a sql server 2012 web database on my server that I use for my race management company.  When we go out to time races I put a copy of the *.mdf and *.ldf files in dropbox and then each timer (if we have more than one crew out at a given time) pulls down those files (meaning each crew starts with the same data) and uses that to time their race on their local machine.  As they time the race the data for their event is uploaded to the server programatically.  Other than writing a script to download just the data each crew needs for their event, is there a better way to do this rather than sticking the *.mdf & *.ldf files in dropbox and copying them to our local machines?  What sometimes happens is the local machine takes a couple of tries to access the data and sometimes it requires a re-start.

I am guessing this is a pretty low-brow approach and am looking for a more seamless approach if it is within my cerebral capabilities.

We run sql server 2012 express on our local machines.  My timing program was written with vb6.
Bob SchneiderCo-OwnerAsked:
Who is Participating?
Why not put the data in a local Access database, with a VBA button that uploads the data to the server? That would let them use the data locally, which should get rid of the need to restart. Once they reconnect to the server, an Upload button in Access pushes the data up to the server.
A database IS meant to be central. Each crew working on a shared database - each crew accessing the central database server - will work on tha same data. I don't understand the reason you'd have to push/synchronize database file across computers....
Bob SchneiderCo-OwnerAuthor Commented:
The reason we have to work locally is because we can't always depend on internet connectivity in the field.  So working locally by starting with a copy of the db on each local machine is how we have solved that.  So, at some point when we have a good connection (before leaving for the race) we have to ensure that we have up-to-date data.  Is there a better way to do that?

I had never thought of putting the data in a local Access db and, at this point, that would take quite a bit of re-writing code to do that.  How much of an advantage would that be over what we are doing now?
It's what Replication is build for :

You can replicate to SQL Express but read-only, the local modifications won't be uploaded to the master. So, you'll need standard edition on local workstations...
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.