The Ultimate Guide to Version Control in dbForge Studio for MySQL
Unlock the power of Database Version Control with dbForge Studio for MySQL! This tutorial guides you through setting up source control, making commits, and managing changes. Perfect for database developers and administrators, you'll learn how to commit static data, push and revert changes. Elevate your MySQL database management today.
🔍 What Will You Learn?
- How to select a database for version control
- Setting up a source control repository (We use Git in this example)
- Making your initial and subsequent commits
- Viewing and managing changes both locally and remotely
- Reverting changes using the Undo operation
Don't miss out on experiencing these features yourself! Download a free 30-day trial of dbForge Studio for MySQL and take your database management to the next level.
👉 Do you want to know more information about dbForge Studio for MySQL? Watch our overview video:
https://youtu.be/uSN4GxsjVHM
✅ Check a full list of dbForge Studio for MySQL features:
https://www.devart.com/dbforge/mysql/studio/features.html
🔥 Download a 30 days free trial version of dbForge Studio for MySQL:
https://www.devart.com/dbforge/mysql/studio/download.html
🔔 Subscribe to our channel and get dozens of tutorials about Devart tools:
https://www.youtube.com/c/DevartSoftware
Do you have any questions or ideas about our tutorials? Feel free to write about it in the comment section!
#MySQL #dbForge #database #MySQLgui #databases #MySQLTool #MySQLTutorial
Closed Caption:
The Source Control functionality of dbForge
Studio for Mysequel allows you to put your
database under a version control system.
First, select a database which objects and
table data you want to version-control.
Specify a source control repository. We
select Git.
Click Test Connection to make sure that the
configurations were specified correctly.
We are selecting the Dedicated database
development model because all our database
developers work with their local databases.
Finally, click Link.
Since our version control repository
is empty, Source Control Manager prompts us to
make an initial commit of all database objects.
Select all objects, enter a
comment, and hit the Commit button.
As you see, the commit has been successful.
Now let's refresh Source Control Manager.
As you can see, there are
no changes detected so far.
Suppose we want to version-control
the table static data. So we link
it to source control. Next, we need to
commit Static Data to our repository.
Now, let's modify a function and a table.
As you see, there are three changes detected:
a function, a table, and static data.
Source Control Manager allows you to
view the changes in detail, including a
script of the modified objects and data.
Suppose a column was
accidentally added to a table.
We can revert the change
using the Undo operation.
After the refresh of Source Control Manager,
in Local Changes, there is only a function.
Let's put this change in the repository.
We enter a comment and click Commit.
As you see, our tool has detected the
changes that were previously committed
to the repository by one of the other
developers working on the same database.
dbForge Source Control allows viewing
Changes History for the selected object
both in Local and Remote Changes.
To update your database with the
remote changes, click Get Latest.
Download a free 30-day trial of dbForge Studio
for Mysequel and see how easily and painlessly you
can manage database changes with its help.
Video Length: 02:43
Uploaded By: Devart
Published: 11/3/2023
View Count: 790