Deploying multiple IIS Servers.

3 Aug 2006 7:47 AM

varija

I have a .NET application which is currently deployed using a single
app server (IIS). I want to use multiple IIS servers for the
application....primary reason being perfromance improvemnet for the
site.

We use SQL Server 2000 in the application and most of the tasks being
run on server are long running tasks taking hours to complete. Right
now only one such task can run at a time on the server and it uses the
SQL server at the back-end heavily. (together with other small
requests).

To improve this situation, i am planning to have multiple IIS servers
deployed. Is this the right way to go or are their any other solutions
?

Also, i think i will need to have multiple SQL servers .

Since i am pretty new to .NET framework, i am having a couple of issues
doing so.
Can some one give me some pointers where to start from or start looking
at something similar will help. It would really helpful.

Thanks in advance

3 Aug 2006 12:27 PM

msnews.microsoft.com

The question is whether high availability or load balance is the issue.

If you are going to load balance, you will have to look at WIndows NLB
(built into Windows 2003 Enterprise) or some other clustering technology.
The same is true for clustering SQL Server. WIth clustering, a group of
boxes have a single ip addresss, from a logical standpoint.

ONe thing you will have to do in your .NET apps is configure machine keys to
be the same on all boxes and have all point to the same session server
(either usingthe .NET session service or SQL Server). If you fail to do
this, you will have to use sticky sessions (person stays on box they
originally hit), which can destroy the benefits of clustering.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*************************************************
Think Outside the Box!
*************************************************

Show quote

"varija" <deepti.***@gmail.com> wrote in message
news:1154591260.934514.175080@p79g2000cwp.googlegroups.com...
>I have a .NET application which is currently deployed using a single
> app server (IIS). I want to use multiple IIS servers for the
> application....primary reason being perfromance improvemnet for the
> site.
>
> We use SQL Server 2000 in the application and most of the tasks being
> run on server are long running tasks taking hours to complete. Right
> now only one such task can run at a time on the server and it uses the
> SQL server at the back-end heavily. (together with other small
> requests).
>
> To improve this situation, i am planning to have multiple IIS servers
> deployed. Is this the right way to go or are their any other solutions
> ?
>
> Also, i think i will need to have multiple SQL servers .
>
> Since i am pretty new to .NET framework, i am having a couple of issues
> doing so.
> Can some one give me some pointers where to start from or start looking
> at something similar will help. It would really helpful.
>
> Thanks in advance
>

4 Aug 2006 5:05 AM

varija

thanks a lot, i did look at WLBS. Though i havnt tried it till now.
One more thing i could not figure out is if i need to write certain
custom load balaincing logic, can i built it on top of say WNLB ? Or in
that case i will have to write my own piece to handle load balancing.

msnews.microsoft.com wrote:
Show quote

> The question is whether high availability or load balance is the issue.
>
> If you are going to load balance, you will have to look at WIndows NLB
> (built into Windows 2003 Enterprise) or some other clustering technology.
> The same is true for clustering SQL Server. WIth clustering, a group of
> boxes have a single ip addresss, from a logical standpoint.
>
> ONe thing you will have to do in your .NET apps is configure machine keys to
> be the same on all boxes and have all point to the same session server
> (either usingthe .NET session service or SQL Server). If you fail to do
> this, you will have to use sticky sessions (person stays on box they
> originally hit), which can destroy the benefits of clustering.
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> *************************************************
> Think Outside the Box!
> *************************************************
> "varija" <deepti.***@gmail.com> wrote in message
> news:1154591260.934514.175080@p79g2000cwp.googlegroups.com...
> >I have a .NET application which is currently deployed using a single
> > app server (IIS). I want to use multiple IIS servers for the
> > application....primary reason being perfromance improvemnet for the
> > site.
> >
> > We use SQL Server 2000 in the application and most of the tasks being
> > run on server are long running tasks taking hours to complete. Right
> > now only one such task can run at a time on the server and it uses the
> > SQL server at the back-end heavily. (together with other small
> > requests).
> >
> > To improve this situation, i am planning to have multiple IIS servers
> > deployed. Is this the right way to go or are their any other solutions
> > ?
> >
> > Also, i think i will need to have multiple SQL servers .
> >
> > Since i am pretty new to .NET framework, i am having a couple of issues
> > doing so.
> > Can some one give me some pointers where to start from or start looking
> > at something similar will help. It would really helpful.
> >
> > Thanks in advance
> >