2015-05-21
1,254 reads
2015-05-21
1,254 reads
It is no good doing some or most of the aspects of SQL Server security right. You have to get them all right, because any effective penetration of your security is likely to spell disaster. If you fail in any of the ways that Robert Sheldon lists and describes, then you can't assume that your data is secure, and things are likely to go horribly wrong.
2015-05-13
9,527 reads
Sometimes you need to reach outside a database and access data and objects from multiple databases, which raises some security issues and increases the complexity of data access. In this stairway level, you’ll learn about cross-database ownership chaining so that you can reach across database boundaries securely.
2024-05-08 (first published: 2015-04-08)
11,318 reads
2015-03-25
1,774 reads
2015-03-19
1,978 reads
2015-02-10
1,651 reads
2015-02-09
1,616 reads
2015-02-05
1,905 reads
Database ownership is an old topic for SQL Server pro's. Check this simple lab to learn the risks your databases can be exposed to.
2015-01-29
11,321 reads
Alter database owner to SA from any other user details against all user databases
2019-05-03 (first published: 2015-01-13)
1,863 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