On Friday the 24th, a virus that preys on a SQL Server vulnerability began to attack networks, taking down many networks. This brief network describes the virus and how to protect yourself from it.
2003-01-27
10,815 reads
Moving SQL Server from one computer to another is not a very difficult thing to do, but it often stumps newbie DBAs. Of course, it needs careful planning to ensure that the SQL Server is moved completely and properly to the new machine, and with a minimal downtime and no data loss. This article introduces you to a couple of methods you can employ to move/migrate SQL Server from one computer to another.
2003-01-24
107 reads
This one is pretty interesting, Andy discusses a few things he sees in comments that not only fail to add value, they end up costing extra time. There's room for discussion here, but definitely a discussion worth having - comments can make you or break you, here's a chance to think about what you think is important in commenting and pass that on to your development team.
2003-01-23
11,109 reads
This application will convert your schema into a standard Word document. Try before you buy, they have two versions - both under $200.
2003-01-23
623 reads
Because of the way date and time values are stored in SQL Server, searching for a particular date or time is not as straightforward as you might think it would be. This article describes how date/time values are stored, how the database design can simplify (or complicate) data retrieval, and how to query date/time data to get the right results every time.
2003-01-21
36,121 reads
This article is the first of a series that I plan on writing and placing on my website to help other DBAs in auditing a new SQL Server environment. This article deals with determing which SQL Server logins have weak passwords, with the definition of weak being, no password, password the same as the login name or having a password of only one character.The stored procedure used for this article is embedded in the article and it has been submitted as a independent script named spAuditPasswords.
2003-01-21
66 reads
Continuing with our worst practices series, Steve Jones looks at another administrative no-no. Making a change to your live system on the fly.
2003-01-20
7,777 reads
David Gugick, SQL Server performance expert and software developer, provides over 100 tips on how to boost SQL Server performance.
2003-01-17
88 reads
You have spent thousands of dollars on that cool technology; clustering, redundant controllers, redundant disks, redundant power supplies, redundant NIC cards, multiple network drops, fancy tape backup devices and the latest and greatest tape technology. You are all set. There is no way your going to have downtime. Right?
2003-01-16
4,925 reads
Andy had a semi-disaster similar to the one he wrote about last year. Interesting to see the kinds of problems that happen to other people. This article raises some interesting points that are outside the scope of basic disaster recovery, looking at how/when to move databases to a different server and how to reduce the server load dynamically.
2003-01-14
7,063 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...
Hello, I inherited a number of tables with like 20-30 column using nvarchar(256) in...
Hi, i'm running vs2022. I'm trying out a c# script that i'd like to...
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