SQL Server and IIS on same box?


    Sponsored Links


  • 1. query stored procedure problem.
    Hi I have a stored procedure that creates a query dynamically based on input parameters and uses EXEC sp_executesql @sql, @paramlist ect. Anyhow I pulled everything out of the stored procedure and ran it as a query setting the input veriables. I then added a Left outer join and the still query works fine but when this left outer join is added to the stored procedure it returns no data. Any suggestions, thanks.
  • 2. SQL Server 2008 Developer edition COA
    I just purchased SQL Server 2008 Developer edition from Amazon..It has a Microsoft COA and I'm sure it's legit... but none of the numbers on the label are close to the 25 character # it's asking for. I can't be the only one who has noticed this. Please offer some advice on who to contact. Thank You Paul
  • 3. Clustered 2005 and 2008 instances
    We currently have a cluster with multiple SQL Server 2005 instances. We will soon be installing at least one SQL 2008 instance on this same cluster. Two questions: 1. After installing SQL 2008 on this cluster, can we still install additional SQL 2005 instances if necessary in the future? 2. If no to #1, can we apply future service packs to the existing SQL 2005 instances after installation of a SQL 2008 instance? We need to maintain support for both versions on this cluster (and others).

SQL Server and IIS on same box?

Postby V2lzZUd1eQ » Thu, 03 Mar 2005 05:11:06 GMT

Is there any MS document or link that clearly states Microsoft's position 
regarding SQL Server and IIS on same box, either from and implentation or 
web-design standpoint?

Thanks in advance.

RE: SQL Server and IIS on same box?

Postby TWlrZSBFcHByZWNodCAoU1FMIE1WUCk » Fri, 04 Mar 2005 19:09:04 GMT


They do not have a policy that say no. You can run everything on one box, 
but then you have to worry more about security.

Look at 
for best practices.

Re: SQL Server and IIS on same box?

Postby Hank Arnold » Sat, 05 Mar 2005 18:13:10 GMT

General rule of thumb, IMHO, is that nothing else should be running on the 
box that is running SQL Server. Otherwise there will be degraded 
performance. Having said that, it may be appropriate if the performance is 
still acceptable to you or the cost of multiple servers is just way too 

Having said that, I would avoid running IIS at all costs. Especially if it's 
accessible externally. Way too much of a security exposure....

Hank Arnold

Similar Threads:

1.SQL Server and IIS on same box?

Is there any MS document or link that clearly states Microsoft's position 
regarding SQL Server and IIS on same box, either from and implentation or 
web-design standpoint?

Thanks in advance.

2.APS.NET, IIS cannot connect to SQL Server box


I am using the following connection string format in an ASP.NET 1.1 
application to attempt to connect to a SQL Server on another machine.

Data Source=ServerName;Initial Catalog=DBName;User 
ID=username;password=pwd;persist security info=True;

I am testing this asp.net app. from my local IIS to connect to a SQL Server 
instance on another box. It will not work and I am unable to determine why, I 
have verified by cutting and pasting the same connection string to a windows 
app and the user name and password to isql and both are able to connect 
without any problems. The really strange thing is if I use an ip address 
instead of a name for the server I can get the web application to connect 
without a problem.

The PC that the asp.net app is running on is WIN XP PRO with SP2 and the 
most current updates, the SQL Server version is 2000 with the most current SP 
and updates. 

I think IIS is not able to resolve the name of the server therefore it can't 
find it, but I don't know how to fix this.
I have run out of ideas please help.

Thank You

3.Keeping IIS and SQL Server on seperate boxes


I have a problem in that I have one server with IIS and another with SQL 
Server 2000. I would like to run SSRS from the SQL Server and then store all 
my pages on the IIS server. Is there a way of doing this. Only installing 
SSRS on the SQL Server and then everything else on the IIS server. I have 
installed SSRS on a server that has both SQL Server and IIS on it and no 
problems. The thing is I need the Virtual Directories on the IIS server and 
not the SQL Server box. I am not allowed to install SSRS on the IIS box as 
this would mean another license which my company is not prepared to do.

Please any help on how this could be done would be greatly appreciated.


4.IIS 6 and SQL Server - two seperate boxes

I am deploying IIS (w/ASP.NET) and SQL on two seperate boxes. I am having 
trouble using a trusted connection between the two. I have found many 
suggested solutions from many "experts" for dealing with this, but I'm 
looking for the most secure option. The documentation I've found to date 
doens't discuss the ramifications of different options. Also, a lot of the 
suggestions seem to be incomplete. Can someone help me with a secure solution 
for this?

5.Server Tools 3.0 & 3.5 on single IIS Box?

I seem to have painted myself into a corner.
I learned today when I went to install the Sql Server 2005 Server
Tools 3.5 on our current IIS box that it requires one to uninstall 3.0
I need to be able to run BOTH versions on the same IIS box.

I was planning to create two virtual directories, one for 3.1 clients
using RDA and Replication to a Sql Server 2000 box, and the other
virtual directory running 3.5 doing just RDA.  Being forced to remove
the 3.1 tools when installing 3.5 really sunk those plans.

Is there any way out of this mess?  I am not in a position to upgrade
the sql 2000 box, I need replication, and my new client app is written
entirely in .NETCF 3.5, which only works with sql ce 3.5, not 3.1.

6. HTTP Connection for MSOLAP (IIS server on a seperate box)

7. Contact to sql server from a seperate box

8. Pad strings/concatenate columns to simulate data columns in ASP select box with SQL Server 2K



Who is online

Users browsing this forum: No registered users and 34 guest