When Redgate posed this question to the SQL Server community, the results were unequivocal. Well over half the respondents wanted that time for either strategic development planning (32%) or proactive development (26%). An encouraging 18% would spend the hour in training or personal development, learning how to automate processes, and generally become better developers. The least popular answer in the poll was to spend the extra hour fixing more bugs (5%).
In other words, we want more time to work out how our applications can deliver maximum value to end users and to the business, more time to spend learning how to design effective databases, and less time firefighting the bugs and performance problems caused by poorly designed applications, databases and queries.
But how do you get back that precious extra hour in every day? If you're a .NET developer working in Visual Studio, you might easily gain this extra hour each day, just by making full use of the productivity tools already at your disposal.
Be a more productive SQL developer
All developers need to be specialists in their team's primary development language, but alongside specialists, an IT department needs people who are broadly skilled and versatile, who can be productive quickly on new projects, and with programming languages with which they are less adept, such as SQL.
SQL Prompt Core is an industry-leading SQL productivity tool, it's included free in Visual Studio Enterprise, and it's best known for giving you advanced, IntelliSense-style SQL code completion, but that’s not all…
| |
Write correct SQL queries in a flash
SQL Prompt Core autocompletes T-SQL commands and keywords, providing intelligent suggestions and prompts, as you type. Its auto-suggestions will allow you to pick very quickly the tables and columns from which you need data. If you can't remember the precise table names, for example, SQL Prompt Core offers suggestions based on the first characters you type, mid-string, or CamelCase.
In the most simplistic case, it reduces the task of writing a SELECT
statement to just a few keystrokes.
Of course, it's generally a bad practice to use wildcards in SELECT
statements, so simply place your cursor after the SELECT *
, hit tab, and SQL Prompt Core will replace the *
with all the columns available in the table.
Even better, avoid the * altogether! Start typing the column name after SELECT
then pick the columns you need from the Column Picker suggestions.
SQL Prompt Core's auto-suggestions will also allow you to flesh out your WHERE
, GROUP BY,
and other clauses, as well as navigate much more easily through complex join conditions.
It will auto-suggest "join" tables, starting with any tables that have a FOREIGN KEY
relationship to the first table. If there isn't a FOREIGN KEY
, SQL Prompt Core suggests relevant JOIN
conditions based on column similarities, such as an EmailAddress
or Username
column present in both tables.
Once you've written your T-SQL query, stored procedure or function, you'll want to test it. SQL Prompt Core autocompletes EXEC
statements too. It'll pick up where there’s a parameter that needs to be parsed, and prompt you to add it before executing.
SQL Prompt Core also makes it quick and easy to write INSERT
statements, for example, by providing placeholders for all column names so you can quickly see the values you need to input to complete the statement.
It's easy to get lost in the nuance of SQL syntax and spend hours stumbling around technical documentation trying to work out where you're erred. SQL Prompt Core will guide you much more smoothly through the syntactical choices, deepening your knowledge of how SQL works while you're working through the code.