Inquiry to those with broad knowledge (especially of RDBMS's)

[PrinceofWands]

I need to set up the network/web for my brothers business. I'm deciding between an Access/MsSQL database fronted by a Frontpage designed web, or an HTML/PHP/MySQL system. The obvious benefit of the MS setup is super easy creation, integration and management, while the open source option gives flexibility and cost savings (and I'm pretty sure it would require less in the hardware department as well).

Basically it's going to be a streaming media system (probably using netjuke), a public website with some limited db features for members, mail and message board, and our primary intranet db management system (which pretty much runs the entire company - member tracking, result tracking, inventory, sales, accounting, corporate reporting, employees, etc). I want all server functions centrally located (with a remote backup location of course), and we'll be serving to two clients initially, adding 2-4 more clients a year to a probable maximum of 20-40 clients (then expanding exponentially including overseas so it's a whole nother ball game at that point), and also having the occassional remote login.

I've had pretty good experiences with the Access route, but I hate to go to the owners with that cost analysis. I hear nothing but good things about a PHP/MySQL setup, but with my limited familiarity I don't know if it would give me the functionality I need. I'm not worried about learning curve of any options, just if the end result will produce my vision adequately.

So what's your votes and why? Also, any suggestions for hardware assignments and network layout? I'm currently envisioning a firewall/security management system, a second tier web/web app system, and third tier DB and storage (probably including music storage on this one). We'll also be needing mail services and probably message board, but I have no clue if that should be a seperate physical machine or if it can co-exist peacefully on one of the others, and if it's to be seperate which tier would you locate it on and why. Please note, this is a small business and we won't be purchasing SunFire's.

Thanks in advance...god I love little pet projects. Now if only I could get PAID for them. 8-(

 

[DJFuji]

Don't have a whole lot of experience with PHP, but i'm kind of partial to the microsoft route, personally. Having an MSDN Universal subscription has nothing to do with it, i swear. =)

We originally started out using Access with ASP 2.0/3.0 because it's a very cheap, easy solution. As things progressed, we took advantage of the Upsizing Wizard to port our DBMS to SQL Server 2000 using microsoft's ASP.NET. It required a bigger initial investment (purchase of VS.NET), but is much more powerful and will scale much better as we grow. The good thing is that being all microsoft products, they inteface fairly well with each other.

 

[jonmullen]

well all I can say is having worked with both, PHP/MYSQL and ASP/MSSQL 2000 I like the PHP/MYSQL route better, I find development time it faster and solutions are usually better. This probally has alot to do with the fact that I just like PHP alot better than VBscript I have to use with ASP classic. I also would say since you plan on expanding PHP/MYSQL is a better option as you grow cost wise.

 

[cyberia]

When I started using ASP few years ago, I was able to get a quick start both on learning and actual solution implementation with GenericDB scripts that provide generic web database interface.

Recently, I looked at what generic solutions are available for my current projects (such as projects tracking, event calendar etc.). It appears that there is a better chance of finding a good generic open source PHP/MySQL solution than a generic ASP/.NET/MS SQL solution. (I looked mostly at SourceForge).

I have no experience with PHP/MySQL at all. But since you are starting a fairly major web site from scratch, see if you can find generic code to implement a large chunk of your vision. Whatever technology offers a bigger number of useful generic solutions might be the one for you.

 

[labgeek]

I do what you're more comfortable with... My only issue with the MSSQL route is the costs. To use on a webserver you need to use the per processor licensing model. Last time I looked it was like $5K for standard and $20K for enterprise for SQL server alone PER CPU. That is if you plan on staying legit with your licenses to begin with...