Checking program code into source control is a daily ritual for most developers, but versioning database code is less well-understood. Grant Fritchey argues that getting your databases under source control is not only vital for the stability of development and deployment, but it will make your life easier when something does go wrong.
SQL Server 2012 introduced columnstore indexes, which can immensely improve the performance of OLAP queries. How were they updated and improved in SQL Server 2014?
Many DBAs back up their user databases, but not their system databases. Whatever the reason for the lack of a backup, John Grover explains how to save yourself (mostly) should you ever find yourself with no viable master database and no good backup.
Red Gate’s running a half-day training workshop at their UK head office in Cambridge on Aug 8. It’ll show you how to link your database source control repository to your build system as the starting point for continuous integration.
A lot of numbers that we use everyday such as Bank Card numbers, Identification numbers, and ISBN codes, have check digits. As part of the routine data cleansing of such codes we must check that the code is valid- but do we? Dwain Camps shows how it can be done in SQL in such a way that it could even be used in a constraint, and keep bad data out of the database.
The SSC team has put together a little quiz on database source control to go with Rob Richardson, Robert Sheldon, and Tony Davis' new book, SQL Server Source Control Basics. Do you daydream about source control... or daydream to avoid it?
This article demonstrates a method of importing a data file directly into a temporary table and selectively inserting data from the temporary table into a SQL Server table, all in a single set of SQL commands.
A good DBA needs to have good technical skills but he also has to have good personal skills. In this article, Greg Larsen discusses the personal skills a DBA should have.
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