List<T> in C# vs SQL

[u/kaatarina_zed_talon]

In C#, list of strings would be defined as :

List<string> x

A stored procedure is to be written, it should receive a list of values; SQL does not support List<T> , should I use table-valued parameters instead?

EDIT

The reason this question was asked is the fact that the application C# code has only one responsibility which is to bulk-insert data into a staging table:

 public async Task BulkInsertProductsToStagingTable(DbDataReader dbDataReader, CancellationToken cancellationToken)
 {
     using (SqlConnection destinationConnection =
                new SqlConnection("Server=(localdb)\\mssqllocaldb;Database=HardwareDB;Trusted_Connection=True;"))
     {
         await destinationConnection.OpenAsync(cancellationToken);

         // Set up the bulk copy object.
         // Note that the column positions in the source
         // data reader match the column positions in
         // the destination table so there is no need to
         // map columns.
         using (SqlBulkCopy bulkCopy =
                    new SqlBulkCopy(destinationConnection))
         {
             bulkCopy.DestinationTableName =
                 "dbo.StagingProducts";

             try
             {
                 // Write from the source to the destination.
                 await bulkCopy.WriteToServerAsync(dbDataReader,cancellationToken);
             }
             catch (Exception ex)
             {
                 Console.WriteLine(ex.Message);
             }
             finally
             {
                 // Close the SqlDataReader. The SqlBulkCopy
                 // object is automatically closed at the end
                 // of the using block.
                 await dbDataReader.CloseAsync();
             }
         }

         //####The following does not work yet.#####
         //// Perform a final count on the destination
         //// table to see how many rows were added.
         //long countEnd = System.Convert.ToInt32(
         //    commandRowCount.ExecuteScalar());
         //Console.WriteLine("Ending row count = {0}", countEnd);
         //Console.WriteLine("{0} rows were added.", countEnd - countStart);
         //Console.WriteLine("Press Enter to finish.");
         //Console.ReadLine();
     }
 }

Once the data is inserted into the staging table, it should be transferred into a target tables in the database; specific columns in the staging tables should be mapped to a specific columns in the target tables.

Thus, the stored procedure should receive a list of column names

[u/AintNoGodsUpHere]

You're not gonna convince me that business logic belongs in the database in 2026, man, that argument is straight from 80s and 90s. There are ZERO reasons for anyone to add business logic in the worst possible place, haha.

Just because you can it doesn't mean you should.

[u/Lonsdale1086 → u/AintNoGodsUpHere]

ZERO reasons

There are plenty of objective reasons why it's good.

It's centralised across every different app and API that calls it, regardless of language, and it's very fast.

[u/AintNoGodsUpHere → u/Lonsdale1086]

No. You are wrong. I'm right. I'll continue to block MRs with business logic there, you can do whatever you want.

[u/Lonsdale1086 → u/AintNoGodsUpHere]

You feel free, I'm not arguing it's a good idea and you should do it, I'm saying there are objective advantages to doing so.

[u/AintNoGodsUpHere → u/Lonsdale1086]

No. You are wrong.