Bespoke Database Design
I have a huge amount of copyright code already developed, which can be included in your database specifications, thus bringing down development costs. I can design simple custom contact databases to complex bespoke relational databases: combined with my experience I can build the application you need at a good price.
The first thing I always say to prospective clients is that a database should describe their company: if it does not do this, then the database is not well designed. A database is not a static collection of data, but a dynamic set of relationships between all the various types of people and objects that make up a company.
)
75 per cent of successful database design is in achieving a deep understanding of what the company is and what it does: that means spending a lot of time talking to people, looking at what they do and honing . It is no good to re-use an existing design and try and fit the company round that design - I am constantly amazed by developers who do this and often get away with it, leaving their client tearing their hair out when they try and use the database.
Finally, a database requires imagination to present these relationships in a way that users will understand, despite the complexities that may lie behind the design.
Which database I use depends on the demands of the business, but I usually use Microsoft Access which is perfect for organisations up to 12 users, but for more demanding projects I use SQL Server or MySQL.
I also design many databases for use with a web site, either to store content or to supply contact information, both of which can be manipulated by administrators or users with permission to do so.
It is also very important to build into any custom built database project a period in which you can get used to using the system as well as uncover any bugs that may get through. This is why I always include a year's support for a new database. At the end of this period, a client will often negotiate an extended contract to include ongoing support and additional development time, although this is obviously optional.
