Articles

Technical Article

Displaying and Removing Unprintable Hexadecimal Characters from SQL Server Data

There are times when you might need to look at your SQL Server data in hexadecimal format. Occasionally some string data will contain unprintable characters, which can cause downstream problems, if not detected and removed. Read on to learn how to display and remove unprintable hexadecimal characters from SQL Server data.

You rated this post out of 5. Change rating

2018-09-11

2,713 reads

SQLServerCentral Article

Configuring Service Broker Architecture

Learn how to configure technically reliable, consistent, robust, efficient, asynchronous message queuing and processing mechanism to start developing highly available, scalable applications based upon the service–oriented architecture.

(9)

You rated this post out of 5. Change rating

2018-09-07 (first published: )

10,979 reads

Blogs

Keeping Redshift System Table History Past 7 Days with S3 Tables

By

Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...

Updating the Data API Builder

By

I was updating my session for the Data API Builder (DAB) recently, mostly to...

T-SQL Tuesday #202 Invitation: That One SQL Server Outage You’ll Never Forget

By

I am excited to host T-SQL Tuesday for the first time. I want to...

Read the latest Blogs

Forums

Practical Ways to Approach SQL Server Problems and Case Studies

By academicexpertt

Working with SQL Server can involve more than just writing queries. Understanding database design,...

Measuring Productivity

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Measuring Productivity

Importing Excel files into SQL Server using DuckDB and Python

By Cláudio Tereso

Comments posted to this topic are about the item Importing Excel files into SQL...

Visit the forum

Question of the Day

Tracking All the Queries

I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?

See possible answers