Bad database design... What would you do?

stoutontap · #1 (**permalink**) 01-13-09, 13:12

I'm having a problem with database design. Please give me some advise.

We have a software development project and I'm the only developer for the project. I did database design and there are 24 tables.

My manager, who is not a software developer but has some database knowledge from Microsoft Access, wants to split the database in 3 different database instances. She insists she needs to split since some of the tables might be going to be used by some other people (or system) in the future so that it would be easier if we split it from the beginning. This is the problem I am having right now.

As you all know, if we split the database you cannot make relationship (like foreign keys and some constraints) between tables among different databases. You need to code the relationship functionality, instead. To me, it sounds nonsense. Relational database has that functionality, but because of her "preference", I have to code it by myself...

I believe that although some of the tables might be going to be used by some other people in the future, it still should be in 1 database. And it's only "possibility", anyways. I have been trying to convince her to keep them in 1 database, but now she is getting annoyed by my suggestion. We kind of had a big argument yesterday and she told me I had to do it (split the database), anyways...

I kind of think because I speak English as a second language, I cannot make her fully-understand why it is a bad idea to split the database.

What do you guys think?

My options are:

1. I try to convince her again (Please give me some advice how I can convince her. I could lose my job if I fail.)
2. Just quit the job (Because developing software with wrong design is a pain)
3. Just do it as she wants (It's going to be a lot of stress but do it just to pay my rent and bills for a while. Eventually I will quit if I find another job.)

MCrowley · #2 (**permalink**) 01-13-09, 13:27

What RDBMS is this being developed in? In most of them, you can define security on tables that will prevent unauthorized users from getting at data.

stoutontap · #3 (**permalink**) 01-13-09, 13:32

Yes, that's what I told my manager, like we could set table-level permissions, but she said it's a lot of trouble although I don't think it's any trouble... We are using SQLServer 2000.

MCrowley · #4 (**permalink**) 01-13-09, 13:37

Only as much trouble as having to set up three databases with users specific to each one.

Oh, she is planning on using SA for all access, then?

stoutontap · #5 (**permalink**) 01-13-09, 13:48

Agreed.

She's planning Windows Integrated Authentification.

stoutontap · #6 (**permalink**) 01-13-09, 13:49

As she created PowerUser, ReadWrite, and ReadOnly groups.

pootle flump · #7 (**permalink**) 01-13-09, 15:56

Quote:

Originally Posted by stoutontap

Yes, that's what I told my manager, like we could set table-level permissions, but she said it's a lot of trouble although I don't think it's any trouble... We are using SQLServer 2000.

Yeah - I often find it is better to rig up my own version of stuff rather than use the in built, native system functionality. Tsk!

Her experience is Access? Security is a b***h in Access, so that might colour her thinking. Also (and I am afraid this is true) there are a lot of people learned a lot of bad practices from dabbling about in Access.

You are spot on.

Would you like some scripts to set up the security on a test system to show how easy this is? (It's easier in 2k5, but not too much bother in 2k).

blindman · #8 (**permalink**) 01-14-09, 08:43

Mark Twain once said "Put all your eggs in one basket....and then watch that basket!"
Same goes true for databases.
Splitting the database is nonsense, even for MS Access. Access is often split to separate the data from the forms and reports, but related data should not be split between DBs.

stoutontap · #9 (**permalink**) 01-14-09, 12:21

Quote:

Would you like some scripts to set up the security on a test system to show how easy this is? (It's easier in 2k5, but not too much bother in 2k).

That is a good idea. I should do it.

Once she knows it is not a lot of trouble, maybe I have some chance to convince her...hopefully.

stoutontap · #10 (**permalink**) 01-14-09, 12:25

Quote:

Splitting the database is nonsense, even for MS Access. Access is often split to separate the data from the forms and reports, but related data should not be split between DBs.

I totally agree. I wish you were in my team and help me convincing her... I am the only developer in the team and there is no one else who can help me... She thinks she is a software developer or database developer, but obviously she is not... Tough situation I am facing...

loquin · #11 (**permalink**) 01-14-09, 12:29

MS Access Security is an oxymoron.

The only reason you would want to split the table in SQL Server is to partition the data for performance reasons. All modern database servers have good to excellent security mechanisms, which aren't hard to implement.

stoutontap · #12 (**permalink**) 01-14-09, 12:38

Yesterday I tried to convince her again. Before it goes to the core part, she got pretty emotional and told me, "I am your boss and now you split the database". I thought it's enough. She's being so stubborn for her wrong idea. I give up.

Last night I was thinking about my situation and kind of decided to quit this job. But, not right now. The job market is quite dead and there are not so many interesting jobs. Plus, I'm a foreighner who speaks English as a second language. Not right time to quit with no plan. I will probably do whatever she wants until l find another job. I know it's a pain. Each time I program some codes, I would feel like, "Am I doing right thing? No!". But I need to pay my rent and bills.

Thank you guys for giving me some comments. You guys encouraged me as I was not wrong. You let me know I'm working for a wrong person. If you have any job info, please let me know.