April 13, 2012 at 12:41 pm
Just curious to see if this is something that's possible to do. I'd imagine that there should not be any problems, since you can do the same with 2005 to 2008, perhaps I've overlooked something? This will be for transactional replication.
April 13, 2012 at 2:09 pm
Yes, this is possible.
May 8, 2012 at 2:09 pm
The link that the responder answered with has nothing to do with the question that was asked.
May 8, 2012 at 2:13 pm
Did you read anything from the link?
The 3rd bullet point in:
Subscriber version depends on the type of publication:
A Subscriber to a transactional publication can be any version within two versions of the Publisher version. For example: a SQL Server 2005 Publisher running can have SQL Server 2012 Subscribers; and a SQL Server 2012 Publisher can have SQL Server 2005 Subscribers.
May 8, 2012 at 2:29 pm
Yes, sorry, I did miss that bit.
Might want to also include the following, as merge is an exception: "A Subscriber to a merge publication can be any version less than or equal to the Publisher version."
February 21, 2013 at 1:48 am
I must be missing something. I have just finished rebuilding my publishing sql server on sql server 2008 r2. When I try to add one of my sql server 2012 servers as a subscriber I get the following error message:
The selected Subscriber does not satisfy the minimum version compatibility level of the selected publication.
The publisher is 2008 R2 SP2 and the subscriber is 2012 SP1.
Bill Soranno
MCP, MCTS, MCITP DBA
Database Administrator
Winona State University
Maxwell 143
"Quality, like Success, is a Journey, not a Destination" - William Soranno '92
February 21, 2013 at 8:53 pm
I am not sure but I suspect that the distributor you are using is SQL 2008 R2. Normally, I would expect the distributor to be the most recent version of all of the SQL servers involved (in your case, this would mean that your distributor should be SQL 2012)
February 25, 2013 at 5:12 am
There are some issues if you connect to SS2012 (Subscriber) with SQL Management Studio 2008 or 2008 R2 (Publisher/Distributor).
Try with stored procedure or with SQLCMD
DECLARE @publication AS sysname;
DECLARE @subscriber AS sysname;
DECLARE @subscriptionDB AS sysname;
DECLARE @frequency_type as int;
DECLARE @subscriber_security_mode as int;
DECLARE @subscriber_login AS sysname;
DECLARE @subscriber_password AS sysname;
SET @publication = ______________ ;
SET @subscriber = ________________;
SET @subscriptionDB = _______________;
SET @frequency_type= ___ ; --(you must check frequency type)
SET @subscriber_security_mode= ___ ; --(you must check security mode)
SET @subscriber_login=______________;
SET @subscriber_password=__________; --(if security mode is 0, SQL Server authentication)
--Add a push subscription to a transactional publication.
USE [DBName]
EXEC sp_addsubscription
@publication = @publication,
@destination_db = @subscriptionDB,
@subscription_type = N'push';
EXEC sp_addpushsubscription_agent
@publication = @publication,
@subscriber_db = @subscriptionDB,
@subscriber_security_mode=@subscriber_security_mode,
@subscriber_login=@subscriber_login,
@subscriber_password=@subscriber_password,
@frequency_type = @frequency_type,
@job_login = ___________,
@job_password = __________;
GO
February 25, 2013 at 7:10 am
Using the sql script worked.
Thanks
Bill Soranno
MCP, MCTS, MCITP DBA
Database Administrator
Winona State University
Maxwell 143
"Quality, like Success, is a Journey, not a Destination" - William Soranno '92
May 21, 2014 at 8:38 am
Apparently if you just use SSMS from the subscriber (SQL 2012) side, you won't get the error:
http://www.keepitsimpleandfast.com/2013/07/the-selected-subscriber-does-not.html
October 28, 2015 at 11:33 pm
Thanks, its helpful for me to proceed further in my work.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply