The working life of the DBA can be punctuated by surprises, but they aren't generally nice surprises. This is especially true if the DBA is not checking and monitoring the databases for obvious things such as database corruption, and disk space. However, the really scary surprises are less obvious and provide fewer warning signs. Brent Ozar gives six scary surprises that can be avoided by the shrewd DBA.
2017-10-31
7,099 reads
SQL was designed to be a third-generation language, expressed in syntax close to real language, because it was designed to be easy for untrained people to use. Even so, there are ways of expressing SQL Queries and data manipulation in ways that make it easier for the database engine to turn into efficient action. and easier for your colleagues to understand. Robert Sheldon homes in on data querying and manipulation and makes suggestions for team standards in SQL Coding.
2017-08-25
5,735 reads
Greg Larsen shows you how to use the Transaction ID value to identify the object_id for a deleted table.
2017-08-22
4,419 reads
2017-06-01
1,046 reads
Bhavesh Patel shows how to validate specific use-cases for integer and decimal values in SQL Server.
2017-05-31
3,649 reads
2017-05-30
1,142 reads
A series of arguments with developers who insist that fuzzy searches or spell-checking be done within the application rather then a relational database inspired Phil Factor to show how it is done. When the database must find relevant material from search terms entered by users, the database must learn to expect, and deal with, both expected and unexpected.
2017-04-27
7,260 reads
Keeps a memory leak under control until the bug fix is developed and applied. Short term band aid.
2017-04-25 (first published: 2017-04-13)
548 reads
2017-04-12
7,058 reads
Audit your SQL logins to find passwords that have never been changed or that are very weak.
2017-04-04
4,385 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