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....
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...
1. Run this query, save results to excel and then send to the business analyst to fill in the description
SELECT TABLE_SCHEMA AS SchemaName,
TABLE_NAME AS TableName,
COLUMN_NAME AS ColumnName,
'' AS [Description goes here]
FROM
INFORMATION_SCHEMA.COLUMNS
ORDER BY SchemaName,
TableName,
ColumnName;<br>
2. Once you have the description from the BA, plug them into this query exec sp_addextendedproperty
@name = N'MS_Description'
,@value = N'Description supplied by the business analyst'
,@level0type = N'Schema', @level0name = 'dbo'
,@level1type = N'Table', @level1name = 'The table name goes here'
,@level2type = N'Column', @level2name = 'The column name goes here'
3. Run SQL doc and it should produce what you need This all said, I've not actually tried it myself yet. / comments
1. Run this query, save results to excel and then send to the business analyst to fill in the description
SELECT TABLE_SCHEMA AS SchemaName,
TABLE_NAME AS TableName,
COLUMN_NAME AS C...
Hello the below link explains how you can use sp_addextendedproperty within SQL server to add explanations to column and tables and store this information in the database... You can then use red-gate SQL doc to use that information to generate a data dictionary in Word/PDF/HTML https://www.red-gate.com/hub/product-learning/sql-doc/documenting-a-sql-server-data-catalog-in-html-and-git-markdown?product=sql-doc One potential alternative tool is Microsoft Purview - it should mean that you can add table/column descriptions using a web UI (as asset descriptions within Purview Data Catalog)... although I have not actually used Purview yet so remains unproven to me as of today. cheers Ben / comments
Hellothe below link explains how you can use sp_addextendedproperty within SQL server to add explanations to column and tables and store this information in the database... You can then use red-gat...
as an update, in case someone has similar use case, I am now looking at two options: 1. 'analyse data' feature in excel 2. 'column profiling' feature in power bi. struggling to get the Power BI to work but will do some more testing. more information below: https://support.microsoft.com/en-us/office/analyze-data-in-excel-3223aab8-f543-4fda-85ed-76bb0295ffc4 https://sqlskull.com/2021/02/28/profile-data-in-power-bi/ / comments
as an update, in case someone has similar use case, I am now looking at two options:1. 'analyse data' feature in excel2. 'column profiling' feature in power bi.struggling to get the Power BI to w...
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...
OK, thanks @Ben_P - useful to know [image] / comments
OK, thanks @Ben_P - useful to know
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...
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...
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...