Skip to main content

How to remove SQL clone agent from a server that is powered down

Hi guys!

As you know, in my environment I use Redgate SQL Clone.

You can check out an older post I have here on what you can do with the SQL Clone application.

Today's post is on how to remove SQL Clone agents from a server.

Let's get started.

I. Remove a clone agent from a server that is still online

Removing a clone agent from a server that is already online is relatively easy.

Just remote desktop into your server > under services, stop the "SQL Clone Agent version#" service.

stop the SQL Clone service









Then under control panel, uninstall "SQL Clone Version#".

Uninstall SQL Clone from the control panel



















II. Remove a clone agent from a server that is offline.

Here's how to remove SQL Clone from a server that has already been shut down.

Note: This method will also work on servers that are still online. Log on to the server and open a powershell window/prompt as administrator. Use the script below.

Inside your powershell prompt enter: Connect-SqlClone -ServerUrl 'http://yourURLserver:URLappPort#' 

Note: You will need to update the URL server and port # to your own URL server and port#.

 Hit Enter.

 Then on the second line, enter: $AgentToDelete = Get-SqlCloneMachine -Name 'machine name'

 Note: you will need to update 'machine name' to the name of your server.

 Hit Enter.

 Then on the third line, enter: $AgentToDelete

 Hit Enter.

Lastly, enter: Remove-SqlCloneMachine -Machine $AgentToDelete

Now you can confirm your agent has been removed from your dashboard [http://yourcloneserver:port#/settings/agents].


If you have any questions related to this post, please put them below.

Thank you and Happy reading,

-marshé hutchinson
#learnSQLwithme
Labels:

Comments

Post a Comment

Popular posts from this blog

Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 199 The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).

Hi guys! Here's another quick and easy post. Scenario I was trying to copy a SQL agent job from one server to another by just copying the script of that SQL job. You can copy any script by right clicking a job > Script job as > create to > new query window. I pasted the job on a different server and tried to execute it and received this error: Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 199 The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]). This error message is simply saying for the variable '@owner_login_name', the user account associated with the variable is incorrect because it does not exist. Fix Simply update the variable for '@owner_login_name' to a valid user account for the current SQL instance. Now when you execute the script again to create the SQL agent job your results will be: Command(s) completed successfully. If you have any furt...
2 comments
Read more

Executed as user: . Incorrect syntax near ''. [SQLSTATE 42000] (Error 102). The step failed.

Hi everyone! Today's post is about an all too common problem... syntax issues. Whether you fat-finger your keyboard or are always in a rush, chances are you have already encountered many syntax errors. But if you are a newbie,  your syntax error is just around the corner. No worries, this is an easy fix. Syntax errors just let you know part of your code or script is incorrect. Scenario I have a SQL agent job that is using the SQL command line to perform index maintenance, but it is failing. Here's my code : sqlcmd -E -S $(ESCAPE_SQUOTE(SRVR)) -d master -Q "EXECUTE dbo.IndexOptimize @Databases = ' databaseName ', @FragmentationLow = NULL, @FragmentationMedium = 'INDEX_REORGANIZE,INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE', @FragmentationHigh = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE', @FragmentationLevel1 = 5, @FragmentationLevel2 = 30, @UpdateStatistics = 'ALL',@WaitAtLowPriorityMaxDuration = 180, @WaitAtLowPriorityAbortA...
Post a Comment
Read more

How to export SQL agent jobs from your SQL Server instance

Hi everyone! As a database administrator, you always need a copy of your data and data processes for: migrating servers disaster recovery backup procedures/best practices This post covers a simple Powershell script. The script is to take a backup of all the SQL agent jobs on your SQL server instance. If you ever needed to recreate all the jobs on another server, all you would have to do is execute the SQL script. I. In SSMS (SQL Server Management Studio), create an empty .SQL file and save it with this naming convention: I.e. SqlAgentJobs_PROD01.sql } This file will represent all the SQL agent jobs on the primary production SQL server. II. Copy the "SqlAgentJobs_PROD01.sql" file from above to a network share. III. Run the Powershell script below in  Powershell ISE as administrator: ##migrating jobs from one server to another with the replace command $SqlConnection = New-Object System.Data.SqlClient.SqlConnection $SqlConnection.ConnectionStrin...
Post a Comment
Read more