Thank you very much for all your input. Very helpful. I do have currently 3 customers using my VFP with SQL Server. Two of them using SQL Server 2008, I know it is not Express but not sure what exactly. The 3rd one is using SQL Server 2005 Express. Not one of the current customers complained about the speed. But it was my perception that Express will have some bottle necks (I am probably mistaken). The key, of course, is how many users they will have. I sent them an email and hopefully this will determine if Express is an option. I don't mind saving them money if they don't suffer performance.


>Maybe I"m missing something but if performance and the perception of the speed of your program is the issue the hardware will determine that (as well as network config ) but it will be primarily an issue of your program design.
>
>Here's some advice which costs the same as Express.:
>
>Speed isn't going to be noticeably enhanced unless you have HUGE amounts of backend processing to do ( not the most common scenario in first-time VFP / Sql apps ) and multi processors are brought into play requiring stepped up versions of SQL server OR you have many many many *simultaneous* users.
>
>If you have some real heavy lifting to do don't be seduced into the idea that processing in a VFP middle tier is somehow the fastest way to go. Processing on the server can really be your friend for munging a lot of data without moving it over the wire.
>
>Keep clear the distinction between SQL Server the server software and a "Server" i,e. the hardware it runs on.
>
>I think you should get your stuff running on Express to see what kind speed you are looking at, tweak your remote views, SPT or backend SPs for max performance and then decide if a *much* more expensive software solution for server software is warranted.
>
>You can do your own testing on the same box against a Developer Edition - which is Enterprise without the license - server to see if the performance is different. I suspect it won't be.
>
>I've seen some pretty extensive VFP apps ( including a few of mine ) run very well on versions of express.
>
>Depends of course on a lot of factors but remember it is *simultaneous* users and frequency of server hits that is a big factor as well as general network traffic issues that may not even be related to your app or SQL Server.
>
>Also, be sure you understand in your VFP app how to share connections so you are not opening more connections than you need.
>
>VFP can be a very good front end and middle tier for a SQL app but a badly designed one can be a real dog just like any other top and middle tier.
>
>VFP is adequate for the task, but it isn't magical. ( sorry I realize I have just offended some religious beliefs still popular here <s> )
>
>>My concern is that if Express does not perform to their expectations (and going from very fast VFP to SQL could have a perception of slow down) they will blame me. So I would rather they get a real and fast SQL Server. If the price is too much then I can suggest Express with their understanding that they will lose the performance.
>>
>>>Just out of curiosity why don't you wan the express edition - at least to start. Too many concurrant users? Need for mutliple processors? Exceed size limits?
>>>
>>>
>>>>Hi,
>>>>
>>>>A customer wants me to buy SQL Server from Microsoft for them, install it, and use with my VFP application. My questions are:
>>>>1. What version should I suggest (SQL 2012?). Currently my app works with SQL 2005 and SQL 2008 but I never tested on 2012.
>>>>2. What type of license. I don't want to offer them express edition.
>>>>3. What would be the approximate cost of SQL Server?
>>>>4. How much time (hours) should I estimate it would take me to install and set up their SQL Server? (this would be done via remote connection since they are out of state).
>>>>
>>>>TIA for any suggestions.