Looking for a hair dryer that does more than just dry? Look no further than XSOOH! Our innovative hair dryers designed to transform your hair care routine.
https://xsooh.com/products/xsooh-high-speed-hair-dryer-sp1

Dear Users,

Thanks for your patience.

We would like to kindly inform you that we have released a new version of the tool. This version includes a lot of fixes.

Please be informed that the long-awaited Source Control feature is now available!

The full list of fixes and features you can find in Revision History:
https://www.devart.com/dbforge/mysql/studio/revision_history.html

You can upgrade to the new version within the app, just look on the bar on top for "Help→Check for updates".

Or you can use the link below:

https://www.devart.com/dbforge/mysql/studio/download.html

In case you have any additional questions or need any kind of assistance, kindly let me know.

Thanks in advance,
Devart Team
www.devart.com

Keep it up

Any news or ETA on this?

Just wonder how frequent they will check these suggestion.

I have dbforge fusion and since TFS doesn't understand how to integrate with project files the source control has to be done manually in team explorer :(

at the time I make the source control manualy in GIT, save the changed SP's on local drive and use sourcetree to commit. it would be greathe if this would be integrated in DbForgeStudio

@gr8kodr - It wouldn't be superfluous as managing separate .sql files for table definitions, stored procedures and functions is a tiresome exercise and prone to accidents as people forget to save their changes.

It would be way more professional and efficient if a user can just right click and commit a database after a days work.

Currently I have a separate C# app that I run each night to script out the individual objects and check them into the SVN repository. It would be great to have this an integral part of DbForge.

It may seem obvious, but ...
Making the following assumptions:
1. that your SQL Schemas and Data are part of a larger Project
2. that said Project is appropriately managed and already using a VCS
3. that your SQL scripts are being stored into a "sql" directory under your project root

Wouldn't additional VCS integration within dbForge be superfluous?

This might be complex, but it beats our current system of exporting the schema into the code tree and versioning it from there. That means we often have no idea who made a change or why, but at least we have a record of when the change was made. It would be worth buying another license or two to get this feature so that we could "encourage" everyone who makes DB changes to use DBForge and track changes properly.

I'm not too interested in source control integration, too many, too complicated.

Now, if PROJECT could be set up ad managed properly, than I can use my source control of choice as I see fit. That would be lovely!

GIT would be awesome!

This should also include TFS :)

Muy buena. Me encanta!
Fabiola

SourceGear Vault

Surround SCM +1!

TFS Up+1

SVN and GIT would be at the top of my list +1

As an interim measure could the backup functionality be extended to write each option into it's own file within a set folder hierarchy and without any timestamp metadata or anything?

If so we'd only need to run the backup into a directory within our source controlled working copies and commit from there. If the files only change when something is genuinely different about the functionality of the object, the source control system will only see actual code changes as amendments to be committed. Purging all SQL files (but not directories) within the target directory would eliminate the need for tracking deleted objects.

I have something similar setup for MS SQL and that works very well (and is scheduled to run automatically every night).

Vault by Source Gear