Got a question about technology? Ask it here. Discussion of hardware, software, TiVos, multi-region DVDs, Windows, Macs, LINUX, hand-helds, iPods, anything tech related. Better than any helpdesk!
Well, SQL Server is cheaper than stuff like Oracle.
You could take a crash course on databases and web programming languages. Or you could just tell the developer, "This is our budget, and we expect this many users per day...." i.e. leave the specifics up to the developer.
OK, general question for other web people - which is easier to maintain? SQL Server/ASP or, say MySQL/PHP? My general experience is that the Microsoft solution is easier, at least until something goes wrong. Then you might be better off with some open source solution....
Thanks for the help.
Edit: I should say, I'm not going be all "You must use this software!" Just, "Here's what a couple of options would cost, now you figure it out."
SQL Server/ASP or, say MySQL/PHP? My general experience is that the Microsoft solution is easier, at least until something goes wrong. Then you might be better off with some open source solution....
I disagree. I think that PHP is easier to learn, and that MySQL, once installed, is pretty easy too. SQL Server isn't easy, in my experience. Just more inherently graphical.
Build your own scanning tunneling microscope: [link]
Tivo S2 DT reviewed.
Conclusion: Not worth the upgrade.
Silicon Graphics files for bankruptcy.
Sad now. But I can see how they're becoming a thing of the past.
If an organization were looking to build a database that people in different programs could access from different sites, would they be likely to use MS SQL Server? It's to track who's in what programs, attendance, progress, etc.
I'm with ita - but with one other perspective. The best development software is the software the people you have to do the job with can use well. MySQL has advantages (and bugs too). But for this small of a job they can probably be worked around. The question is have you already chosen the developer? Cause if you have you will get a better result developing in the language she or he is comfortable in.
I'm not actually choosing the language for the designer, but I need to come up with cost estimates for designing in-house versus buying a commercial product, so I just wanted to pick a reasonable starting point to say, "If, for example, you pick XYZ, it will cost you $$$." I'm good to go now. Thanks!
