Articles

SQLServerCentral Article

Non-Continous Replicaton and The LogReader

Last year Andy wrote about turning off the log reader as a way to reduce the overhead on a server, primarily when you have many logreaders running. In this follow up article he talks about the downside of using this technique and how the behavior of the logreader can be "tweaked" to make using non-continuous replication a little less of a headache.

(1)

You rated this post out of 5. Change rating

2002-03-28

5,155 reads

Blogs

SQL Server Journey till 2025 (brief)

By

Quick Summary for Microsoft SQL Server till 2025, I am fortunate to be part...

Building Power BI Reports: Desktop vs Fabric

By

Why this comparison feels confusing If you’re a Power BI report author who’s just...

Identity Columns Can’t Be Updated: #SQLNewBlogger

By

I’m not sure I knew identity column values could not be updated. I ran...

Read the latest Blogs

Forums

Can someone please explain what happens?

By skeleton567

I have mentioned this several times over several years.  Can someone please help me...

SELECT COUNT(DISTINCT) returns null when nothing is found instead of 0

By tim8w

SELECT COUNT(DISTINCT Component) AS Found FROM tblComponents WHERE(Component NOT LIKE '%[a-z]%') AND(LTRIM(RTRIM(Component)) = 'GM13622')...

Remotely Engineer Fabric Lakehouse objects: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Remotely Engineer Fabric Lakehouse objects:...

Visit the forum

Question of the Day

Creating JSON III

In a SQL Server 2025 table, called Beer, I have this data:

BeerIDBeerName
1Becks
2Fat Tire
3Mac n Jacks
4Alaskan Amber
8Kirin
I run this code:
SELECT JSON_OBJECTAGG(
    BeerID: BeerName )
FROM beer;
What are the results?

See possible answers