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 2005 Forums
 Replication (2005)
 Many-to-One Replication - One Way

Author  Topic 

dkonefal
Starting Member

3 Posts

Posted - 2008-12-30 : 17:16:45
Hello,
Our company has multiple regions. All regions are running the same application, with data on their own SQL 2005 server (all servers are in the same building). The database name and table structures are identical on all servers. I would like to create a consolidated database for reporting purposes only. I have considered merge replication - the concern is that the consolidated data should only exist on the reporting server, not all servers (in other words, it needs to be one way only).

I started down the path of replicating data from each source server to its own database on the target server, then using triggers to update the consolidated database. This works fine, except that when replication is re-initialized the triggers are deleted. Although I can create a recovery process, I do not have 100% confidence in the process. Any suggestions for an easier way to do this?

Thanks.

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-12-31 : 22:40:38
Perhaps your explanation is not clear so we can help you. Why Merge Replication when you need one-way?
Go to Top of Page

dkonefal
Starting Member

3 Posts

Posted - 2009-01-02 : 09:04:12
I am not sure what additional information you need. As I said, I had considered Merge Replication and decided that is would not work, as I need one way. I had also considered log shipping, but I have to exclude some legacy data from each of the servers. I appreciate the help, I thought I was clear but apparently was not. What other information can I provide that will help clarify?
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2009-01-02 : 12:48:42
Why don't you consider Transaction replication?
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-01-02 : 13:06:53
I agree that transactional replication should be used here. Do not use triggers for this.

We use transactional replication for all of our reporting needs.

Log shipping can't be used as each time it does a restore, all users will need to get disconnected.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

dkonefal
Starting Member

3 Posts

Posted - 2009-01-02 : 16:02:06
Thanks for the advice, I will look into using transactional replication.
Go to Top of Page
   

- Advertisement -