One database or many for multicountry web application -

let's different points of view situation have.

i'm creating (asp.net) web application database (sql server express, max 10gb db size).

this application manages entities entities related countries, 1 country - many entities.

before anything, can't predict how db going grow. personal/hobby project i'm doing in free time.

my concerns if should create specific copy of database per country. reasons think are:

• size of databases smaller, won't have problems of size starting sql server express.
• again, db size. smaller per country, performance better.
• can maintenance tasks (backups, deployments) @ low peak time every country.
• in case of different laws protecting data per country can adapt each db specific law.
• customized text search per country. not problem because think create view per different country , text search of view.

then, if have 1 database countries there advantages:

• maintenance going simpler. 1 database means doing things once.
• no reduntant code. use stored procedures lot of web app. 1 change need published once in production.

god! writing down pros of each alternative seems make multiple database winner! seems single database lazy people...

anyway, i'd read more points of view, please guys, feel free contribute thinkings. thanks!

i choose 1 database.

for easier maintenance work. there 200 countries in world, if have database half of them. day want add column table , have change in every database going nightmare.(making sure don't forget 1 database or if mistype name, etc).

also, power/capacity of current computers, performance shouldn't problem. (unless it's important program).