Anything but SQL Server a non-starter for both me and corporate.

I seem to remember the license has to do with simultaneous connections so I was wondering if 50 offices which never connected more than 10 at a time need more than ten licenses.

This sounds like a job for Craig ! <s>


>>Assume a server in the corporate office with Sql Server 2008.
>>
>>Offices all over the country, connected to corporate on a VPN.
>>
>>VFP program, currently with data in Fox, which has data to be sent to corporate once a day. Framework handles remote views very well, very comfortable doing them. Framework has a connection manager, so each office will open only one connection to server.
>>
>>How would I want to work the licensing on the SQL Server. Offices can stagger times for update, full update procedure should take no more than 5-10 minues. No need for a full-time connection. 100 or more field offices.
>>
>>Future design involves converting backend in the field to local SQL Express 2008 databases. What would be my options in that case for connecting to and updating to and from corporate server using SQL Server services?
>
>One possibility would be to install a FOSS DB server like PostgreSQL or MySQL at corporate, and have the field offices talk to that. No licensing issues whatsoever.
>
>You would then need a process at corporate that periodically queried the FOSS DB, looking for new updates to move across to the central SQL Server 2008 database.