Server Upgrade (Update)
So, we were going to be upgrading the RAM on our server this weekend. This is the e-mail that I sent out to staff members before the upgrade was set to happen:
We will be performing a planned upgrade to Caleb1 tomorrow night. This maintenance will begin at 5:35 PM 04/26/2007 and be concluded by 7:35 PM 04/26/2007. During this time, only limited network services will be available. You will not be able to connect to the Internet, e-mail, Shelby, Pro Care, or any of the shared drives.
We don’t anticipate any problems with this procedure, and we have high hopes that it will increase network performance…
Now, I don’t believe in being jinxed or anything, but I do regret saying that we didn’t anticipate any problems. Of course there are going to be problems - there’s always problems on our network.
So, I stuck the RAM in, turned the machine on, and it was sweet. It was so much faster, but there was a casualty. SQL Server 2005 didn’t agree with the RAM upgrade and wouldn’t fully start-up. Not being in the mood or having the luxury of time, I did not re-install the SQL Server. Instead, I pulled out the new RAM, put in the old, and the problem was solved.
So, we’ll tackle the upgrade when we have time to create a true fix.
May 21st, 2007 at 5:25 pm
[...] I did a RAM upgrade on our sole server back on April 29th. It didn’t work out very well. Sure, nearly everything was great, but SQL Server 2005 [...]