SQL 2000 and dot.NET
-
Pardon the possible naivete of my question, but here it goes:
We intend to put up a handful of Win2000 servers with IIS5 and dot.NET
Framework on them (in order to use ASP.NET). In addition, there will be one
dedicated Win2000 Server machine with SQL2000, which will act as a back-end
database server answering queries from the IIS boxes. This SQL2000 computer
will NOT have IIS installed because it doesn't need it.
So my question is: In the above scenario, is it a good idea to install the
dot.NET Framework also on the dedicated SQL2000 box, or only on the web server
boxes?
What are the advantages/pros/cons of installing, vs. not installing the
dot.NET Framework on a dedicated SQL2000 machine with no IIS?
Thank you.
-
It sounds like you shouldn't need .Net on the SQL Server box. As long as you aren't running IIS (and/or Reporting services Web server part, etc.) on the SQL Server, the framework won't do you any good. I don't go out of my way to install the framework on SQL Servers unless it is needed by another app that we have chosen to install on the SQL Server.
-
I agree with Chris
You should always keep everything as distinct as possible. One server for SQL2000(only), doesn't need anything more, and the other for IIs and the framework - distinct : Database versus Engine. It's a good schema and it works better(most of the times - it should). -
This would depend on how the application is architected. In systems I design, I almost always build multiple tiers in the system, and I will want (if possible) to put the tiers that do the actual data access on the same server as SQL Server. It is not uncommon to have a .Net middle-tier component (web service) construct a dataset for a web page from 4-6 queries on the database. It is more efficient to do the 4-6 db queries from the component on the same server (using Shared Memory protocol connection) and just pass the single dataset to the program constructing the web page, than to have 4-6 queries across the network from the web server to the SQL Server using (slower) TCP protocol.
However, if web sites are built two-tier, where the .Net web are accessing the databases directly, there probably is not a need for the .Net framework. Although, if there are application options where you might want to use DTS or SQL jobs to call a custom application program from SQL Server (using the SQL Job Scheduler to execute programs?), it may be helpful to have the .Net framework on the server.
Hope this helps
Mark
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply