We asked our vendor to put our custom codes into stored proc for an ETL process on our SQL server. The ETL process is going to deal with transformation and loading of many rows(like 200,000+ rows) with Insert/Update/Delete etc.
Instead, the vendor insisted that to put the custom codes in LinQ compiled codes, and installed the C# codes on the SQL server. So we have no access to change the codes, but to work with them in the future. That is just wrong.
They kept telling our business users that LinQ is faster than stored proc. I searched online, that is no clear cut winner of LinQ vs. Stored procs. Can you help? so I can fight the battle against this greedy vendor. Thanks
Thursday, April 07, 2011 4:02 PM
Microsoft is conducting an online survey to understand your opinion of the Msdn Web site. If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site.