# tagDatabase - proper usage **URL:** \ **Category:** General Discussion\ **Created:** [July 1, 2020, 12:37pm UTC](https://forum.liquibase.org/t/tagdatabase-proper-usage/4369 "2020-07-01T12:37:48Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![krysgian](https://avatars.discourse-cdn.com/v4/letter/k/e19adc/32.png) [@krysgian](https://forum.liquibase.org/u/krysgian)\ **Post date:** [July 1, 2020, 12:37pm UTC](https://forum.liquibase.org/t/tagdatabase-proper-usage/4369/1 "2020-07-01T12:37:48Z")
I have added a tagDatabase changeset in my databaseChangeLog, along with 100 other changesets (create table, add constraints, etc). I notice in the databasechangelog table, the tagDatabase changeset has a tag column with the appropriate tag name. All of the other columns within the same change log have a blank tag column. Should I have added a tagDatabase instruction to each changeset record or is it the intent for just one record to contain the tag? It would seem to make sense if I were to do a roll back against the tag, that I would specify the tag and it would rollback all that contain that tag (and not all that were inserted at roughly the same time as that tag record). ---
**Author:** ![Pete](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/pete/32/184_2.png) [@Pete](https://forum.liquibase.org/u/Pete)\ **Post date:** [July 1, 2020, 4:27pm UTC](https://forum.liquibase.org/t/tagdatabase-proper-usage/4369/2 "2020-07-01T16:27:07Z")
The Liquibase tag is not a container for changesets. Instead they put a bookmark of sorts in the DATABASECHANGELOG table that you can get back to with a rollback. So when rolling back using a tag you are telling Liquibase to rollback all changes that came AFTER the tag instead of before the tag. Typically users will tag the database after a release so that they can quickly rollback to the last “official” state easily as they begin development on changesets for the next release.