SQL Server and Excel Hierarchyid Example for Organization Charts
In this tip we look at how to build a hierarchy chart using the SQL Server hierarchyid data type and Excel to format the chart.
2019-07-16
Additional Articles
10 steps you can take to be compliant worldwide – free whitepaper
Learn how data protection legislation is changing around the world and the 10 steps database teams can take to ensure compliance and defend against data breaches.
2019-07-15 (first published: 2019-06-21)
Reporting Services Basics: Understanding Data Sources and Datasets
Data sources and datasets are critical components of an SSRS report, but many people new to SSRS struggle to understand them. In this article, Kathi Kellenberger shows you how to create these components and explains when they should be shared vs. embedded.
2019-07-15
4 Ways to Move Data Into a Reporting Server
You’ve decided that you need to offload reports to a different SQL Server, and you’re willing to pay the costs. Here are the most common ways to move the data from production to a reporting server, arranged roughly from easiest-to-implement to hardest.
2019-07-12
Loading data into SQL Data Warehouse
In this step-by-step guide, we’ll be walking through the process of moving data from an on-premises SQL Server to Azure SQL Data Warehouse using the Copy Data feature in Azure Data Factory. The use case we’ll focus on is the first-time loading of data.
2019-07-12
Data privacy: don’t look forward, look back
What does Amazon’s Alexa have to do with a wiretapping law from the 1960s? With all the talk about new data privacy legislation, we don’t stop to think about existing laws. Legislation like the GDPR kick-started the way the world views data privacy, and this blog post explores how existing laws are being used in new ways around the globe to enforce similar protection.
2019-07-11
The End of SQL Server 2008 and 2008 R2 Extended Support
Many organisations still run their companies on SQL Server 2008 or 2008 R2. There are many reasons to upgrade, but the most pressing reason is that extended support is running out. In this article, Brian Kelley explains what this means, tells you about some of the features you’ll gain if you upgrade, and provides some options.
2019-07-11
Simple Steps in SQL Change Automation Scripting
Phil Factor demonstrates the bare essentials of SCA PowerShell scripts that can form the basis for an automated process for database delivery or help improve your current process.
2019-07-10
SQL Server Reporting Services: What I wish I knew when I started?
In this article Scott Murray covers some lessons learned over the years when working with SQL Server Reporting Services that he wish he knew when he started with SSRS.
2019-07-10
Refactoring Databases with SQL Prompt
Louis Davidson demonstrates how SQL Prompt can significantly lessen the pain involved in occasional, 'heavyweight' database refactoring processes, such as renaming modules, tables and columns (Smart Rename), or splitting tables (Split Table).
2019-07-09
Blogs
Flyway Tips: AI Deployment Script Descriptions
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
A New Word: Fawtle
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
Post-quantum key exchange – Insurance policy for your packets
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Forums
Where Your Value Separates You from Others
Comments posted to this topic are about the item Where Your Value Separates You...
Fixing the Error
Comments posted to this topic are about the item Fixing the Error
T-SQL in SQL Server 2025: Encoding Functions
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Question of the Day
Fixing the Error
On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:
SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error? See possible answers