I'd suggest getting performance metrics on individual statements within the query. AND, as has been said several times, the execution plans for the queries. Those two bits of data are...

Try batching based on 102,400 rows. The reason I say that is because less than 100,000 rows in a batch and columnstore indexes use the delta store until you get...

Hi Jonathan, Thanks for the input. I would like to know if there is any implications/perf issues of using MERGE statement especially when dealing large sets of data?...

Hi Grant Sir,

Thanks for the pointers and sharing the link of capturing Waits. will check with them replace old join syntax's with ANSI joins.

Couple of questions:

1. for conditions like...

Literally no way to really answer this question for you. Scale depends on so many different factors.

Let's look at it like this. The various different data management systems that are...

More data. "Something is slow and here are a bunch of wait stats" doesn't tell us anything. I'd suggest enabling Query Store on the database in question. It's relatively lightweight...

First, not trace. Use Extended Events. It puts far, far less of a load on the system. Plus, you're on SQL Server 2017. Every single piece of new functionality is...

Weeks? You're doing it wrong. You should be able to...

You can absolutely create logins (and there are several choices on how to do this) that only have enough privileges to do certain things and not others. And then, yeah,...

Can a column contain more than one data type? The short answer is no, unless the column is of data type variant. I do not recommend using this. I...

Microsoft has some fantastic documentation on exactly how to get your backups done in Azure VMs. Pretty much everything you need. Don't forget though, untested backups are unknown. The...

You mean a computed column? Probably not the greatest of choices, but yes. As long as it's unique and the...

I had to check, and yep, mainstream support ended in 2019. Extended support ends in less than two years. Don't "upgrade" to 2014. Move on to one of the three...

Strong, strong suggestion, if you're upgrading from 2000, 2008, 2012, skip 2014. Go to 2016 or greater. The reason is simple. 2014 introduced a new cardinality estimation (CE) engine, but...

Except for columnstore indexes, every test I've ever seen says reorganize is a waste of time. You may still hit timeouts doing a rebuild, but yeah, I'd stop doing the...