Scripts

Technical Article

BASE64 Encode and Decode in T-SQL - optimized

This is just an optimized version of Daniel Payne's two scripts, base64_encode and base64_decode, with changes to end-of-block handling and a bug fix or two. If the encoded string ends in =, the last character is truncated. If ending in ==, two characters are chopped off. That seems better than replacing NUL characters with spaces, […]

(5)

You rated this post out of 5. Change rating

2006-12-18 (first published: )

7,760 reads

Technical Article

HexToInt

Challenged by Hans Lindgren's stored procedures of the same name, I created this. Note that it produces strange results on non-hexadecimal strings, overflows at 0x80000000, and could have issues with byte-ordering on some architectures.How does it work? Well, the distance between one after '9' (':') and 'A' is 7 in ASCII. Also, if I subtract […]

You rated this post out of 5. Change rating

2006-12-15 (first published: )

238 reads

Technical Article

SQLStackEngine - simulate a character stack

SQLStackEngine - simulate a character stack using a string.  This script was developed specifically to support the operator stack in SQLCalcEngine(also on this site).  However, the implementation is complete enough to stand on its own.There are several functions in the package that correspond to the common stack functions of Push, Pop, Peek, and so on.In […]

You rated this post out of 5. Change rating

2006-12-12 (first published: )

164 reads

Technical Article

Search for an expression in the body of programmable objects

Sometimes you want to modify an object (like a stored procedure, Function, trigger and view) and you can not remember the name of that object, but you remember some words of the comments that you placed in the body of that object. If this is your case, you can use the following procedures depending on […]

You rated this post out of 5. Change rating

2006-11-30 (first published: )

198 reads

Technical Article

Remove Exec Permissions To Extended Stored Procs

I created this script to simplify the process of restricting access to high risk extended stored procedures. It will find any user or role which has execute permissions on any of the stored procedures in the "#High_Risk_Stored_Procs" temp table and will generate the relevant revoke statements to remove those permissions.The current list of stored procedures […]

(1)

You rated this post out of 5. Change rating

2006-11-27 (first published: )

678 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