Articles

Technical Article

Exploring 'ON DELETE SET NULL' in SQL Server 2005

At first glance, the 'ON DELETE SET NULL' option in SQL Server 2005 may not seem like a big deal, but once you've seen how it can be used, I think you will be impressed. The basics? If Order.CustomerID has a foreign key to Customer.CustomerID and a customer is deleted, 'ON DELETE SET NULL' causes the CustomerID field in each of that customer's orders to be set to NULL.

2005-02-26

946 reads

External Article

Review: Access Workbench

For some years, I have been asked to review a product that I have only just gotten around to looking at. It was developed by Garry Robinson, who publishes a very useful web resource called vb123.com and who recently wrote one of the best books on Access security, Real World Microsoft Access Database Protection and Security. The product is called The Access Workbench (TAW)

2005-02-25

2,359 reads

SQLServerCentral Article

Access to SQL Server: Getting Started with Access Projects

SQL Server 2000 and Access databases are two technologies closely linked with the new Access ADP format using SQL Server as the basis for the code. Access Projects are also a way to closely link the two products together and take advantage of each to produce an application very easily. Author Kathi Kellenberger brings us part 3 of her Access series with a look at Access Projects.

(1)

You rated this post out of 5. Change rating

2005-02-24

10,024 reads

Technical Article

Review of Adventnet SwisSQL SQLOne Console, SQL Query Converter

Recently, SwisSQL approached me for a review of their product that can convert SQL statements from one dialect to another. They told me that "SwisSQL SQLOne Console" is a GUI application that can convert SQL statements from one RDBMS implementation to another and the dialects supported include:

Microsoft SQL Server
Sybase
Oracle
IBM DB2
Informix
MySQL
PostgreSQL
MySQL
and last but not the least, ANSI SQL

2005-02-24

1,438 reads

Technical Article

Migrating Microsoft Access Applications to SQL Server

Microsoft Access targets individual information workers and small teams that use the Microsoft Office System to track, manage, prioritize, and act upon an increasing volume of business information. The data stored in these databases rarely justifies moving to a more robust platform until the application begins expanding into departmental scenarios. When this happens, it is worthwhile to consider moving the data into a more robust platform for enhanced reliability, scalability, and greater IT control. In most cases, the data can be moved through a process called "upsizing" while the Access application front-end continues to provide information workers with access to critical data. Microsoft has created resources in the following three categories to help manage Access data in your organizations:

2005-02-23

3,934 reads

Blogs

Presenting with Visual Studio Code

By

A while back I wrote a quick post on setting up key mappings in...

Advice I Like: In 100 Years

By

In 100 years a lot of what we take to be true now will...

dataMinds Saturday 2026 – Slides

By

At Saturday the 21st of February I’m presenting an introduction to dimensional modelling at...

Read the latest Blogs

Forums

connections vs apis

By stan

hi , i hear more and more that we have too many connections to...

is it true we cant debug c# scripts in ssis anymore under vs

By stan

Hi, i'm running vs2022.   I'm trying out a c# script that i'd like to...

Missing the Jaro Winkler Distance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Missing the Jaro Winkler Distance

Visit the forum

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