Dead links

Hi.
In report manager, links to Home, My subscription, Site settings, Help,
Contents, Properties works fine.
But links to New Folder, New Data source and Upload files are completly
dead - what could be wrong?
I'v installed evalution edition incl. SP1.
Best
LABProblem solved, it was a matter of browser-sequrity.
/LAB
"LAB" <nomail@.nomail.dk> skrev i en meddelelse
news:#NLIMzXnEHA.2680@.TK2MSFTNGP15.phx.gbl...
> Hi.
> In report manager, links to Home, My subscription, Site settings, Help,
> Contents, Properties works fine.
> But links to New Folder, New Data source and Upload files are completly
> dead - what could be wrong?
> I'v installed evalution edition incl. SP1.
> Best
> LAB
>

Deactivating Replication

Hi,
We have a set up of Transactional replication, with Pull subscription. I want to deactivate the replication. How do I do it? Will stopping the Log Reader Agent suffice? I know the subcription will be deactivated after 72 hours. What do I need to do to the Publisher? How do I deactivate it?
Any help is appreciated.
Thanks.What do you mean about deactivating replication? Do you want to drop a subscription or you want to drop everything(publication and subscription)? Or you just want to stop it for a while?|||I want to stop subscription for a few months before eventually dropping everything-Publication and subscription.
I know the subscription will be inactive after 72 hours. Do you think its a good idea to stop the log reader? We can always start it to perform a one time synchronization if required.

I think I have figured out how to disable the publication... In SQL EM, select the Publisher, right click on the replication and "Disable Publisher" and follow the steps..

Do the same on the distributor......

Is that right...Am I missing any steps?

Thanks for your help.|||If a few months is the duration, I would suggest that you drop the subscription and the publication. Not only because SQL expires replication agents but having replication setup would make DDL changes harder. If you want to keep the replication setup, you can script it. A few months later if you decide to install it, you can just run the script and the replication should be back up and running, assuming you keep up with all the changes in the database.

When dropping the replication, remember to drop subscriptions first and clean all the jobs in the subscriber, then drop the publication. You can use the Wizard to do that.

Hope this helps.|||Thanks a lot for the advice, that sounds good!!

Deactivated?

Merge replication.
Push New Subscription.
Immediately after I click "finish" in the wizard (push new subscription),
the subscription status shows deactivated. The merge agent runs and
completes then shows status has failed. error = "the subscription to the
publication pub_name is invalid. The remote-server is not defined as a
subscription server. 14010"
Your problem is that the remote server is not enabled as a subscriber. I'm
not trying to be flippant, but this might take a little back and forth to
fix.
First off - all publications/subscriptions are marked as deactivated until
the snapshot agent runs. So this status is not problematic in your case.
To enable your subscription server as a subscriber, go to tools,
Replication, Configure Distributor, Publishers, and Subscribers, click on
the subscriber tab, locate your subscriber or register it.
You might also want to review this pdf -
http://www.nwsu.com/lowres_replication_ch02.pdf
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
news:%23cKdOIoAFHA.904@.TK2MSFTNGP12.phx.gbl...
> Merge replication.
> Push New Subscription.
> Immediately after I click "finish" in the wizard (push new subscription),
> the subscription status shows deactivated. The merge agent runs and
> completes then shows status has failed. error = "the subscription to the
> publication pub_name is invalid. The remote-server is not defined as a
> subscription server. 14010"
>

Deactivate Subscription status

Hi,
I have a transaction replication b/w two servers. In the publisher's subscription list status,it displays deactivated.
The Replication is stopped because of this, i am not able to change the status.
What to do ? Please let me know.
Kumaran,
Subscriptions can be deactivated or can expire if they are not synchronized within a specified period of time. If this shouldn't have happened then you might want to increase the subscription expiration property of the publication and the maximum transact
ion retention property of the distribution database for the future. For now, you'll need to reinitialize.
HTH,
Paul Ibison

DDL Still Replicates Even With DDL Replication Off (@replicate_ddl = 0).

There are times when we need to make DDL changes and have them NOT replicate to the subscription database. The documented approach is to disable DDL replication using sp_changepublication (replicate_ddl = 0). See http://msdn2.microsoft.com/en-us/ms147331.aspx

However, our DDL still replicates even when following those steps. I've even tried the very simple steps below to reproduce the error.

Set up transactional replication of one small test table. Replication is working fine. Set @.replicate_ddl = 0 with sp_changepublication. I manually verify the setting (using the GUI) before continuing. Run a simple alter on the publication DB; change one column from varchar(25) to varchar(30). "ALTER TABLE <tablename> ALTER COLUMN <colname> VARCHAR(30) NULL". The DDL still replicates. The subscription table still has the column altered to the new definition.

I've even tried manually setting the option in the GUI and also stopping and restarting the synchronization after changing the setting; nothing works.

We are using SQL Server 2005 and just upgraded to SP2 a few days ago.

I have not found any other articles/postings on the topic so it appears we are the only ones having this problem. If anyone has any advice or input, it is greatly appreciated.

Regards,

Adam

Adam;

This turns out to be a problem with MS SQL Server Management Studio. When you upgraded your SQL Server 2005 to SP2 you did not upgrade your local copy of MS SQL Server Management Studio to SP2.

To fix this upgrade your local MS SQL Server Management Studio to SP2 and recreate your replication.

HTH

Paul