I would like to have the agent run a script that after cloning, it detaches the database and then attaches it again with some modifications. As of now this is not possible as the agent tries to attach the database immediately when it has been detached. Is it possible to configure the agent so that it does not automaticaly try to attach the database when it has been detached?
Comments
2 comments
-
To add on to this the solution we had to use was to shut off the service of the SQL Agent on the instance where it had created a clone to bypass the windows error that the file was being used.
-
Hi, thank you for your forum post.
May I ask what modifications you are looking to apply?
It is possible to make modifications during the create Clone process, further reading in this help document.
Better still, modify the image during the Image creation step, as per this help document.
There is no configuration you can make to the SQL Clone Agent to prevent it from automatically attach to the Clone.
Also, any modifications you make to the Clone post the creation of the Clone, will cause the differencing disk to inflate which may inflate to a size bigger that the original database, depending on what you are modifying.
Many Thanks
Eddie
Add comment
Please sign in to leave a comment.