MySQL was free but it turns out this is not always the case. MySQL isn't (necessarily) free anymore unless your client application is GPL. There are also some other arguments made here that do NOT apply to MySQL. It runs on a free OS with free clients, so it is free. You are forgetting MySQL is essentially free for Linux boxes. Not sure how long this has been available, but SQL Server Express has free management tools that can be downloaded and used for free. On the subject of pricing: If an app is distributed with SQL Server Express, can Enterprise Manager be included? If not, then how much must one pay? - ?CFK Still, you're probably getting more revenue, right? ) Rob Spencer Add another CPU or a backup server (or a test server) and you need more licences. For example, you will need an unlimited license if running a web server/service as you don't know how many end-users you will have. You need to check your usage against the license you intend to use. Last I checked an unlimited seat, single CPU license was less than $5,000 - Randy Jean ![]() ![]() I tell people: SQL Server Express (free) for small to medium shops or $20,000 for unlimited. Mainly, though, it's a big design issue: real-time, or 'refreshing'?īesides, I've always seen a DBF solution as more in-line with smaller businesses, or those who don't really need to centralize their data. DBFs are perfect for those clients whose needs wants merit having access to all the data, all the time. Using SQL is great if your clients can handle only getting some of the data. Just an FYI - There is an excellent quick-fill textbox control that uses SPT that is described in Creating Visual FoxPro Applications with Visual Fo圎xpress. SQL can be a lot more than just looking at the data, it can definitely require changes to the overall presentation design, too. always having to select from a dropdown or a list form. For fast data entry, you need to have codes that the user can enter vs. The users have grown accustomed to IntelliSense type entry for these fields. We have an app now that was designed with all surrogate keys and no user entered keys (candidate keys) so this will be a problem. If they are of relatively large size and you are going to use SQL, uh-oh! Time to change to list forms, etc. ![]() These are real fast when coming out of DBF's even if you are using views. Randy JeanĪnother common UI feature in most non client/server desktop apps (that is also hard sell to change) is that of pre-populated dropdown lists for lookups. For instance, if users are used to being able to fast forward and rewind to the top and bottom of a giant table and scroll every record in between without requesting record sets using criteria, this could be a problem for making the SQL argument. Scott FineganĪlso, don't forget that it may require user interface and workflow changes to a legacy app to make the switch. The choice is a lifestyle change IMO, not a choice of which is better, unless security is the issue. DBFs involves the developer, or Backup Open Files, SQL involves responsibility shifting to the IS backup people. Live backups: available for both DBFs and SQL.Scalability: both may be scaled, SQL is a purchased black box solution with many users, and much testing already done.Easy to develop: many of the same development tools may be used for DBFs and SQL.Speed: depends on the developer, the software, the access method used, the network load, server load, and the hardware.These range from pre-compiled programs such as VFP, VdB, to Code Base C libraries.Ī SQL database, which uses a software engine that _always_ sits between the data and the client (the actual structure is hidden from the developer). I disagree with most of the supposed advantages because they leave too much out of the equation.Ī DBF (a file with repeating sequences of data): There are at least half a dozen data access engines available to get at the data in a DBF. ![]() Win9x,Windows CE) - This only applies to MS SQL - I would say the rest ( My Sql, Informix, Oracle…) run on a variety of platforms.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |