![multiple select and editing with redgate sql toolbelt tips and tricks multiple select and editing with redgate sql toolbelt tips and tricks](https://ftuapps.dev/wp-content/uploads/2020/02/RedGate-SQL-ToolBelt-v2.3.6.2707.jpg)
![multiple select and editing with redgate sql toolbelt tips and tricks multiple select and editing with redgate sql toolbelt tips and tricks](https://www.red-gate.com/simple-talk/wp-content/uploads/imported/2364-clip_image001.png)
With some thought, this shortcut convention could be extended to cater for different sources or types of snippet.
MULTIPLE SELECT AND EDITING WITH REDGATE SQL TOOLBELT TIPS AND TRICKS CODE
Each of SQL Prompt’s built-in code snippets is generally very short and simple, and is invoked using a 3-4 letter shortcut code, which is an initialism of the SQL command it executes (so ALTER TABLE…ALTER COLUMN is atac). Like many programming problems, a big part of the solution for distinguishing between different types of snippet is in having a consistent naming convention. Source separation through naming conventions Another concern is that I work on at least three different computers regularly, and I want to have my snippet library available for my use on all of them, and a simple local shared folder will not do because they are not on the same network.
![multiple select and editing with redgate sql toolbelt tips and tricks multiple select and editing with redgate sql toolbelt tips and tricks](https://getintopc.com/wp-content/uploads/2020/06/RedGate-SQL-ToolBelt-Full-Offline-Installer-Free-Download-300x169.jpeg)
However, SQL Prompt only one directory in which to store your snippets. My goal is to be able to keep the different sources of snippets in one library, but also be able to source control them separately and “publish” only those that I want to share. I don’t share these snippets, simply because they are just ‘noise’ to the anyone but myself. They are general-purpose enough that I have them published on GitHub here: ( ).įinally, I have a set of snippets for maintaining my ‘hobby’ databases, such as my photography database, which I want to save in source control alongside the database source code. I also maintain a set of personal snippets that I use for formatting SQL comments for books or articles, getting min and max datatype values, and so on. Anyone in the team can propose changes but they must always be fully tested before I or any team member distributes or changes a snippet. The latest version of each of these ‘corporate’ snippets must be available in a central location, to which everyone in the team has access. We also have snippets to help us explore the structure of tables in our databases, troubleshoot locking and blocking, validate configurations before a release, and more. For example, we have a code snippet to create tables and columns using our corporate standards, and another to make it easier to drop a table or column and there are dependencies. Our team use a shared set of “corporate” snippets for managing, querying, and troubleshooting our databases. I use code snippets pretty much every day, and for all these activities. Managing different sources of snippetsĪs a career database programmer/architect, a technical writer, and a hobby photographer, I use a SQL Server database, and write SQL, for many reasons. This is a guest post from Louis Davidson.