External Article

Understanding the SQL Server 2012 BI Semantic Model (BISM)

SQL Server 2012 introduced an unified BI Semantic Model (BISM) which is based on some of the existing as well as some new technologies. This model is intended to serve as one model for all end user experiences for reporting, analytics, scorecards, dashboards, etc. In this tip, I will talk in detail about the new BISM, how it differs from earlier the earlier Unified Dimensional Model (UDM) and how BISM lays down a foundation for future.

External Article

SQL Server Transaction Log Fragmentation: a Primer

Generally, you will have no need to worry about the number of virtual log files in your transaction log. However, if you use the default settings for 'auto-grow', you can end up with such 'fragmentation' in your transaction log as to affect performance noticably. How can this be avoided? How can you tell it's a problem? What do you do about it? Greg explains.

Blogs

Flyway Tips: AI Helps with Commit Messages

By

At Redgate, we’re experimenting with how AI can help developers and DBAs become better...

Startup scripts in SQL Server containers

By

I was messing around performing investigative work on a pod running SQL Server 2025...

Using SQL Compare with Redgate Data Modeler

By

Redgate recently released SQL Compare v16, which included a new feature to work with...

Read the latest Blogs

Forums

Encoding Strings

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Encoding Strings

Deep Learning and Craftsmanship Matter

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Deep Learning and Craftsmanship Matter

Building a Real-Time Analytics Pipeline with Azure Stream Analytics and SQL Server

By AR

Comments posted to this topic are about the item Building a Real-Time Analytics Pipeline...

Visit the forum

Question of the Day

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