Activity overview
Latest activity by RichardMacaskill
Hi Teri,
As long as your team is licensed for SQL Clone, you don't need an additional license for the build server.
Details are toward the bottom of this page https://www.red-gate.com/products/dba/sql-clone/
Explicitly, entitlements are not required for "Contributing changes to an automated process which use database clones".
hope this helps
Richard / comments
Hi Teri,
As long as your team is licensed for SQL Clone, you don't need an additional license for the build server.
Details are toward the bottom of this page https://www.red-gate.com/products/dba/...
Hi Teri,
As long as your team is licensed for SQL Clone, you don't need an additional license for the build server.
Details are toward the bottom of this page https://red-gate.com/products/dba/sql-clone/
Explicitly, entitlements are not required for "Contributing changes to an automated process which use database clones".
hope this helps
Richard / comments
Hi Teri,
As long as your team is licensed for SQL Clone, you don't need an additional license for the build server.
Details are toward the bottom of this page https://red-gate.com/products/dba/sql-...
You just download and install the upgrade on the server. The agents take care of themselves with a silent update (you can check on their progress in the Machines tab of the SQL Clone web application).
We'll look at making this clearer in the documentation.
Thanks for posting, Mattias.
Richard / comments
You just download and install the upgrade on the server. The agents take care of themselves with a silent update (you can check on their progress in the Machines tab of the SQL Clone web applicatio...
Appreciate the suggestion Mattias. We had a user story around 'more reporting, visibility of state', which we've added this to, and this will help us guide the prioritisation. Can I ask how you would use that cmdlet? Is it for a report or as part of a larger workflow?
thanks
Richard (Product Manager for SQL Clone) / comments
Appreciate the suggestion Mattias. We had a user story around 'more reporting, visibility of state', which we've added this to, and this will help us guide the prioritisation. Can I ask how you wou...
Hi 3kernodle,
We can't see a reason transactional replication wouldn't work -the SQL Server engine sees a clone database as a normal database - but we haven't tested that yet.
It might be a setup that needs careful management though; transactions posted into the SQL Clone database would be written to the differencing disk which is local to that SQL Server instance (in its default data directory).
So leaving replication running on the same clone database could cause that file to inflate to the extent that much of the benefit of using a clone database is lost.
It might work to have a clone database which is configured to be a replication subscriber, which is then refreshed daily (dropped and recreated from a new, more recent image).
I expect you would need to be able to add and remove the subscription for that database programatically in order to make that manageable.
Sorry for the delay in getting back to you, I was hoping to get a worked example in place - and possibly a blog post - before weighing in on it. I still hope to do so in the near future.
hope this helps
Richard
(SQL Clone Product Manager) / comments
Hi 3kernodle,
We can't see a reason transactional replication wouldn't work -the SQL Server engine sees a clone database as a normal database - but we haven't tested that yet.
It might be a setup t...
Hi Mattias,
Thanks for your post.
As you're using Octopus, I'd definitely point to the new difference report that SQL Release creates. It has a new look and feel (intra-line diff similar to GitHub, better navigation), and also includes static data changes, so combined with SQL Source Control's static data can support change control for data as well as schema (I blogged about it here; http://www.red-gate.com/blog/change-control ).
If you're using DLM Dashboard to guarantee the integrity of your build pipeline, and to alert you on out-of-process changes, you can now also use the SQL CI Build step to send your packages and version names direct to DLM Dashboard. If not, please do give DLM Dashboard a try. There are lots of exciting improvements in the pipeline as well.
We've also improved lots of aspects of the getting started experience by simplifying the installation and activation process.
Hope this helps. Please do let us know what you'd like to see.
Richard Macaskill
Product Manager
DLM Automation / comments
Hi Mattias,
Thanks for your post.
As you're using Octopus, I'd definitely point to the new difference report that SQL Release creates. It has a new look and feel (intra-line diff similar to GitHub,...