Let's break down a typical workflow for making a SQL change using Redgate's SQL Toolbelt, let's say creating a new stored procedure to search for customers.
Having a SSMS plug-in makes all the difference in the world. Redgate's SQL Toolbelt provides many different tools, including SQL Source Control which is a SQL Server Management Studio (SSMS) plug-in. Microsoft SSDT is a Visual Studio plug-in. The difference is the user interface used to kick off this process. nupkg for DLM Automation, and deployed to SQL Server (or Azure SQL Server if you are using PaaS). In fact, they both follow the same core concepts. Both Microsoft's SSDT and Redgate's Toolbelt can be used to automate database deployments. Hence this post.īefore I dive too deep into this post, let's get the elephant in the room out of the way. And you know what, they're right, it would make a good post. The email mentioned the answer might be a good post. I was sent an email asking for further clarification on why Redgate was chosen over Microsoft SSDT. Could it do what Redgate did? Could we build additional functionality around it? In the end, the answer was no, but that delayed us as well. Microsoft SSDT Tooling Considered - the increased cost of licenses forced us to take a hard look at Microsoft's SSDT tooling. Back in the article How Redgate Helped Define our Process, there was this small blurb about SSDT:
0 kommentar(er)
