- Aug 8, 2005
- 593
- 0
- 0
There are some minute issues going with a SQL server, after doing research I came to the conclusion that .NET framework 2.0 needs to be deployed on it to resolve the problem, however I don't know what it could potentially impact.
Therefore I want to make a virtual server that is basically a duplicate of the actual environment and use it as a test bed.
Should I put this server on a DMZ? If it is an exact image copy that is (also would nortons ghost, be the best way to deploy the image on that test bed) I just don't want the actual server effecting clients that are requesting any information from that database so i'm wondering if going to the extent of putting it on a DMZ would be the best bet..or if I even have to go that far, since technically all the ODBC connections should look by hostname/ip address, and if I technically just change the hostname it should never request it.
Therefore I want to make a virtual server that is basically a duplicate of the actual environment and use it as a test bed.
Should I put this server on a DMZ? If it is an exact image copy that is (also would nortons ghost, be the best way to deploy the image on that test bed) I just don't want the actual server effecting clients that are requesting any information from that database so i'm wondering if going to the extent of putting it on a DMZ would be the best bet..or if I even have to go that far, since technically all the ODBC connections should look by hostname/ip address, and if I technically just change the hostname it should never request it.