Enhance the @max_rows_per_batch parameter (introduced in #94 by @EitanBlumin ) to add batch separators (ie. GO keywords) between the individual MERGE statements.
In addition to resolving #75, I have seen a 100% performance improvement from my testing on a table with 40k records.
Enhance the
@max_rows_per_batch
parameter (introduced in #94 by @EitanBlumin ) to add batch separators (ie.GO
keywords) between the individualMERGE
statements.In addition to resolving #75, I have seen a 100% performance improvement from my testing on a table with 40k records.
Tested on the
WideWorldImporters.Application.Cities
table which took 4 minutes to execute withoutGO
s and only 2 minutes withGO
s.Before-and-after:
The below was generated before and after this PR on the
AdventureWorks.Person.AddressType
table (@max_rows_per_batch=3
):Note: To preserve the previous behaviour of NOT including the
GO
keyword between merge batches, specify the following param:@batch_separator=NULL