External Article

The DIS-Information Principle: A Splitting Headache

You can easily re-factor bad DML code, but if a database design is wrong, you can do little to rescue the problem, even with expert queries. So what constitutes 'wrong RDBMS design? What are these errors that continually crop up? How can you recognise them and fix them? Joe embarks on a new series of articles by identifying a series of bad practices based on the habit of 'splitting' that which shouldn't be split.

Blogs

SQL, MDX, DAX – the languages of data

By

Ramblings of a retired data architect Let me start by saying that I have...

Setting PK Names in Redgate Data Modeler

By

A customer was testing Redgate Data Modeler and complained that it auto-generated PK names....

Flyway Tips: AI Deployment Script Descriptions

By

With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...

Read the latest Blogs

Forums

Connecting Power BI to SSAS and effective user not working

By Paul Hernández

Hi everyone, Below is a consolidated summary of what we validated Architecture & data...

High Availability setup - has anyone seen this method?

By Paul Lancaster

Hi all, I recently moved to a new employer who have their HA setup...

Semantic Search in SQL Server 2025

By Deepam Ghosh

Comments posted to this topic are about the item Semantic Search in SQL Server...

Visit the forum

Question of the Day

Encoding URLs

I have this data in a SQL Server 2025 table:

CREATE TABLE Response
( ResponseID INT NOT NULL CONSTRAINT ResponsePK PRIMARY KEY
, ResponseVal VARBINARY(5000)
)
GO
If I want to get a value from this table that I can add to a URL in a browser, which of these code items produces a result I can use?

See possible answers