June 20, 2007 at 8:37 am
Hi All,
I just started working for a new company which has a large datacentre running SQLServer 2005.
When I examined the database I noticed the following:
- There are no referential constraints in the entire database.
- Most tables have a compound primary key which includes an identity column.
- Referential integrity is enforced using triggers only (obviously).
In my opinion this is not a very well designed database so I'm trying to get the developr who designed it to refactor or redesign it. In order to make my case I need some good arguments and since I'm not a DB specialist I was hoping someone here can help me.
Specifically I would like to know how these design decisions effect performance.
Thanks
Rene
June 20, 2007 at 9:42 am
First question : data warehouse or transactional database (reporting or working)?
June 20, 2007 at 10:34 am
the most important point is that most databases and applications are often not well written for any number of reasons. If the performance of the database is bad then fair comment but the points you raise are unlikely to degrade performance.
RFI is always good but there could be good reasons why there isn't any - as for compound PK's - well to be blunt, without any knowledge of the application or database you are saying this is wrong - you probably won't make many friends with this approach - it's too long a discussion as to PK choice - and another thread - I tune apps/databases for a living - I work on the basis thta most customers want improvements and life's like that, databases are often bad.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
June 20, 2007 at 10:44 am
Nice pragmatic approach, I agree with it entirely!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply