Enhacement: Optimize the 'InsertAll' way of insertion.

[mikependon]

Description

Currently, the 'InsertAll' is generating a packed-statements of INSERT statement.

Let us say, you are inserting 10 rows of customer.

INSERT INTO [dbo].[Customer] (Name, SSN, Address, CreatedUtc, ModifiedUtc) VALUES (@Name, @SSN, @Address, @CreatedUtc, @ModifiedUtc);
INSERT INTO [dbo].[Customer] (Name, SSN, Address, CreatedUtc, ModifiedUtc) VALUES (@Name1, @SSN1, @Address1, @CreatedUtc1, @ModifiedUtc1);
...
INSERT INTO [dbo].[Customer] (Name, SSN, Address, CreatedUtc, ModifiedUtc) VALUES (@Name9, @SSN9, @Address9, @CreatedUtc9, @ModifiedUtc9);

It is more optimal to use it this way.

INSERT INTO [dbo].[Customer] (Name, SSN, Address, CreatedUtc, ModifiedUtc)
VALUES
(@Name, @SSN, @Address, @CreatedUtc, @ModifiedUtc),
(@Name1, @SSN1, @Address1, @CreatedUtc1, @ModifiedUtc1),
...
(@Name9, @SSN9, @Address9, @CreatedUtc9, @ModifiedUtc9);

Acceptance Criteria

• The Unit Tests for SQL Builder must be rewritten.
• Ensure that the Integration Tests are all passing.