February 14, 2010 at 11:55 am
Hi All,
Presently we are having a database that is having around 410 tables and no primary key, foreign keys, stored procedures , indexes etc...our company is in good form now having around 24 applications running such as iphone,blackberry etc.., we are doing great in business. In this way its taking us a longtime to develop new application and very difficult to try to find relationship between tables as we dont even have documentation. We r planning to create a new database and import all data parallely of developing new application.So please suggest me tools or best practices for doing this
February 14, 2010 at 1:26 pm
I'm a little confused...
If you decide to create a new database you'd need to have a good understanding of the business rules as well as the data model and structure.
Once you have that it might be worth looking at the current database and add the primary keys and foreign keys.
Regarding the lack of any procedures: That indicates you're running the queries from your apps diretly to the tables. That's not really a safe form of communication between app and SQL Server (for details please search for "SQL injection" to get a feeling for the risk you're probably putting your database at...).
This should also be considered when creating a new database. As long as the overall concept of software development doesn't change, even a new database won't help you in the long run, I think...
I strongly recommend to get a consultant in house to support you making a decision regarding the direction to go.
February 14, 2010 at 7:48 pm
I am like a inhouse consultant for them , i am trying to see how can i help them. Only I have good understanding of database, i want to make sure i am proceeding in right direction
February 16, 2010 at 5:11 am
I have worked on a re-engineering application before and this is what I observed. The fastest way to create a new database or to re-model the existing database is to understand the business process. Anything you try before that is just going to cost\waste your time. The smartest thing to do would be to build a ER model for the new database and map the old tables to it for migrating data
February 16, 2010 at 5:53 am
Ismail Ahmed (2/14/2010)
I am like a inhouse consultant for them , i am trying to see how can i help them. Only I have good understanding of database, i want to make sure i am proceeding in right direction
I would start by hiring a Functional analyst, a Project manager and a Database architect - those are the skills needed to tackle described project.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply