Web Server and Database Server separated

Hi,

Here is the scenario. Our website is hosted by hosting company. We plan to host the database at our office. The website connects to our database at our office. Is this possible? Is there a performance issue?

Thanks.

Dennis

That certainly is possible.
Things to take into mind, you have a open connection to your database server to anyone on the intranet, so you have to secure the connection via firewall and IP access control list. You might also think about creating a Web Service at the location where your database is for the application on hosts machine to access your data. Connection to the service via SSL would be relatively secure.
Secondly, there will be a slowdown in perfermance since the performance of your website rely's on the speed of yours hosts connection, the speed of your connection, and traffic on both of your networks. A local connection is faster than a remote connection, especially for accessing large amounts of data and a high number of queries. So if your pipe from the host to your database location is not sufficient to support the traffic for you site there will be a performance issue.

It's likely possible (depending mostly on your database engine, and thefirewall situation between your office and the hosting company) butthere may be some pretty serious performance issues. The timethat it's going to take to get data across the Internet could besignificantly longer than over a LAN. Personally, I'd bepretty cautious about this configuration. Not that it won't work,but certainly, test it well.

Web Server Performance

We have a Win 2003 Server that runs around 15 instances of an ASP.NET 1.1
Web Application ( in the same application Pool).
Each instance connects to a SQL 2K database on a separate database server.
The database size is around 100 MB (min ) to 3 GB Max.
The web server is a 2.6 GHZ Xeon with 2 GB of RAM.
The database server is a dual proc Xeon with 4 GB of Ram.
Each instance of the Web Application has an average of 15 users.
We reboot the servers every wend.
I have set the Worker Process to recycle at 4 AM everyday.
The problem is that our clients often receive Out Of Memory exceptions.
Task
Manager doesn't show any abnormal activity.
The Memory Utilization on the web server seems to be around 500 MB .. which
should be fine for a 2 GB RAM system that is used solely as a web server.
My questions:
1 Are we overloading the server. ?
2 What tweaks or configuration changes can we do to improve performance.
Thanks,
Sachin SalgarkarSachin,
Sometimes it can be something as simple as changing the
connectionstring to the database slightly to improve pooling, or ensuring
that the garbage collection is happening correctly. Even though .Net is
managed, garbage collection should still be written to handle the closing of
datareaders/connections and disposing of them properly. That helps free up
their resources quickier.
MS released a great book in their patterns and practices called Improving
.Net Application Performance and Scalability. You don't have to buy it
though as they also made a downloadable PDF version at:
http://msdn.microsoft.com/library/d...n
et.asp
This has a good number of well-organized do's and dont's that would let you
dig through and check to see if there is something going on in your code
that could be altered or some setting that could be tweaked to avoid your
issues.
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199...2006
"Sachin Salgarkar" <sachin@.aegiscommerce.com> wrote in message
news:uN7rUpG7GHA.4552@.TK2MSFTNGP05.phx.gbl...
> We have a Win 2003 Server that runs around 15 instances of an ASP.NET 1.1
> Web Application ( in the same application Pool).
> Each instance connects to a SQL 2K database on a separate database server.
> The database size is around 100 MB (min ) to 3 GB Max.
> The web server is a 2.6 GHZ Xeon with 2 GB of RAM.
> The database server is a dual proc Xeon with 4 GB of Ram.
> Each instance of the Web Application has an average of 15 users.
> We reboot the servers every wend.
> I have set the Worker Process to recycle at 4 AM everyday.
> The problem is that our clients often receive Out Of Memory exceptions.
> Task
> Manager doesn't show any abnormal activity.
> The Memory Utilization on the web server seems to be around 500 MB ..
> which
> should be fine for a 2 GB RAM system that is used solely as a web server.
> My questions:
> 1 Are we overloading the server. ?
> 2 What tweaks or configuration changes can we do to improve performance.
> Thanks,
> Sachin Salgarkar
>
Thanks Mark.
-Sachin
"Mark Fitzpatrick" <markfitz@.fitzme.com> wrote in message
news:uVUhZxG7GHA.2380@.TK2MSFTNGP02.phx.gbl...
> Sachin,
> Sometimes it can be something as simple as changing the
> connectionstring to the database slightly to improve pooling, or ensuring
> that the garbage collection is happening correctly. Even though .Net is
> managed, garbage collection should still be written to handle the closing
> of datareaders/connections and disposing of them properly. That helps free
> up their resources quickier.
> MS released a great book in their patterns and practices called Improving
> .Net Application Performance and Scalability. You don't have to buy it
> though as they also made a downloadable PDF version at:
> http://msdn.microsoft.com/library/d...br />
enet.asp
> This has a good number of well-organized do's and dont's that would let
> you dig through and check to see if there is something going on in your
> code that could be altered or some setting that could be tweaked to avoid
> your issues.
>
> --
> Hope this helps,
> Mark Fitzpatrick
> Former Microsoft FrontPage MVP 199...2006
> "Sachin Salgarkar" <sachin@.aegiscommerce.com> wrote in message
> news:uN7rUpG7GHA.4552@.TK2MSFTNGP05.phx.gbl...
>

Web Server Performance

We have a Win 2003 Server that runs around 15 instances of an ASP.NET 1.1
Web Application ( in the same application Pool).
Each instance connects to a SQL 2K database on a separate database server.
The database size is around 100 MB (min ) to 3 GB Max.
The web server is a 2.6 GHZ Xeon with 2 GB of RAM.
The database server is a dual proc Xeon with 4 GB of Ram.
Each instance of the Web Application has an average of 15 users.

We reboot the servers every weekend.
I have set the Worker Process to recycle at 4 AM everyday.

The problem is that our clients often receive Out Of Memory exceptions.
Task
Manager doesn't show any abnormal activity.
The Memory Utilization on the web server seems to be around 500 MB .. which
should be fine for a 2 GB RAM system that is used solely as a web server.
My questions:
1 Are we overloading the server. ?
2 What tweaks or configuration changes can we do to improve performance.

Thanks,
Sachin SalgarkarSachin,
Sometimes it can be something as simple as changing the
connectionstring to the database slightly to improve pooling, or ensuring
that the garbage collection is happening correctly. Even though .Net is
managed, garbage collection should still be written to handle the closing of
datareaders/connections and disposing of them properly. That helps free up
their resources quickier.

MS released a great book in their patterns and practices called Improving
..Net Application Performance and Scalability. You don't have to buy it
though as they also made a downloadable PDF version at:
http://msdn.microsoft.com/library/d...ml/scalenet.asp
This has a good number of well-organized do's and dont's that would let you
dig through and check to see if there is something going on in your code
that could be altered or some setting that could be tweaked to avoid your
issues.

--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006

"Sachin Salgarkar" <sachin@.aegiscommerce.comwrote in message
news:uN7rUpG7GHA.4552@.TK2MSFTNGP05.phx.gbl...

Quote:

Originally Posted by

We have a Win 2003 Server that runs around 15 instances of an ASP.NET 1.1
Web Application ( in the same application Pool).
Each instance connects to a SQL 2K database on a separate database server.
The database size is around 100 MB (min ) to 3 GB Max.
The web server is a 2.6 GHZ Xeon with 2 GB of RAM.
The database server is a dual proc Xeon with 4 GB of Ram.
Each instance of the Web Application has an average of 15 users.
>
We reboot the servers every weekend.
I have set the Worker Process to recycle at 4 AM everyday.
>
The problem is that our clients often receive Out Of Memory exceptions.
Task
Manager doesn't show any abnormal activity.
The Memory Utilization on the web server seems to be around 500 MB ..
which
should be fine for a 2 GB RAM system that is used solely as a web server.
My questions:
1 Are we overloading the server. ?
2 What tweaks or configuration changes can we do to improve performance.
>
Thanks,
Sachin Salgarkar
>

Thanks Mark.

-Sachin

"Mark Fitzpatrick" <markfitz@.fitzme.comwrote in message
news:uVUhZxG7GHA.2380@.TK2MSFTNGP02.phx.gbl...

Quote:

Originally Posted by

Sachin,
Sometimes it can be something as simple as changing the
connectionstring to the database slightly to improve pooling, or ensuring
that the garbage collection is happening correctly. Even though .Net is
managed, garbage collection should still be written to handle the closing
of datareaders/connections and disposing of them properly. That helps free
up their resources quickier.
>
MS released a great book in their patterns and practices called Improving
.Net Application Performance and Scalability. You don't have to buy it
though as they also made a downloadable PDF version at:
http://msdn.microsoft.com/library/d...ml/scalenet.asp
This has a good number of well-organized do's and dont's that would let
you dig through and check to see if there is something going on in your
code that could be altered or some setting that could be tweaked to avoid
your issues.
>
>
--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006
>
"Sachin Salgarkar" <sachin@.aegiscommerce.comwrote in message
news:uN7rUpG7GHA.4552@.TK2MSFTNGP05.phx.gbl...

Quote:

Originally Posted by

>We have a Win 2003 Server that runs around 15 instances of an ASP.NET 1.1
>Web Application ( in the same application Pool).
>Each instance connects to a SQL 2K database on a separate database
>server.
>The database size is around 100 MB (min ) to 3 GB Max.
>The web server is a 2.6 GHZ Xeon with 2 GB of RAM.
>The database server is a dual proc Xeon with 4 GB of Ram.
>Each instance of the Web Application has an average of 15 users.
>>
>We reboot the servers every weekend.
>I have set the Worker Process to recycle at 4 AM everyday.
>>
>The problem is that our clients often receive Out Of Memory exceptions.
>Task
>Manager doesn't show any abnormal activity.
>The Memory Utilization on the web server seems to be around 500 MB ..
>which
>should be fine for a 2 GB RAM system that is used solely as a web server.
>My questions:
>1 Are we overloading the server. ?
>2 What tweaks or configuration changes can we do to improve performance.
>>
>Thanks,
>Sachin Salgarkar
>>

>
>