Part I of this series illustrated how to use simple case functions in queries. This installment discusses how to use case functions in different types of scenarios.
2008-04-04 (first published: 2007-04-12)
10,572 reads
Learn about common data integrity issues, and see how Analysis Services 2005 gives you the tools to handle them.
2008-04-04
1,985 reads
Few would disagree that striving for a loosely coupled design is a bad thing. Unfortunately, the software we typically design is much more tightly coupled than we intend. How can you tell whether your design is tightly coupled?
2008-04-04
1,816 reads
Blocking occurs in SQL Server 2005 when one process has one or more records locked, while another process tries to acquire locks on the same set (or subset) of records. This can create a daisy-chain of processes waiting to complete their work.
2008-04-03
3,069 reads
A look at how you can implement error handling in your stored procedures.
2008-04-03
4,813 reads
Indexing a SQL Server database in some respects is considered both an art and a science. Since this is the case, what are some considerations when designing indexes for a new database or an existing one in production? Are these the same types of steps or not? Do any best practices really exist when it comes to indexing? Where does indexing fall in the priority list from an application or production support perspective?
2008-04-03
4,878 reads
An article that speaks about some of the issues faced by the Author, during his Data Integration Project using SSIS. Shared with you in this article are the issues he was faced with and the solutions applied.
2008-04-02
3,879 reads
2008-04-02
2,786 reads
In this article I discuss a new feature in SQL 2008, table-valued parameters and particularly the restriction that they have to be read-only. I argue that this makes this feature considerably less useful that it could be, and that in order to build scalable applications be able to pass read-write table parameters between stored procedures is essential.
2008-04-02
2,677 reads
2008-04-01
4,964 reads
A while back I wrote a quick post on setting up key mappings in...
By Steve Jones
In 100 years a lot of what we take to be true now will...
At Saturday the 21st of February I’m presenting an introduction to dimensional modelling at...
Hi, i'm running vs2022. I'm trying out a c# script that i'd like to...
Comments posted to this topic are about the item 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