SQL Server has this concept of an owner of an object. Similar to the concept of schema, but not quite the same. Best practice dictates that all objects in SQL Server be owned by dbo, but that does not always happen. Tracking those objects down might be a pain, but Santveer Singh brings us an easy way of doing this.
Learn how to achieve scalable, high-performance merge replication applications. (White Paper)
Destroyed your database? Corrupted files? What about corrupted records? What do you do in SQL Server? MSSQLRecovery is a product that can help you with this and more. Read this review by Dale Elizabeth Corey and see if this product might be something you can use.
One of the age old problems in DTS is moving packages between your development, test and production environments. Typically a series of manual edits needs to be done to all the packages to make sure that all the connection objects are pointing to the correct physical servers. This is time consuming and gives rise to the possibility of human error, particularly if the solution incorporates many DTS packages. Many companies have provided their own custom solutions for managing this problem but these are still workarounds for a problem that is inherently DTS's.
Deploying a SQL Server database with your software can be tricky. It's easy to forget something that you added to development when trying to script out or detach and copy a database. And there's the whole problem of integrating the installation or upgrade into your main installation routine. New author Mark Vermeulen takes a look at Red Gate's SQLPackager, designed to make the job of deploying a database much easier.
The key to effective security is embracing it as an ongoing process rather than a one time event. This document examines how database security can be enhanced with a proactive security lifecycle approach.
A short survey from Microsoft looking for feedback from users in order to try and improve the application development process. If you build applications with MS technolgies, especially SQL Server, take a moment and respond.
SQL Server has a rock solid backup and restore routine. However, it is not the most efficient way of handling the backups and restores. Neither in terms of time or space required. A number of software vendors have developed their own additions to SQL Server that accelerate or compress the backups (or both). Wesley Brown has taken four of these products into his environment and run some comparisons. Read about large databases in part 2 of this series.
SQL Server depends heavily on good indexing to perform well. The optimizer requires relevant and intelligent indexing in order to do its job well. Author Andre Vigneau brings us a script that he uses to detect possible index problems in the database design as well as a number of hints to ensure that your database is performing optimally.
SQL Server has a rock solid backup and restore routine. However, it is not the most efficient way of handling the backups and restores. Neither in terms of time or space required. A number of software vendors have developed their own additions to SQL Server that accelerate or compress the backups (or both). New Author Wesley Brown has taken four of these products into his environment and run some comparisons. Read part one of his review.
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...
By Steve Jones
I haven’t done one of these in awhile, but I saw an article recently...
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