A common mistake in considering a database implementation is to assume that simply using SQL create table statements or to use the facilities of a database tool to define them for you is all you have to do. However, uncontrolled ad hoc creation of tables by end users leads to an unmanageable and unusable database environment and can result in the inclusion of multiple copies of potentially inconsistent data resulting in end users unable to find the data that they require.
It's not enough to know what kinds of a database might work for you. You also need to carefully think through how to find the right database for your needs, and how to get it up and running smoothly. This involves defining your needs, evaluating your options, efficiently implementing the software, and providing the ability to maintain your database.
For the past 10 years, I have been deeply involved in the design, implementation, training of users, and maintenance of complex databases for a broad range of clients in various industries. My goal has always been to ensure that these expensive business assets meet their business demands.
My successes are partly the result of my ability to address the dozens of technologies and tools available in this constantly evolving environment. This requires me to be a lifelong student of database design processes and tools.
It’s not that all the decisions I make are perfect but I make them with conviction. I can fix a bad decision but improvement can’t be achieved until a decision is made.
If you’re encountering performance issues with your databases or plan to implement a new database infrastructure or need an expert on SQL Server Databases then we should talk.