Dumb SQL 2k Tricks

2 posts tonight, one is far to geeky to mix with the other.

How many of you have an old SQL 2000 app running somewhere at your company or a client. It can be an old custom app, a piece of unsupported software, or any number of other things. Often you can allivate the main issue with these systems, hardware failure, with virtualization. If you are not familiar with P2V processes I would recommend doing the P2V with the SQL services stopped, or better yet do a cold clone.

However I can across another issue that can happen in today’s computer world. A client of ours had an old SQL 2k database on a Windows 2k server (YAY for VNC!). This was a very sizeable database, around 200 custom scripts, numerous tables, etc. It was also still business critical. It had stopped sending mail, a key function to inform users of inventory counts. A coworker who is gifted with computers but with limited SQL experience asked me to take a look at it. He had been working on tracking down the expression that sent the mail, I was convinced that without the data loss there was nothing to indicate that.

A short bit of troubleshooting and I remembered that SQL 2000 had no smtp or other mail connectors built in. It used an Outlook profile to send mail, a pain that was done away with in later versions. The company in question had recently moved to AppRiver’s hosted exchange solution. Their old mail server was turned off, poof no more SMTP server for it to send to.

The quick fix? Log into the server with the SQL service account and change the Outlook profile to point to a new server. In this case it was a Friday after 5 pm, so that ended up being a spare hosting server of mine.

Admins have long learned not to change service accounts without expecting something to break. Also think about the effect of moving to the cloud on old services.


Leave a Reply