How can we help you today? How can we help you today?
ben_b

Activity overview

Latest activity by ben_b

Internal Usage Survey
Hi RedgateWe have 25 toolbelt licenses used by people across 6 different teams.I was wondering if you have any sort of digital survey I can use internally that would establish1 - Who is using what....
1 follower 1 comment 0 votes
Search across multiple servers
we have been discussing Microsoft Purview at my place for a little while.  It is a confusing product and takes a long time to get your head around it.One of the primary use cases for the Purview da...
0 followers 0 comments 0 votes
Data Profiling Tools
I feel like this comes up for me every couple of years for me.We want to get data owners / stewards to look at specific "critical data elements" and use their industry expertise to feedback data qu...
1 follower 1 comment 0 votes
Azure Synapse support across red-gate products
Hi All.  I've searched the forums and found a few answers (some of which were recent but some of which were a couple of years old), but I was hoping to get all the information in one place and conf...
4 followers 4 comments 0 votes
Sql Agent 2.0
Hi AllI recently saw this article and definitely agree. https://www.sqlservercentral.com/articles/the-case-for-sql-server-agent-2-0SQL Agent is always a massive part of what we do in the data wareh...
0 followers 0 comments 0 votes
I can share something I have done at three companies using Sql Source Control that has worked brilliantly  but probably only works if there are one or two developers co-located.  At the time we used SVN and TFVC and didn't use branching.  Also, I was pretty strict on one-piece flow. 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 [image] / comments
I can share something I have done at three companies using Sql Source Control that has worked brilliantly  but probably only works if there are one or two developers co-located.  At the time we use...
0 votes