Security

Technical Article

SQL Server 2000 SP3 and xp_cmdshell Woes

  • Article

The problems caused by the SQL Sapphire Worm, also know as the SQL Slammer, have caused many sites to do a quick upgrade to SQL Server 2000 Service Pack 3 (SP3). It includes the fix that prevents infection by the worm. While moving to the latest service pack is usually a good thing, to do so without thorough testing risks breaking a working application. That is exactly what happened to one of my clients over the weekend.

2005-11-02

2,068 reads

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