Comments on: Minimizing Downtime When Deploying ASP.NET Web Applications http://www.billrowell.com/2009/01/17/minimizing-downtime-when-deploying-aspnet-web-applications/ Welcome To My World Tue, 15 Jun 2010 12:06:03 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Bill http://www.billrowell.com/2009/01/17/minimizing-downtime-when-deploying-aspnet-web-applications/comment-page-1/#comment-3138 Bill Tue, 10 Feb 2009 04:17:51 +0000 http://www.billrowell.com/?p=472#comment-3138 Josh, Thanks for the suggestions. I'll definitely try working some of those into my solution. Josh,

Thanks for the suggestions. I’ll definitely try working some of those into my solution.

]]> By: Josh http://www.billrowell.com/2009/01/17/minimizing-downtime-when-deploying-aspnet-web-applications/comment-page-1/#comment-3135 Josh Tue, 10 Feb 2009 02:14:55 +0000 http://www.billrowell.com/?p=472#comment-3135 I run my site on 2 dedicated servers, 1 for web and 1 for the DB. I keep a staging version of my site on the DB server for testing since it is generally handling a lighter load and that way if I require an IIS restart it will not affect my live site. As for database changes, unless you are modifying existing fields in tables there should be ways around it affecting your live site. If I need to change a view or stored procedure, for example, named qryItems I will temporarily create a new one based on the original called qryItems1 which will include the new modifications and change the code on the test site to use this view for testing. I almost never make changes to tables besides adding fields anyhow so this approach has worked well for me. When it comes to actually deploying new assemblies the only downtime the live site has is performing the IIS restart :) I run my site on 2 dedicated servers, 1 for web and 1 for the DB. I keep a staging version of my site on the DB server for testing since it is generally handling a lighter load and that way if I require an IIS restart it will not affect my live site. As for database changes, unless you are modifying existing fields in tables there should be ways around it affecting your live site. If I need to change a view or stored procedure, for example, named qryItems I will temporarily create a new one based on the original called qryItems1 which will include the new modifications and change the code on the test site to use this view for testing. I almost never make changes to tables besides adding fields anyhow so this approach has worked well for me. When it comes to actually deploying new assemblies the only downtime the live site has is performing the IIS restart :)

]]>