General discussion

Locked

Help - Bad Code

By dcraun ·
I am the NT admin for my companies webservers. Its a fairly complex setup with load balancing, failover for all servers, DB servers, PDC & BDC's. Here is my problem, the programmers continuously puplish bad .asp's and .dll's each week which often crash the WWW service and cause other havoc. What would you recommend I should do to minimize the risk? Many of our applications require registry entries and ODBC changes as well. Of course we do have a QA department everthything must pass through. However, the live enviornment has many more variables.

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Help - Bad Code

by shawn.tooley In reply to Help - Bad Code

I think the best answer to your problem (also the most expensive) would be to build the QA test lab to same specs of your production servers. Use hardware that replicates your existing production enviroment and restore the latest production back-ups to the test servers to get a more thorogh idea of the how the production servers will act after the code updates.

Collapse -

Help - Bad Code

by dcraun In reply to Help - Bad Code

Thanks for the advice, those steps are already in place. I was hoping for that magical answer, like some application that would track changes for you.

Collapse -

Help - Bad Code

by dcraun In reply to Help - Bad Code

This question was closed by the author

Back to Windows Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums