Stop SQL Injection Attacks Before They Stop You
This article discusses: How SQL injection attacks work, Testing for vulnerabilities, Validating user input, Using .NET features to prevent attacks, and Importance of handling exceptions
Getting The Most Out of SQL Server 2005 UDTs and UDAs
The CLR integration in SQL Server 2005 greatly expands on the capabilities of the SQL Server platform. One new area is the ability to build user-defined types and user-defined aggregates. Solomon Rutzky brings us a way to get around some of the limitations in this area with his SQL# toolkit.
Opening Day
Today is the opening day for the PASS conference here in Denver and it's kind of exciting. As many of you read this, I've hopefully gotten Simon Galbraith, owner of Red Gate software, and my boss, out here at the ranch shoveling manure. He's anxious to get on the ATV for a ride, so maybe I can work out a deal to reduce my workload 🙂
Close These Loopholes - Testing Database Modifications
In the latest in their popular series on 'Unit Testing' database development work , Alex K and Alex S give some examples of unit testing Database Modifications
Upgrading to SQL Server 2005: A dozen must-have tips
We've compiled a list of our dozen most popular tips in the area of upgrading to SQL Server 2005 and they run the gamut.
From DBA to DWA
Everyone wants to know what a DBA does and it is becoming a hard question to answer as the responsibilities and capabilities of database platforms increase. Longtime author Vincent Rainardi brings us the proposition of a new type fo DBA, one that focuses more on data warehousing.
Indy Tech Fest
There's a free event in Indianapolis for SQL and .NET developers. It's on October 13th and it's jointly sponsored by the .NET and SQL users groups. If you're in the area reigster and support this group.
Oh Lawd, it's the end of the world
There have been some strange things that have happened in this world that I would never have expected. The Red Sox winning the World Series, Macs with Intel processors, and are things I never thought I'd see. But none of the them seems as strange as this to me.
Unethical or Just Sneaky
One of the fundamental rules of a stable, controlled production system is that you apply updates singly, after they've been tested, and you document the change. This way you can ensure that if a problem occurs, you can do some backtracking to see what might have caused instability.
Where To Find Integration Services Packages in SQL Server
An article explaining where to find packages when saved to SQL Server.
Blogs
Presenting with Visual Studio Code
A while back I wrote a quick post on setting up key mappings in...
Advice I Like: In 100 Years
By Steve Jones
In 100 years a lot of what we take to be true now will...
RANK() vs DENSE_RANK(): #SQLNewBlogger
By Steve Jones
I haven’t done one of these in awhile, but I saw an article recently...
Forums
is it true we cant debug c# scripts in ssis anymore under vs
Hi, i'm running vs2022. I'm trying out a c# script that i'd like to...
Missing the Jaro Winkler Distance
Comments posted to this topic are about the item Missing the Jaro Winkler Distance
Question of the Day
Missing the Jaro Winkler Distance
I upgraded a SQL Server 2019 instance to SQL Server 2025. I wanted to test the fuzzy string search functions. I run this code:
SELECT JARO_WINKLER_DISTANCE('tim', 'tom')
I get this error message:Msg 195, Level 15, State 10, Line 1 'JARO_WINKLER_DISTANCE' is not a recognized built-in function name.What is wrong? See possible answers