Git vs. Redgate SQL Toolbelt Essentials

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Git
Score 10.0 out of 10
N/A
N/AN/A
Redgate SQL Toolbelt Essentials
Score 8.2 out of 10
N/A
Redgate's SQL Toolbelt Essentials includes industry-standard tools for SQL Server development & deployment, enabling users to include SQL Server databases in agile processes and enabilng developers to embed robust and scalable development practices.N/A
Pricing
GitRedgate SQL Toolbelt Essentials
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
GitRedgate SQL Toolbelt Essentials
Free Trial
NoYes
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
GitRedgate SQL Toolbelt Essentials
Considered Both Products
Git
Chose Git
We migrated from svn to Git and the transition was smooth. We have tools that migrate the complete history along with the authors of the various files and the history from svn to Git. The migration was seamless and easy. We can see complete history of check-in as if we were …
Chose Git
We were using the TortoiseSVN previously and it was super slow when we created a new branch or switched between branches. Git makes our life easy. :)
Chose Git
Git is far superior at merging than SVN and I think every other VCS from what I've heard. It's also by far the most common so using it is a no brainer. Since it's written by the one true king Linus himself there can be no question to its design and architecture.
Chose Git
The only other VCS tool I've used in production is SVN. In my option Git is a better option for several reasons. Reason one is simplicity, actions like reviewing changes, committing or stashing changes, and managing multiple feature branches is much easier with Git. The second …
Chose Git
The two main alternatives to Git that I know about are Mercurial and Subversion. I've never used either one, but I know a bit about Subversion. From what I remember, Subversion requires a server. I don't anyone using any other source control other than Git, it seems to have …
Chose Git
Git is more advanced and easier to use. It has a very simple UI and a very efficient command-line tool. Git gives you flexibility and performance for the price, and has greatly increased the complexity of workflow. The overall performance is good. It caches information locally …
Chose Git
What I know is Perforce and CVS, such other repos tend to store deltas while Git stores the snapshots of the stuff as their commit ID's. This is what makes Git much much faster when you are developing on huge repos, since the checkouts are just instantaneous.
Chose Git
Gitlab provides similar features like Git. Git is more robust, secure and developer-friendly to work on.
Chose Git
There are not many surviving alternatives for Git (maybe SVN) which in itself is quite meaningful. Git is the best versioning system of all time for programming, period. The difference between a good mathematical tool and sending .zip-s around emailing lists or FTP drives is so …
Chose Git
GIT being a widely used tool have better reliability than its peers and have stands out when we compare it on operational performance criteria.
GIT with speedy and extensive branching capabilities have helped developers to use check in their code quickly and space efficient way.
G…
Chose Git
It's easy to use and stable. These are the two strengths I see in Git. It does not need a lot of time to learn, but you still need to learn it. It has high stability. Bugs are not often to see in Git, and the community support is wonderful. With the help of GitHub, you can …
Chose Git
Compared to SVN, Git has a decentralized approach which increases collaboration in the team by enabling the local stored branches. There is no need to be connected to the repository(via an internet link) to work and commit code. Besides the fact that the performance of Git is …
Chose Git
I do not have much experience with other version control tools. Git is highly used everywhere and it is hard to find a development team that isn't using it. One thing I know is that with Git each developer has their own copy of a repository so they could technically work …
Chose Git
Git is the best Source Control Management Tool I've used. Every company, team, and project I've worked on professionally either used Git 100%, or was moving to Git, away from the alternatives like SVN. Git has all the features necessary, as well as a very large community of …
Chose Git
Git is by far the best version control system out there. It's open source, free, and fast. No other version control system I've ever used has had all three features.
Chose Git
Primarily we chose Mercurial, but our customers from abroad choose Git and recommended us to use it within a project that we are doing with them. Git for us is very easy way to contribute to these projects. But from the other side we see that more and more projects and …
Chose Git
For us, we use both Git and GitHub so they were a package. I suppose you could use Git with another VCS/hosting service to track changes if it fit well enough, but for us we just went with design out of the box. We pay for the GitHub private repository for the extra security.
Chose Git
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different. The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in …
Chose Git
N/A. No other products like Git were used.
Chose Git
Branching and merging are easy: Branching is a walk in the park. It feels like a natural part of the workflow. They are cheap (fast and consume very little space) so that you can branch whenever you want. This means you can sandbox your features and ideas till they are ready …
Chose Git
Git is pretty much the main choice today when choosing a source control system. There are still others out there like Subversion and Mercurial, however I have not evaluated these as they are older than Git and I tend to try to stay on the leading edge of what is in use for the …
Chose Git
Git is a distributed version control system. There is more flexibility to work with a bigger team. You can modify the same file and later merge all changes into a single file.
Chose Git
After using Subversion previously for a number of years, Git comes across as the new and improved source control approach. Git seems very suited to working with Agile:- branches can be created easily, allowing multiple developers to switch to them quickly, and having local …
Chose Git
While my experience is limited on Microsoft Team Foundation Server, my understanding is that it works only for windows development work. This leaves out developers of alternative languages. Since git allows any code to be placed in it (you could even use it to back up plain …
Redgate SQL Toolbelt Essentials
Chose Redgate SQL Toolbelt Essentials
Honestly, due to prior experience, we just have stuck with Redgate. Great tool and no reason to look anywhere else.
Chose Redgate SQL Toolbelt Essentials
I've used Visual Studio Database Projects for this type of work in the past with some success, but Redgate SQL Compare is faster, more transparent, and simply easier to use.
Faster is self explanatory.
More transparent, means that it's much easier to set up your desired options …
Chose Redgate SQL Toolbelt Essentials
We did not consider other products before choosing Redgate.
Chose Redgate SQL Toolbelt Essentials
Redgate SQL is better.
Chose Redgate SQL Toolbelt Essentials
I've been using Redgate SQL Compare for 15+ years and have no desire or need to look for anything to replace it.
Chose Redgate SQL Toolbelt Essentials
We only looked at Redgate SQL Compare if I recall correctly.
Chose Redgate SQL Toolbelt Essentials
I haven't felt the need to try many different products like Redgate.
Chose Redgate SQL Toolbelt Essentials
I was familiar with the quality of Redgate's products at the time of making the purchase decision. I checked out a trial version to make sure I could achieve what I wanted from the application, but I never made comparisons with other vendors tools on this occasion. …
Chose Redgate SQL Toolbelt Essentials
We haven't compared SQL Compare with other tools in a VERY long time because they are honestly THE BEST.
Chose Redgate SQL Toolbelt Essentials
Honestly, I have never been interested in the usable alternatives. I have always been good to use it. The license cost after all has always been sustainable. I never had the idea of \ u200b \ u200bchanging it nor the need to look at other software. Also (always a redgate …
Chose Redgate SQL Toolbelt Essentials
We have used Symantecs Database Agents for Backup Exec and Veeam's Database Backup products. Symantec does not stack up well as compared to Redgate. Veeam is a considerable contender with their SQL Server Explorer. In some scenarios I would prefer to use VEEAM over Redgate, …
Chose Redgate SQL Toolbelt Essentials
Frankly, I came into a RedGate equipped database shop and never considered looking for anything else. I didn't find RedGate, it found me. When I leave one company, to go to a new company I immediately make sure there are licenses to Toolbelt Essentials. It's that important to …
Best Alternatives
GitRedgate SQL Toolbelt Essentials
Small Businesses
GitHub
GitHub
Score 9.0 out of 10
DBeaver
DBeaver
Score 9.2 out of 10
Medium-sized Companies
GitHub
GitHub
Score 9.0 out of 10
DBeaver
DBeaver
Score 9.2 out of 10
Enterprises
Perforce P4
Perforce P4
Score 7.7 out of 10
DBeaver
DBeaver
Score 9.2 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
GitRedgate SQL Toolbelt Essentials
Likelihood to Recommend
10.0
(0 ratings)
8.0
(0 ratings)
Likelihood to Renew
10.0
(0 ratings)
-
(0 ratings)
Usability
9.0
(0 ratings)
7.0
(0 ratings)
Support Rating
8.5
(0 ratings)
8.6
(0 ratings)
Implementation Rating
9.0
(0 ratings)
-
(0 ratings)
User Testimonials
GitRedgate SQL Toolbelt Essentials
Likelihood to Recommend
Git is by far the best Source Control Management Tool I've used. I would recommend it to anyone, whether it's an individual working on their own project, a small start-up company, or a huge organization with thousands of developers. Maintaining code via source control is absolutely mandatory for all developers everywhere.
Read full review
We use SQL Compare to troubleshoot performance problems quite a bit since our data model is more like a template and not everything is 100% in sync and customization occurs between different client databases. We continually get pulled into performance issues and the developers will say Client A is performing different than Client B, why? Using SQL Compare, we usually find that one client was tuned and had indexes altered or added that weren't deployed to all clients or other objects weren't deployed correctly during the release. On the other hand, since our data model practices allow client databases to drift I tried to create a new golden image by trying to compare multiple databases based on the same data model and found it to be a very difficult process to complete using SQL Compare. SQL Compare gave me too much information and doesn't allow enough filtering to eliminate a lot of the noise.
Read full review
Pros
  • Git is designed to work in a distributed manner, allowing each developer to run a local node that has full control of the project. Through this, the developer is able to merge his work with others on a main 'branch' & work in sync without having to worry about stepping on your other developers toes.
  • Because Git has solved the software problem of dependency, users who commit code that needs to be deleted can just roll back to a restore point, saving precious development time & tons of headaches for Information Technology. This is also very helpful when cloning projects or creating new features on the current project.
  • Git has a beautiful command line interface that is intuitive, easy to learn & extensible. You can also observe all the changes you have made in your project throughout the development with just a few simple commands. This diverse set of command-line tools is easy for the end user & very powerful.
Read full review
  • Simple and easy comparison of database schemas and data. Differences can be copied or synced from one database to another with a click of a button.
  • You can save "projects" so that you can easily rerun a previous comparison whenever you need to.
  • It has a very simple, easy to learn interface. I've never needed to read any documentation or watch any tutorials in order to figure out how to do something.
Read full review
Cons
  • Some of the commands are a little obtuse if you're not using a Git Client
  • Since Git is so widely used in the development space, it's easy to believe that growth and innovation might become stale in the area of version control. Competition is sparse these days and I'm curious if this "Standard" is going to keep moving forward somehow.
  • It's hard to fault a tool that is so ubiquitous and hardly gets in your way.
Read full review
  • Pricing.... I wish there was an inexpensive developer version I could buy for myself.
  • Portability.... I would like to use it from a flash drive so I can use it where ever I am asked to work.
  • Unbundled.... This may be available already but I dont' recall I can buy it cheaply as a stand-alone product. Its only part of the bundle - cost effectively.
Read full review
Likelihood to Renew
Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
Read full review
No answers on this topic
Usability
Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.
Read full review
It's a good tool to have, but becomes expensive to buy a user license for each developer.
Read full review
Support Rating
I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
Read full review
They have a great community website where you can search for answers but are also very responsive when it comes to direct support.
Read full review
Implementation Rating
It's easy to set up and get going.
Read full review
No answers on this topic
Alternatives Considered
GIT being a widely used tool have better reliability than its peers and have stands out when we compare it on operational performance criteria. GIT with speedy and extensive branching capabilities have helped developers to use check in their code quickly and space efficient way. GIT have the facility to quickly fetch the complete repository on to your local system.
Read full review
I've used Visual Studio Database Projects for this type of work in the past with some success, but Redgate SQL Compare is faster, more transparent, and simply easier to use. Faster is self explanatory. More transparent, means that it's much easier to set up your desired options for schema change deployment scripts. Easier to use, It's really dead simple. Start a project, connect your source, connect destination, click compare.
Read full review
Return on Investment
  • Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
  • Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
  • Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
Read full review
  • Makes deployment fairly simple. Cutting our deployment time down.
  • With the SDK, we can customize our deployment process very quickly and easily.
  • History is not great, it does create scripts you can go back and see but it would be nice to have a quicker version view by object to save time.
Read full review
ScreenShots