Versioning active database files is a very bad idea. If you want to use Git (or any other versioning system) to store past versions of your database, you should do so with database backup/dump files (.sql), not the actual database files themselves.
If you do not actually want to version these files, but they are located in your working copy, you should be able to right click > ignore them in SourceTree.
The main problem is that the files you are currently versioning represent part of a specific runtime state of your database. They depend on matching states in other parts of the system, such as other files (which you may also be versioning), but also potentially system data that could be stored in the registry or elsewhere.
Secondly (as you've discovered), storing binary database files completely prevents you from being able to preview or diff the files in/between revisions. If a commit message is missing or unclear, it is anybody's guess what changes have actually been made.
Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs