![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
camwynSQL has installed. Currently the machine is pulling down SQL Server 2005 Service Pack 1, because that is what the server it's to duplicate is using. The install appears to have gone without a hitch. I have not tried to configure anything beyond defaults and basics, which is what our programmer said to do.
Last time, SQL installed and ran, but nothing could be published to the internal web site that was being used to distribute the SQL application. I am hoping this will not be the case this time. I do not know. I think I may have tracked down the error, though- I could be wrong, but I think it has to do with server naming. SQL was installed on the server when it was named SULU. For some reason, I forget what, the server had to be renamed to TAKEI before anything else could be done. After that, forget it- le doom. The server is supposed to take the place of one named UHURA, so I took it off the network, named it UHURA, and installed SQL. Once that was done I renamed it to NICHELLE and connected it to the network so it could pull down its updates- UHURA is already in service on the network, so it couldn't be reused. When all of this is done I'm naming it UHURA and joining it to the domain for testing, but this can't be done while the original UHURA is still in use. We will have to test it during off hours or something.
Once the test is successful, the original UHURA is going to go up to our contingency site and be installed there for use in disaster recovery situations. The new one will be staying here. The test is scheduled for the 4th and I do not want to delay it any further because of my own unfamiliarity with this stuff, so I'm knocking on wood, praying and hoping, and invoking St. Isidore of Seville, patron saint of the Internet.
On the bright side, I'm going out to dinner and then probably to a Traveller RPG session tonight. I have no intention of thinking about any of this after hours. It'll just eat at my circulatory and digestive systems. I can worry about it in the morning.
Last time, SQL installed and ran, but nothing could be published to the internal web site that was being used to distribute the SQL application. I am hoping this will not be the case this time. I do not know. I think I may have tracked down the error, though- I could be wrong, but I think it has to do with server naming. SQL was installed on the server when it was named SULU. For some reason, I forget what, the server had to be renamed to TAKEI before anything else could be done. After that, forget it- le doom. The server is supposed to take the place of one named UHURA, so I took it off the network, named it UHURA, and installed SQL. Once that was done I renamed it to NICHELLE and connected it to the network so it could pull down its updates- UHURA is already in service on the network, so it couldn't be reused. When all of this is done I'm naming it UHURA and joining it to the domain for testing, but this can't be done while the original UHURA is still in use. We will have to test it during off hours or something.
Once the test is successful, the original UHURA is going to go up to our contingency site and be installed there for use in disaster recovery situations. The new one will be staying here. The test is scheduled for the 4th and I do not want to delay it any further because of my own unfamiliarity with this stuff, so I'm knocking on wood, praying and hoping, and invoking St. Isidore of Seville, patron saint of the Internet.
On the bright side, I'm going out to dinner and then probably to a Traveller RPG session tonight. I have no intention of thinking about any of this after hours. It'll just eat at my circulatory and digestive systems. I can worry about it in the morning.
