Oh, and side note. There is one other thing to consider.

There exists a heirachy within Service_Providers

Owner
Worker

I opted not to use two seperate tables because this would increase programming complexity. ... I would have to implement to determine, in some fashion, wether the person logging in was a owner or a worker ... in that case, I would have If statements all over the place everytime I wanted to do a query. Because I won't intutively know what type of user the person is so therefore, I wouldn't know automatically which table to query.
Not to mention the fact that Owner and Service Provider have almost identical table attributes... in programming inheritence would solve this problem easily ... but I know no way of doing that in DB Design