Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 one or several similar databases?¿?¿?¿?

Author  Topic 

tuenty
Constraint Violating Yak Guru

278 Posts

Posted - 2005-04-29 : 12:36:02
This is a design question

When I started working, in the Insurance company I'm working, I was asked to create two databases exactly the same for two different products. As new products are added new databases are created, I don't like this approach. At this moment only tables of one module are being updated life in SQL the rest of the tables are imported from legacy systems that are supposed to be substituted eventually.

The problem is that from time to time I have to modify databases and each time it is getting more complicated. And once we start creating the rest of the modules I think it will be like hell to make other modifications.

I want to merge all DBs into one (adding a product ID field) but I have to convince first the IT director. Some other issues with the data is that not all business rules apply the same to all products and I don't really know how complicated will be to enforce DB constraints depending on a field value ex. ProductID. Also the data is very sensitive so I may have some security issues that I'm not sure how to exactly deal with it at DB level (no DBA here), but I have already developed a DB to manage it at application level.

Can somebody guide me and give me some pros & cons so I can desist of the idea or convince the IT director to the change. I haven't done it earlier beacause I was alone in the company but we are going to hire 1 or 2 programmers that can help me in the conversion proccess

My pro list
  • Data is centralized
  • Better connection pooling
  • Easier to maintain
  • We can implement some new flexibilities that soon will be requierd by law
  • It will be easier to change now with only one module to change than later


My cons list
  • Data access may be slower
  • DB security may not be so secure



A candle loses nothing by lighting another candle

Kristen
Test

22859 Posts

Posted - 2005-04-30 : 10:06:35
I reckon that's about the top & bottom of it

Kristen
Go to Top of Page
   

- Advertisement -