Comments
9 comments
-
Hey @giumaRE - quick question just to check, maybe a clone with that name doesn't already exist on that instance, but is there an already existing DB on that instance with the same name? Or any possibility of something similar?
Thanks! -
Hi,
No, nothing like that.
There are only five clones:
MarketingScrignoV2CreditcheckDWHChargeBack
I also checked querying sys.sysdatabases -
Interesting - so no clone (or non clone) DB doesn't exist on that Instance with the same name... is there a chance that there are some orphaned LDF/MDF files on the instance from a previous clone of the same name? Maybe one that was created before but not properly cleaned up?
-
nothing, no file
-
Is it possible there are some dirty data left in the SQLClone_Config database?
-
Are you able to attach the logs? I'm curious as to if this is a SQL Clone error or a SQL Server error - it could be the SQL Clone config DB, but I've only ever seen this come up as a SQL Server error.
Does it show the Clone DB with that name having been deleted from the Clones table in the config db? -
Please find attached the log file and a csv with the contents of the table Clones filtered for "Rete" DB
-
Hmmm I'm not entirely sure what is causing the issue from the logs, it doesn't say exactly other than there is already a DB with that name on machine "SQLPROVV-TEST"...
I would say you've got a couple of options - 1) you can raise a ticket with red gate support and see if they can help, or 2) you and I can take a look if you're happy to screen share - if you ping me a message on twitter PlantBasedSQL or with your email and you're happy to speak at 12pm BST or 5pm BST then I can ping you a google meet invite
Noting, of course, that 2) could invariably lead to 1) as I don't work for Redgate, but am a "Friend of RG"
Entirely up to you!
-
I'll open a ticket to Redgate and I'll keep you posted
Many thanks for your help
Add comment
Please sign in to leave a comment.
I'm receiving the error when I create the clone, but the clone not exist in the target SQL Server instance:
Is there a way to solve the error ?
Thanks a lot