Azure Cosmos DB

SQLServerCentral Article

Quick and Effective Migration Between CosmosDB Collections Using ADF

  • Article

This document aims to explain the process of using ADF (Azure data Factory) to make a copy of a Cosmos DB (Instance A)  collection into a new collection in another Cosmos DB Instance effectively and cost effectively. For example, here is our  Instance A in the Data Explorer: Here is Instance B: We are looking […]

5 (1)

You rated this post out of 5. Change rating

2024-03-25

914 reads

Blogs

Time to Revive our YouTube Channel

By

It’s been forgotten about and neglected for few years but I’ve decided to dust...

Microsoft MVP 2025: Continuing the Data Platform Journey

By

I am honored to announce that I have been renewed as a Microsoft MVP...

What is KTLO? Keep The Lights On vs Project Work in Agile

By

🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

Import/Export SSMS Settings issue

By Brandie Tarvin

I have tried a number of times to export and then import my SSMS...

FQDN - SQL cannot connect when the server name has backslash

By krypto69

Hi I need to connect to a SQL server via FQDN -  that is...

Visit the forum

Question of the Day

Query Plan Regressions --

For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question:  You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?

See possible answers