I need to set up a mechanism for transactional replication with "n" publishers and a subcriber. In this way I thought of putting a single database ditribution.
I would like to know if there are problems between versions of ditribution and publishers; for example, I can have a publisher created with MSSQL 2005 and distribution database created in MSSQL 2012?
Thanks,
Francesco
Your needs have been anticipated: MSDN documentation.
Quoting the article:
For all types of replication, the Distributor version must be no
earlier than the Publisher version. (Frequently, the Distributor is
the same instance as the Publisher.)
For transactional replication, a Subscriber to a transactional
publication can be any version within two versions of the Publisher
version.
It would seem that your topology meets the requirements. Build it in test though to make sure you don't have any surprises.
Related
Are there any SQL Server Replication Best Practices? Are there any links I can read up on?
I’m using 2012 and 2014. I want to know, in general, what type of database objects typically people replicate
from the source instance (publication) to the target instance (subscription)? Table is definitely one of them.
If there are a lot of views associated with the source database and probably not being used in the replicated
database (target/subscription), should I include them in the replication process? What about stored
procedures? In both cases, would it be better just to replicate the data and manually deploy the views and
stored procedures? I’d like to get some ideas/suggestions? Thanks
Here are some resources that cover replication best practices and improving performance:
Best Practices for Replication Administration
Enhance General Replication Performance
You can find a list of database objects that can be published using Replication here:
Publish Data and Database Objects
If the objects are being used at the replicated database (subscriber) then yes, you should replicate the objects. If not, feel free to exclude them from the publication.
The benefit of including them in the publication, rather than manually deploying them, is that replication supports schema changes to published objects and when you make schema changes on appropriate published objects at the Publisher, those changes are propagated by default to all Subscribers. This is covered in Make Schema Changes on Publication Databases.
I need to perform replication on MS SQL Server 2005 Standard Edition. The goal is, that I have several databases (for example 4 instances of SQL Server) and each must act as publisher to other sites. I know, that merge replication model of subscriber - publisher - subscriber is possible, but it doesn't suit me. I need to maintain replication process between other machines when no matter which server is down, so all other servers will have actual data.
Is it even possible? And if yes, can You point me to something?
Thanks in advance.
It sounds like you're describing peer-to-peer replication. Read up on it here.
I need to use replication between my databases. But me hosting provides only Web Edition of SQL Server. In web edition replication is not supported. May be anyone have some suggestions?
Thanks
If you are savvy with programming then you can accomplish a very slim form of replication through code. If not, you might be out of luck.
You can have DML triggers on your tables that you would normally have as articles for replication, and when the data changes log it to a table with the necessary information. Then have a scheduled task that runs an application to push those changes to the logical subscriber(s). Just an idea, but it looks like you may have to get creative.
Is it possible using SQL Server Replication to replicate data to AND from (bi-directional) Oracle and SQL Server? The schemas are completely different. In real-time would be a bonus.
Have already investigated Oracle Golden Gate, which seemed to do the job, although the licence cost is not insignificant!
I wondered if anyone has had any experience in replicating data across different schemas, and what other tools they employed? I realise this is a bit of an open-ended question but any advice and previous experiences would be most useful.
Thanks
Duncan
I recently had to create a solution to import periodically lots of data from different databases (most of the time from Oracle databases) to a SQL Server database (a data warehouse). To do so, I used SQL Server Integration Service to create a package able to import, transform and insert the data as I wanted (since it was from heterogeneous sources too). This software comes with SQL Server and the version 2005 and superior is really easy to use (graphical programming). In your case, you could trigger your created services when needed. I am not sure it is the best solution since you would need to create a SSIS service for each direction (from Oracle to SQL Server and from SQL Server to Oracle).
I have 2 similar tables in different servers, data in certain columns can only be changed by server A while data in other columns can only be changed by server B.
However, I need these tables to always be consistent (1 minute schedule). Is this the kind of scenario that "Transactional replication with updatable subscriptions" solves?
You want merge replication.
YEs, updateable subscriptions allow for this, but that is a deprecated feature:
This feature will be removed in a
future version of Microsoft SQL
Server. Avoid using this feature in
new development work, and plan to
modify applications that currently use
this feature.
The way going forward is Peer-to-Peer Replication.