If your problem is as simple as persisting your Enum values inside SQL Server [In fact the storage DB doesn't matter that much in such scenario] then I have a word of advice for you. Store int representation of your enums inside your database and pursue a happy life afterwords:
Lets say you have a field in your your class storing phone number types:
public enum ContactType
public enum ContactType
{
Home = 0,
Mobile = 1
}
How would you go if you are asked for an additional entry, going and changing DB every time? No good!
You simply add it to you enum inside your code and problem sorted.