Architectural Scenario #653 - SQL Server Replication
When I first got to my current job the setup was two production database servers that had over 100 databases between them. Data was imported every morning from files that dropped in a folder by our headquarters that were in zip files. The data import job was set to run at a specific time and imports the data into a database that existed on both servers. This is the main database that is referenced by all the other databases. So the import job would import the data into the database on one server then copy the data to the other server once it was finish with the first one. I thought this was crazy.... Needless to say we had problems. If the files are late being dropped the ETL import job would fail. If the first import failed the other server would not get updated. This was a 1980s setup. People there is something called "Replication". I was told SQL Server Replication has problems, it's too difficult to setup and support, backups and restores will be horrible, etc