I don't know how concerned are you about scalability as I am not sure
what the proposed uses for your database solutions are, but for the
most part you can use simple ODBC MS Access databases, because those
yield the highest performance and can handle the biggest loads. And the
records are accessible from ASP pretty easily. This means that you don't
need to buy a SQL server until you are running into overload problems,
which you will be able to tell from the logs easily, and by then it will
be much easyer to justify the costs of a full blown SQL server.
If you can define what you want I can be more specific about the
solution.
..Endre
James A. Tucker wrote:
>
> Dumb me! Cold Fusion is just a development application/server like IDC/HTX and ASP.
>
> Any opinions are still welcome on this subject though.
>
> Thanks.
>
> James A. Tucker
>
> -----Original Message-----
> From: James A. Tucker [SMTP:jtucker@centuryinter.net]
> Sent: Tuesday, July 15, 1997 10:42 PM
> To: 'ntisp@emerald.iea.com'
> Subject: M$ SQL Server or Cold Fusion? Need opinion
>
> I'm looking for an Internet Database solution. In the left corner I have M$ SQL Server weighing in at $2999.00. In the right corner I have Cold Fusion Pro weighing in at $995. Is SQL worth 3X the weight in gold?
>
> My key areas I'm looking at are:
>
> Scalability
> Simultaneous Connections
> Administrative Costs
> Programming Ease or rather difficulty.
>
> I already know IDC/HTX so SQL leans a little in favor, but at 3X the cost I think I could learn Cold Fusion.
>
> I would appreciate opinions and experiences.
>
> Please, no ear biting between team M$ and team anti-M$.
>
> Thanks
>
> James A. Tucker
> Internet Administrator
> Century Telephone - Southern Region
>
> PS. Why do I feel like I've started a fire?
>
> ----------------------------------------------------------
> NTISP Mailing List listserver@emerald.iea.com
>
> ---------------------------------------------------------------
>
> Part 1.2 Type: application/ms-tnef
> Encoding: base64