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.

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

Comments

event id 101 task start failed - task scheduler event id 101 launch failure

Hello again. This post is related to automating SQL server tasks with Task Scheduler. In this example I was tasked with exporting SQL server agent jobs twice a month. To achieve this, I setup a task scheduler task that ran a PowerShell script that: establishes a local connection to the SQL server. cleans the file before writing to the .sql file to avoid adding on (appending) results on subsequent runs of the task scheduler task. when a connection is established, export the SQL agent jobs on the server to a .sql file on a remote server. sends a confirmation email via the SQL server database mail profile that the SQL agent jobs were exported to the specified remote server path. That was a mouthful. Now that you know my task scheduler task is calling a PowerShell script, let's get back to why it is failing. The good news is this error is not related to the script. The error launch failure means the task could not even run. This is most likely due to a permissi...

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

Database "" database is not in full recovery mode on each of the server instances. The full recovery model is required for a database to participate in database mirroring or in an availability group. [SQLSTATE 42000] (Error 1465).

Hi there. This post will be a quick and easy fix. If you are not already aware, availability groups are the replacement for mirroring in SSMS (SQL Server Management Studio). We like to utilize availability groups so that there is minimal data loss. Also, in the event of some natural disaster or disk failure on a server that is participating in an availability group, the data will fail-over to a backup server (replica). I was adding a database to an availability group when I received the error: Database "database_name" database is not in full recovery mode on each of the server instances. The full recovery model is required for a database to participate in database mirroring or in an availability group. [SQLSTATE 42000] (Error 1465). The error is exactly as it sounds; The database is not in the full recovery model. To fix this: I. In SSMS, right click the database to see the properties. On the Options page, change the database recovery model to Full. II....

learnSQLwithME

Search This Blog