Showing posts with label deactivate. Show all posts
Showing posts with label deactivate. Show all posts

Thursday, March 8, 2012

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!!

Deactivating Admin and Domain-Admins

Hello,

is it possible to deactivate the groups admins and domain-admins in sql server without getting in trouble with the sql-server. For example when the system boots the program should start normally without any problems.

We want do deactivate the accounts because we have some critical information in sql server and dont want to give all admins the possibility to have a look at these data.

We just want to have sa within the role sysadmin.

Regards
Franz

You can drop the BUILTIN\Adminstrators group from the sql logins. Make sure you have the password to sa as you don't want to leave yourself with no sysadmin login.

Remember, if you're using SQL Agent, the service account it runs under does need to be a sysadmin in sql.

HTH!

|||Thank you for the answer.

Yes we are using the SQL Agent. If i give the account the role sysadmin, an administrator has the possibility to give it an new password and can then see all information.

Is there really no chance to deactivate the accounts?

We also have an SQL Cluster is there any further account needed?

If i have no chance to deactivate those accounts generally without giving some special acoounts the sysadmin role, is it a method to deactivate the accounts and when i have to reboot or start the services to give them temporarely the sysadmin role?

Regards
Franz
|||

The SQL Agent Service is a sysadmin by design. In a future version we may be able to modify the design to make SQL Agent not have to be a sysadmin but that doesn't help you today.

Removing builtin\administrator is probably the best you can do.

HTH,

-Steven Gott

SDE/T

SQL Server

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