What I have is one SQL server in NV and the other in CA. The NV server is
the one that billing is being done from.
The problem is when the connection in NV goes down (Sprint) the RadiusNT in
CA can't get to the SQL for authentication. The SQL server in CA has a copy
of the DB but I don't want to do a full transfer every night.
> I would not recommend doing a nightly transfer unless you're short on
> bandwidth, or don't care about concurrency control. A transactional
> replication would be much better for this. I'm doing it now, and it's
> actually very light on the CPU and Bandwidth.
For more information about this list (including removal) go to: