-
Writing database code faster
Steve works for PrentoBank, building databases in
SQL Server Management Studio (SSMS).Picture him at his desk, adding rupees to the database so PrentoBank’s Indian customers can bank online.
As Steve types, SQL Prompt finishes lines of code for him. It helps him work faster. It means he can focus on developing, not memorizing table names.
-
Simple ways to share database updates
When Steve is ready to share his work, he turns to
SQL Source Control.With two clicks in SSMS, his work is stored safely. Steve’s colleagues can grab his updates without interrupting their own work.
And there’s a permanent record of what Steve has changed.
-
Database builds that check each change
Committing a change to source control triggers the database Continuous Integration (CI) process.
On the team’s build server, SQL Compare and SQL Data Compare build a new database to test Steve’s work.
-
Automated tests to catch errors early
Automatically, the test database is pumped full of realistic data from SQL Data Generator. Steve’s changes are checked with SQL Test.
The tests stop any code that contains errors from being applied to the database, so doing CI means the PrentoBank development team always have an up-to-date, working database.
-
One process to deploy the whole application
Steve’s tests pass. It’s time to deploy. Steve uses Deployment Manager. It takes his application – ASP.NET website, assemblies, database – and turns it into flexible NuGet packages.
Deployments run through a secure connection, so Steve can deploy to any server confidently – local, remote, even the Cloud.
