jump to navigation

A Single Database, or Multiple Databases for a Global Company? 02/09/2009

Posted by TBoehm30 in Database.
Tags: , ,

A Global Information System (GIS) can allow a company to have a single source for data. Multinational companies have the opportunity to have one database that can be used for all agents in every country around the world. This database could handle all transactions relating to a single application. Borders become blurred when using technology to connect disparate locations of a single company.

The single database model can enforce a unified process across the entire company. Using one database for the entire company can provide measurements and reports that are valid for every department. Reports can be compared between countries because data can be consistent across business units around the world.

Any company that does business in multiple countries could use a GIS. A logistics system would track all products in every country. Warehouses would connect to the same database to query and enter inventory quantities. Availability of parts could be determined not just be warehouses in a single country, but by the closest location.

A CRM application would provide complete break-fix reports for products. Every country would report on problems with a product. A company could easily determine how to proactively improve their products for every country out of one database. Having a single source of data allows the company to synchronize their presentation to their customers.

Why use a global database?

A global database is needed to standardize data from around the world. A Global Information System (GIS) can allow a company to create reports for all countries and regions that can be compared against each other. A single instance of a database could be an amazing resource for understanding the position of a company.

In the CRM world, there are so many different processes that one could not even attempt to catalogue them, much less count them. Whether that process is good or bad, it should be very similar no matter which country a customer is calling from. An English speaking user should get the same process results as a German speaking customer. The data that is collected in Japan should be very similar to data collected in Canada.

Why not?
Creating a single instance of a database can be a daunting task. It requires that users from disparate locations have equal access to the computers. It means that all users must have some form of understanding of a language that is agreed upon. Users will have to compromise on customizations. There must be some fields that have to be in a common language.

All affected divisions of a company would have to agree on the front end software allowing the users to have a single view of their data. Managers wanting improvements would have to schedule their customizations in cooperation with managers around the world. Processes would have to be similar in order to enter the correct data into the database.

The servers that deliver the database would have to be available 24 hours a day, 7 days a week. Because of differing schedules of daytime and night, there are always offices who need live access to their data. Bringing the system down for planned maintenance becomes a coordination effort of massive proportions.

A single database would most likely have a single set of servers, meaning one location. Connecting to those servers becomes slower based on numerous factors. The network needs to be robust and fast. The number of users could slow down a system that isn’t scaled correctly.

Maintenance must be handled by a group of people who are not only technically efficient, but able to communicate in any language. Problem calls would come from any country in every language. The company must have a way to handle any call about problems with the database. Internal support is a critical factor in getting everyone to keep using a single database.

If technical people are using a shared database, they will inevitably find a need to create their own solutions. They will create a personal database on their own computer. They could create a small database that is shared with their group. They might even come up with a workaround to highjack the existing database and load it with their own information. Keeping a single instance of a database requires that every be convinced it is the correct solution. Managers must make sure that their groups follow the rules covering the global database.

If a company has the need for a single source of data, they will need to determine how to use a single database. There are many ways to come up with an answer to that problem. The trick is finding a way that accomplishes the same functionality with a sustainable return on investment along with a system that is usable and supportable over the long term.

Currently many global companies have separate databases for their business units that report differently. So a financial office in Russia would connect to a different database than the financial office in Boston. The customer facing agent in Japan would use a different database than the agent in Switzerland. The reporting group for finance might use a different database than the logistics group.

Different databases allow a company to find the best of breed application for any geographic area. This probably works great for individuals and small groups, but has problems when reporting is needed at the top. Reports must be created by merging all of the different data together. This requires very technical skills and a lot of time to do properly.

The data warehouse is another solution that is popular. The warehouse will normalize all needed from any number of different systems. This works well if the company has the money and resources to support that environment. Of course, what they are doing is creating a single source of data not unlike the single global database. Data warehouses can be expensive and difficult to maintain. They certainly have their value when done correctly, but starting with a single global database might be a better answer.

This is just my 2 cents; I’d love to hear your opinion.
Remember, it’s a global world out there, and technology makes it happen



1. sameer derashri - 06/15/2009

ur article was very informative.
i would like to know what parameters a company must cater before deciding to go for a single or a multiple databse.
will wait for ur response.

tboehm30 - 06/15/2009

I am not sure what you mean by “what parameters a company must cater”. I would however look at the cost and effort to create an actual GIS compared to what it would take for numerous local databases.

I think that is the biggest question – what is the effort. You need to coordinate many people around the world, you need a good hardware and software architecture; and you need a fantastic support staff.

If you are starting from scratch, why not plan everything from the standpoint that it will be global eventually.

Oh, and 2 more tips – 1) Start out with a Unicode setting; and 2) Use GMT on the server.

2. shubhasish ghosh - 09/03/2009

See I need to manage database for a multiple company and for every company there are multiple financial year.Can you please suggest me how I manage it in the database(SQL Server 2000)?will I create separate databases for different company and their different financial years???Or create different database for different company only and keep all the financial years result in that particular company’s database by finyrID.please suggest me.


tboehm30 - 09/03/2009

You need to find out the requirements.

You say there are multiple companies. Will management ever want reports that cover all companies (sales to a customer across any company, supplies bought from a vendor across any company, profit from a single product across any company, etc.)?

If so, then you will find it difficult to create those reports from separate databases. Even if you start out with the best of intentions and similar schemas, they will get changed and incompatible at some point.

You say they have multiple financial years. I assume that you mean over many years, but the same question arises: Will they need a consolidated report? If so, then you need a single database.

My guess is that you should have a separate database for each company. SQL 2000 will have no problem growing over time and tracking yearly results. All of your reports will simply rely on the accounting year. Make sure all of your table have enough date fields to cover the issue.

If you will need to consolidate companies, then you will wind up with a single database. In that case you will need to ensure that there are fields in every table to identify the company.

Good luck, and let me know how it goes.

3. upasana pardeshi - 10/20/2009

hello sir,gud evening there..
i am a student of B.E.(I.T.),have to submit the major project.my major project title is implementation of normal forms(1,2,3).i learnt java technology.this project is all about automated the burden of normalizing database upto 3rd normal forms.i don’t know that what will be the constraints or limitation of project n how to initiate it.plz help me out if u can…..
thanks in advance
plz do rply as soon as possible

4. Randell Closovschi - 04/03/2010

Hey, I found your blog while searching on Google your post looks very interesting for me. I will bookmark your site. Keep up the good work!

existing franchises for sale

5. Nabil Doctr - 02/08/2012

While customers, it’s a directly to make sure that people are generally dealing with a trustworthy business which usually works on the dependable repository protection supervision method.Bazy Firm Polskich

6. best security camera systems for home - 03/18/2014

Hello to every one, the contents present at this web site
are actually amazing for people knowledge, well, keep up
the nice work fellows.

7. ERP Systems - 05/20/2016

[…] in your business. The best thing is that Top ERP system integrates all the data and facts into a single database for simpler access and visibility. It will accommodate all your needs and reduce the complexities […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: