Join the Redgate Tool Tips Swap – win a Pluralsight subscription!
Share your Redgate tool tips to win a Pluralsight subscription!
Now more than ever, we need to make the most of our existing resources. To help you achieve more with your Redgate tools, we’ve launched the Redgate Tool Tips Swap.
To join in, please share your top tip for improving productivity with Redgate tools in the thread below.
The Redgate Tool Tips Swap closes on 15 January 2021. All tips collected will be shared with the Redgate community via our blog, forums and social media channels.*
Plus, everyone who takes part will be entered into a prize draw for a 3-month subscription to Pluralsight (a leading online training provider).
Looking forward to hearing your tips
Roseanna*By taking part in the Redgate Tool Tips Swap, you give permission for us to share your tip on www.red-gate.com and on Redgate’s forums and social media channels.
Configure SQL Prompt's settings for your needs. SQL Prompt is a fantastic tool for working more efficiently. You can make it work even better for you by adjusting the settings for your needs. Redgate's Grant Fritchey has a short training course on this.
Over to you. What are your tips for improving productivity with Redgate tools?
In SQL Change Automation in Visual Studio, there's a hidden filter capability
When importing changes from a database to generate migrations, simply begin typing to filter out changes by object name.
This is handy for scenarios such as generating a script to be used for re-seeding data for an integration test without having to write that insert by hand.
This is handy during data exploration and feeding values from one query into another, such as grabbing the ID's from one query and dropping them onto the where clause of another query.
I've not been able to use prompt in recent assignments but current client uses Redgate so some things I'd long forgotten are coming back to me and that one just came to me today!
It's not best practice but is so quick and easy to setup and move code around environments.
1. Hook all your environments up to source control using the 'dedicated' model irrespective of whether you are using shared or dedicated environments. for me, this included prod.
2. Develop in your development environment and commit using Sql Source Control
3. When you want to move the change to a test environment, just use the Get-Latest tab. Same with production deployments.
4. If you ever did need to do an emergency hot-fix in prod. Just push to source-control from there and make sure you get the latest on your development environment straight away.
Some people may baulk at this haha but I reckon I have done over 3,000 commits and 100's of production deployments using this method without ever running into a problem!!
It also means you only ever work in one tool, SSMS. CI/CD pipelines are all the rage but imo they are not trivial to setup and they are not essential to building great software, especially for very small, tight-knit teams.
Also worth noting that this was on Data Warehouse projects and I had created automated tests so I knew early whether my changes would work - the tests just weren't triggered, i had to click a button
Thank you to everyone who has shared a tip so far! The Redgate Tool Tips Swap closes tonight. If you have any tips for increasing productivity with your Redgate tools, please do share them below.
Everyone who submits a tip will be entered into a prize draw to win a 3 month subscription to Pluralsight.
I'm delighted to announce that the winner of a 3 month subscription to Pluralsight is.... @DaveDavis. Congratulations Dave I'll send you a direct message to arrange delivery of your prize.