8 replies
by shellbot
how big will it need to be?
how many users will use?
what language will your program be in?
what technology are you comfy with?
I'm a MS person..if it was me I'd be choosing SQL Server..if your not going to have many users..SQL 2005 Express is free. Interacts well with MS programming languages. Reporting services plugs right in and without a whole lot of effort you've some nice reports to give the boss..
Then again, could always use Access..it does the trick if you don't know much about what your doing.
Give a few more details and we'll see if we can narrow down what you need.
by jaqui
The critical importance of the database design.
You hinted at it in your questions, since they all impact the design. :p
but, will this app ever be called on to handle huge numbers of users? [ such as selling it after completed ]
while access or the fre ms sql server can handle a fair amount, going with the more capable server to start improves scalability.
MySQL is an option, it is very reliable, handles massive concurrent connections, will also handle replication for failover protection schemes, making it competely scalable.
and it will run on windows systems :p
Then you can work with sql itself for the db interaction, making it more portable to other database engines if desired
by shellbot
wasn't thinking "ahead" to selling it..
but i did ask the all important "how many users" :)
ah ya, access or SQL express are only good for a couple concurrent users..so if he's talking what 6-8 initiall users..whats the chance in the next couple of years that will increase..better off to go with SQL or MySQL in the first place then.
Not quite sure what SQL express will take in terms of users..not a whole lot i suspect..
If you want some fairly esoteric financial/statistical functions then teh lower end DBMS' might man you have to write them yourself as opposed to using built in functionality.
Other than that, as Shell says, cost, size, performance, curent inplace technology will have more of an impact than the brand name
by shellbot
by jaqui
50 concurrent connections and the input stream writes access off, without using a multiple server solution.
I would be leery of SQL2005 light as well, though it may be able to handle it.
SQL Server may be out of the budget.
MySQL and Postgresql both run on windows, both compare to SQL Server in performance and scalablility, both available free.
security wise, Postgresql beats MySQL by a bit.
[ financial data, I always put security high on the list of priorities... ok, I always put security high for any confidential data ;) ]
by shellbot
hence why i wasn't posting right away..
access, no good
SQL Express..dunno..don't think it would handle it..oh i'm sure MS says it would (haven't actualy checked) but i wouldn't put much money on it actually coping.
Ya, depends on budget..I'm a SQL person..all i really know other than FoxPro..who wants to go there!! :) (wonder if its still available??)
Used..eh..i'll rephrase that..tried MySQL for a while..eventaully said FTS and moved to SQL server :)
I know nothing at all about Postgres...
so i guess we see what is budget is like..
if its good..wey hey..SQL 2005 and .NET..( i get free cookies nad milk everytime i rope another user into MS..i kinda feel bad..but dang it i like cookies)
But seriously..if have budget and going for ease of use..I'd vote SQL server.
If no budget...I pass the reigns to you, oh Master of Darkness
:)
This discussion is closed to new replies.
Trending Software posts
Sort by Trending