---
title: "Comment by Richard Sylvester on \"[Mastering Oracle SQLcl Liquibase - Part 3/3] - Synchronize your existing environments\" | Hashnode"
description: "Hi Rafal, thanks for the detailed explanation of how to use Liquibase on an existing environment. Let's say I have a dev environment with 105 tables of which 5"
url: "https://hashnode.com/posts/episode-33-synchronize-your-existing-environments-and-start-using-sqlcl-liquibase/65095eacb8c416459711578d/comment/65f0a169da55346f9f2e51db"
---

[Discussion](https://hashnode.com/posts/episode-33-synchronize-your-existing-environments-and-start-using-sqlcl-liquibase/65095eacb8c416459711578d)

Comment [\[Mastering Oracle SQLcl Liquibase - Part 3/3\] - Synchronize your existing environments](https://hashnode.com/posts/episode-33-synchronize-your-existing-environments-and-start-using-sqlcl-liquibase/65095eacb8c416459711578d)

[Richard Sylvester](https://hashnode.com/@risylv)

[Mar 12, 2024](https://hashnode.com/posts/episode-33-synchronize-your-existing-environments-and-start-using-sqlcl-liquibase/65095eacb8c416459711578d/comment/65f0a169da55346f9f2e51db)

Hi Rafal, thanks for the detailed explanation of how to use Liquibase on an existing environment.

Let's say I have a dev environment with 105 tables of which 5 of them are used by developers to try out new features and rest 100 tables I would like to keep in sync in UAT. What would be the best approach?

[Rafal Grzegorczyk](https://hashnode.com/@rgrzegorczyk)

[Mar 12, 2024](https://hashnode.com/posts/episode-33-synchronize-your-existing-environments-and-start-using-sqlcl-liquibase/65095eacb8c416459711578d/comment/65f0a169da55346f9f2e51db#reply-65f0a704ff88c61e6258f3e7)

Hi Richard! Thanks for asking. The answer is: it depends :) I would see some approaches for that:

1.  Every developer cleans his mess before you will run the generate-schema command versus DEV and then update to UAT ( so you don't have those tables then)
2.  Manually remove those changesets (with those 5 not needed tables) from files generated by generate-schema and then update to UAT
3.  You run generate-schema only at the beginning of your journey with SQLcl Liquibase. After that, every developer creates his changesets and commits them to git. Those 5 tables will not be added there, so they will not be deployed to UAT during the update.
4.  After running generate-schema on DEV, edit the changesets with those 5 tables and add a tag contexts="DEV\_ONLY" ( or any other name ). When deploying to UAT, use liquibase update -changelog-file controller.xml contexts="!DEV\_ONLY." Thanks to that, changes with contexts DEV\_ONLY will not be deployed.

And a few more approaches, I suppose. Hope it helps. Rafal

[Richard Sylvester](https://hashnode.com/@risylv)

[Mar 12, 2024](https://hashnode.com/posts/episode-33-synchronize-your-existing-environments-and-start-using-sqlcl-liquibase/65095eacb8c416459711578d/comment/65f0a169da55346f9f2e51db#reply-65f0abc3279cd93ed451ece7)

[Rafal Grzegorczyk](https://hashnode.com/@rgrzegorczyk) Thanks again for the suggestions. I think point #4 would be a great idea to add tags and using it while updating the UAT environment.

Trying to get started on a DEV environment where there are 100s of temp tables created as part of nightly processing every day. :-)
