Comments
Sort by recent activity
@RichardMGreen I think the easiest way around it (without using Data Masker) is to copy or restore a backup of the DB first using DBATools or other similar method via PowerShell, then run the modification scripts, then create the Image from that copy of the DB. This could at least have the unintended benefit of ensuring all transactions were completed before creating the image meaning they won't be replayed against the clones... / comments
@RichardMGreen I think the easiest way around it (without using Data Masker) is to copy or restore a backup of the DB first using DBATools or other similar method via PowerShell, then run the modif...
@RichardMGreen Q1 - are you creating the image from a backup file or from a live DB copy and Q2 - are you also using Data Masker for any obfuscation of the Image data? / comments
@RichardMGreen Q1 - are you creating the image from a backup file or from a live DB copy and Q2 - are you also using Data Masker for any obfuscation of the Image data?
Hey kr_DBA I'm pretty sure it should all be fine, so long as (just like on prem) SQL clone has all the network connectivity, ports open, credentials etc. Etc. I have seen SQL Clone in use on AWS and Azure Vms before, so I don't see why GCP would be any different. The documentation site (documentation.red-gate.com) has a fair architecture diagram and networking/permissions documents so as long as you stick to that you're good 👍 Hope you get on ok! / comments
Hey kr_DBA I'm pretty sure it should all be fine, so long as (just like on prem) SQL clone has all the network connectivity, ports open, credentials etc. Etc. I have seen SQL Clone in use on AWS an...
Hey @tdobe have you tried right clicking and hitting view history on the object itself, as opposed to top level on the database? It's been a while since I used SQL Source Control, but from memory it should just give you the history for that one object. / comments
Hey @tdobe have you tried right clicking and hitting view history on the object itself, as opposed to top level on the database? It's been a while since I used SQL Source Control, but from memory i...
Hey @darrenpMB if you've deleted the VHDX image files from the fileshare and the only issue is them still hanging around in the UI and not deleting - you could probably just update the status in the dbo.Images table in the SQL Clone Config DB to show as deleted and then refresh and it should be all good! I'd take a quick backup of the DB before making any changes though. Only other option is i'd say open up a support ticket with redgate support who might have a better answer [image] / comments
Hey @darrenpMB if you've deleted the VHDX image files from the fileshare and the only issue is them still hanging around in the UI and not deleting - you could probably just update the status in th...
@vvt when you use SQL Source Control you're using the state based source control process, so naturally the build artifact from the build will be the whole DB (the state of it, as it is in source control) You then need to use SQL Change Automation in whatever deployment tooling you're using (Octopus or Bamboo or ADO etc.) to generate a deployment (or "release") artifact from your build artifact (.Nupkg) which will generate the diff upgrade script plus any drift reports against the target. It should go: DB -> VCS -> Build (produces NuGet Package) -> Release Artifact (folder including drift checks and a target deployment sql script) -> Deploy from release artifact This is because a comparison needs to happen between the accepted (and correctly built) state of the DB from the build which resides in the Nuget, and the target DB you're deploying to. / comments
@vvt when you use SQL Source Control you're using the state based source control process, so naturally the build artifact from the build will be the whole DB (the state of it, as it is in source co...
Hey @JonathanC my understanding is that if you leave the descriptions just in SQL Doc and don't save to DB then it'll just be saved within the SQL Doc project itself. However if you hit "save to database" I believe that it will write the description to the MS_DESCRIPTION extended property for that object. / comments
Hey @JonathanC my understanding is that if you leave the descriptions just in SQL Doc and don't save to DB then it'll just be saved within the SQL Doc project itself. However if you hit "save to da...
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" [image] Entirely up to you! / comments
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 coup...
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? / comments
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 err...
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? / comments
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 o...