SQL Server is not always the answer

I found a database recently called “Birthdays”. A bit odd.

I looked into it, and found a single table storing the names of about 30 people, more than half of whom no longer worked for the company. And a stored procedure that no longer worked that was supposed to read this table and email the rest of the team when someone’s birthday was approaching.

Monitoring showed that this database hadn’t been used in three months (ie since monitoring began…)

This seems like one of those situations where, I don’t know, some sort of Calendar might be a better option than a SQL Server-based solution.

Database dropped.

This entry was posted in SQLServerPedia Syndication, Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.