I would definitely run wired instead of wireless. With wireless you will likely have much higher latency to the server, which is bad news with SQL. You can also get interference from wireless phones on the 2.4GHz range and things like microwaves, other wifi hotspots in the area, and even overhead aircraft. Sync has issues, as has been explained in other threads. Bert's suggestion is always to try what you are thinking in a virtual machine first, and many times and different ways, to see what will work for you. Syncing in certain ways can cause loss of data such as patient records.
Here is a post from another forum which I thought would be applicable
'physicall it takes a signal longer to go through air than it does through a cable'
Actually, this isn't true. The speed of electromagnetic propogation through a medium can be expressed in terms relative to the speed of light in a vacuum by the formula 1/sqrt(Er) *c, where Er is the dielectric constant of the medium.
The dielectric constant of air is around 1.05, whereas the dielectric constant of copper in a twisted pair of 24 gauge wire is around 2.5, resulting in the speed of propogation through air faster than through copper.
Of course, you could consider effects such as relection in a non line-of-site environment to impact the amount of time it takes for a signal to move from point A to point B nonlinearly.
But the main reason why wireless networking has a higher latency than wired is the amount of digital signal processing involved in decoding the signal. A wireless receiver must do many more complex mathematical computations to extract a spread-spectrum wireless signal from ambient noise than its wired counterpart. Plus on top of that, if you run WEP encryption, the encoding/decoding adds to computation time. As well, wireless networks operate on a shared segment, and the time it takes to detect and recover from collisions can be greater than on a segmented store-and-forward ethernet network.
Link to that post -
http://www.hardforum.com/archive/index.php/t-893589.html
