Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Urgent Questions about Replication and Partition table Expand / Collapse
Author
Message
Posted Thursday, April 24, 2008 12:49 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, April 28, 2008 4:10 AM
Points: 2, Visits: 6
Question1:
I have 3 database on a same server. And databaseA and databaseB both have a table call
T1 and the structures are same.
Now I want to replicate databaseA.T1+databaseB.T1 in DatabaseC . I heard in SQLServer2005, there is an option call merge replication , Can anyone give me a hint?

Question2:
I used to work with partition table in Oracle . In SQLserver2005, how do we realize partition table ? I mean a table stored in 2 partition , and when the SQL inquiry one partition , the performance is getting better .
Post #490228
Posted Sunday, April 27, 2008 8:32 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, April 28, 2008 4:10 AM
Points: 2, Visits: 6
DTS is a kind of available option?
Post #491128
Posted Monday, April 28, 2008 1:46 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, February 27, 2014 3:44 AM
Points: 179, Visits: 331
Answer to Q1:
Merged replication is somewhat different to what you presume. The Merged replication allows to update the Primary server from the secondary when any change occurs in it. It has nothing to do with merging databases.

You can implement your plan, using DTS in SQL 2000 or SQL Server Integration Service from SQL 2005 onwards. Note that you can schedule the transfer as easily as in a replication.

Hint: You can have triggers, which keep track of inserted, updated or deleted data in a table for the duration post execution of the job upto the time of execution. In the job, you can just insert the inserted, update the updated, and delete the deleted. You can also have a separate table to log the changes happened and the changes applied.

Hope this helps.


Chandrachurh Ghosh
DBA – MS SQL Server
Ericsson India Global Services Limited
Quality is not an act, it is a habit.
Post #491225
Posted Monday, April 28, 2008 1:56 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, April 16, 2014 4:45 AM
Points: 2,385, Visits: 1,843
If you would like to resolve your issue with Replication here is the solution:

Use Transactional replication to replicate data from
A.T1 to C.TA
B.T1 to C.TB

Create View T1 combining C.TA & C.TB.

For Partition refer following site:
http://msdn2.microsoft.com/en-us/library/ms345146.aspx#sql2k5parti_topic23

Hope this will help. Good Luck!


---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
Post #491227
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse