I've tried to remove a replication between 2 databases on 2 different servers (both are SQL Server 2000).
The replication is completely removed from the publisher, however, the subscriber still has a link. I don't know very much about replication, so I hope someone can help me out here...
PUBLISHER has no traces
SUBSCRIBER I find a subscription in the Enterprise Manager under REPLICATION\SUBSCRIPTIONS:
The line sais:
If I run sp_dropsubscription on publisher site, it sais that the DB doesn't exist (which is correct since it was detached).
If I run sp_dropsubscription on subscriber site, I get 'The Publication does not exist.
How can I remove this subscription?
Thanks!
I was able to delete the subscription using the SQL Management studio (2008).
Related
Trying to get replication to work on MSSQL 2008, I am getting "The process could not connect to Subscriber" when viewing the synchronization status.
That happens on both of the servers defined on the replication (P2P replication).
I have went over the procedures of defining the replication over and over again, watched many video tutorials, but it still doesn't work. What am I missing?
Thank you!
I am new to replication. I have two sql server 2008 servers running on windows 2008 R2. The servers are in two different locations and on two different domains. I have been able to use aliases to get both "Snapshot publication" and "Transactional Publication" working perfectly. But what I need is "Transactional publication with updatable subscriptions" so if a change is made on either server, the changes are replicated to the other server.
When I run through the New Publication, I get through every page to the very end with no problem but when I click the finish button I get an error. There are three actions and it fails on the first action called "Creating Publication 'xxxx'" The message I get is "SQL Server could not create publication 'xxxx'. an exception occurred while executing a Transact-SQL statement or batch. The distributor has not been installed correctly."
I have searched for an answer and cannot find it. I think this is a permission problem between the two servers but I have no idea how to solve it.
Any help would be appreciated.
In my experience the installation of different types of replication over the top of one that was previously implemented can cause issues.
If able I would suggest clearing all replication and starting from scratch with your new approach.
You have to run a variety of stored procedures to get it completely off the server. Using the GUI only doesn't do nearly as good a job of cleaning everything off.
This guide from Microsoft should get you started.
http://msdn.microsoft.com/en-us/library/ms152757.aspx
I've been trying, googling and hitting my head against the wall but can't figure our what the problem is or how to solve it.
I have and SQL 2005 Standard server acting as a publisher. I need to do transactional replication to an SQL 2008 R2 Web server on another location.
I've set up the publication, and enabled FTP access to get the snapshot.
On the 2005 server when I launch replication monitor it keeps saying Uninitialized Subscription.
If I test this with a different subscriber that is running SQL 2008 Enterprise, it works fine.
Could it be because of the version? Could it be the SQL 2008 R2 Web can't work as a subscriber with SQL 2005?
Thanks,
Federico
Mixed versions are supported, but:
Distributor version must always be equal or newer than Publisher
Subscribers for transactional replication can be within 2 versions newer/older of Publisher
Subscribers for merge replication must be equal or older than Publisher
You need to troubleshoot to verify initial setup. I would suggest you to setup Replication using GUI
http://www.sql-server-performance.com/2010/transactional-replication-2008-r2/ (Should be similar in SQL 2005) as well
To do a clean installation please drop existing setup (Publisher, Subscriber, Distribution DBs)
How to cleanup Replication Bits - http://blogs.msdn.com/b/repltalk/archive/2010/11/17/how-to-cleanup-replication-bits.aspx
The comment listed below is from our SQL PFE. I am still trying to get some documentation.
"Publisher version must be equal to or greater than the Subscriber version."
I have been asked to write a SQL script that can be run, which will stop replication and remove the subscriber/subscription.
Is this at all possible? Or do you have to use the GUI?
Which version of SQL Server you are using.
Try
sp_removedbreplication 'DB_PROD'
go
Related Read - How to cleanup Replication Bits - http://blogs.msdn.com/b/repltalk/archive/2010/11/17/how-to-cleanup-replication-bits.aspx
Google as well provides MSDN article in results
How to: Disable Publishing and Distribution (Replication Transact-SQL Programming) - http://msdn.microsoft.com/en-us/library/ms147921.aspx
If you're look to completely remove replication, including all the "bits". Or your server only has one publication and this is the one you're trying to remove.
I would recommend:
Connect to the Publisher or Distributor you want to disable in Microsoft SQL Server Management Studio, and then expand the server node.
Right-click the Replication folder, and then click Disable Publishing and Distribution.
Follow the steps in the Disable Publishing and Distribution Wizard, and instead of processing select the option to generate scripts.
This has the advantage of not only completely cleaning things up. But also removing the distribution database, which if you've ever dealt with before is known to become littered with remnants of replications past.
Full documentation can be found here.
I have a main SQL Server, running SQLServer 2000, with two (in theory) subscribing servers, each running SQL Server 2005.
One of these is subscribing fine, but the other always seems to fail subscribing, both when attempting to set up the subscription from the publisher (SQL2000) to the subscriber(SQL2005), and when trying to set it up from the subscriber to the publisher, both via Server Management Studio 2008 and via SQL Enterprise Manager
In both cases, the publication is created on the publisher, but a corresponding subscription is not created on the subscriber.
I then get an error message saying "The process could not connect to Subscriber [ServerName]", and no more sign of activity. There's no problem with logins, permissions, etc. The password for sa is the same on both machines, and is different on the 2005 machine that works.
Is this a problem anyone else has encountered?
EDIT: I've now tried adding both a dbSubscriber and a dbPublisher access account on each server so that they're not logging into each other using "sa", but it doesn't seem to have made any difference.
EDIT2: Adding a push subscription does not create a Local Subscription on the subscribing server. Is this normal, or is this the point at which everything is falling to pieces?
Thanks for posting an update, always good to know how things turned out.
There are "complications" and intracacies involved when creating SQL Server Replication topologies incorporating different versions of SQL Server, as it sounds like you are discovering.
Keep in mind that Replication functionality is limited to that of the oldest version of SQL Server in your topology:
Using Multiple Versions of SQL Server in a Replication Topology
We don't really understand what was going wrong, but we think that the 2005 server was unable to accept the 2000 server as a Push Publisher.
We created four different Pull subscriptions on the 2005 server and the first three failed, while the fourth magically worked.
We are accepting this as a blessing from the God of Computers and will not question His benevolence.