How to move AG(Availability Group) databases to new location

Question

Post reply

How to move AG(Availability Group) databases to new location

aashish.lg

SSC Veteran

Points: 287
More actions
June 27, 2015 at 7:40 am

#318517

I would like to move my AG databases to new location using C#.
I found article on MSDN which uses SQLCmd utility to do that, but I cant run that utility from my application.
I am looking for general steps OR T-SQL if possible so that I can follow the same from my C# application.
Regards
Ashish

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

JManuelN SSCommitted Points: 1708 More actions · Answer 1

Hi Ashish,

Could you post the URL of the MSDN article that explains the procedure?

Additionally. Do you need to change the database location for the primary and the secondary replicas all together or just one secondary replica?

Best regards,

aashish.lg SSC Veteran Points: 287 More actions · Answer 2

Below mention is the MSDN URL..

http://blogs.msdn.com/b/sqlserverfaq/archive/2014/02/06/how-to-move-databases-configured-for-sql-server-alwayson.aspx

I would like to change the mdf and ldf file path of AG Databases in all the replicas.

Justin Manning SA Hall of Fame Points: 3190 More actions · Answer 3

Are you doing this as a form of Automation?

Just want to understand why you need to use C#?

aashish.lg SSC Veteran Points: 287 More actions · Answer 4

We are writing the code for managing SQL server instances from the centralized server.

This is in the interest of storage domain solutions fro SQL server.

We migrate DB to our storage drives from the centralized server.

Regards

Ashish

Justin Manning SA Hall of Fame Points: 3190 More actions · Answer 5

Have you looked at using PowerShell at all?

This can be called from within your C# application and PowerShell has AlwaysOn assemblies you could use for the database manipulation?

http://blogs.msdn.com/b/kebab/archive/2014/04/28/executing-powershell-scripts-from-c.aspx

https://msdn.microsoft.com/en-us/library/ff878391.aspx

Maybe incorporate The SQL Scripts you mentioned in your link:

http://blogs.msdn.com/b/sqlserverfaq/archive/2014/02/06/how-to-move-databases-configured-for-sql-server-alwayson.aspx

I'm guess your challenge is the SQLCMD commands in the T-SQL Statements,

i.e. connect noode1:

JManuelN SSCommitted Points: 1708 More actions · Answer 6

Hi

Sorry but I do have a test environment with me now but I think that you could try creating temporary linked servers on a master instance and then replace the SQLCMD connect command to other servers on the blog example by using the EXEC ('SQL CODE') AT [Linked Server]

I hope that helps.

Dynamic SQL execution on remote SQL Server using EXEC AT

http://www.mssqltips.com/sqlservertip/1757/dynamic-sql-execution-on-remote-sql-server-using-exec-at/[/url]