Updated: Jan 2008. One of the big changes in SQL Server 2005 is the integration of the CLR into the relational engine itself. This is probably the biggest reason for the delays in completing the product and it is a controversial decision. Steve Jones spends a few minutes looking at the pros and cons of having the CLR integrated and possible implications for DBAs.
This white paper describes how application developers can incorporate data quality into their Microsoft SQL Server 2005 Integration Services solutions.
Part one of this series illustrates how to enable Change Data Capture on a database, and on a table, and how to keep track of Data Definition Language changes on a table.
In order to support multiple environments, a number of choices, not readily apparent, need to be made. This article outlines one approach that is working.
SQL Server 2005 has greatly expanded the capabilities of SQL Server in many different areas. One of those that has matured greatly is the integration of XML data inside SQL Server. Longtime writer and guru Michael Coles brings us the first part of a two part series on XML ion SLQ Server 2005.
How interesting would it be to not have to guesstimate what size server to buy for your next application? Steve Jones may have found a way to help you.
This article explores the data types and methods used for storing BLOBs (Binary Large Objects), such as images and sounds, inside SQL Server.
By Steve Jones
Last week I spent a few days in Cambridge, UK for the Redgate Company...
By Steve Jones
Recently I had someone internally ask about whether SQL Source Control supports Git Hooks....
By Steve Jones
At Redgate, we’re experimenting with how AI can help developers and DBAs become better...
I'm running a group MSA for the database engine and SQL Agent in a...
All, My query is as follows: SET DATEFORMAT dmy SELECT p.query_id, DATEADD(MICROSECOND,-rs.max_duration,rs.first_execution_time) AS starttime,...
Comments posted to this topic are about the item Encoding Strings
I have this code in SQL Server 2025. What is the result?
DECLARE @message VARCHAR(50) = 'Hello SQL Server 2025!'; DECLARE @encoded VARCHAR(MAX); SET @encoded = BASE64_ENCODE(@message); SELECT @encoded AS EncodedResult;See possible answers