From: Larry on
Hi there,

I have an app that needs to upload flat files into my DB and each file will
range from a few hundred KB to a maximum of 16 MB. Normally it will be at
the low end of this range however. Ideally I'd like to process each upload
in a single transaction so that on any failure, none of the data will make
it into the DB. Since there can theoretically be several thousand uploads
going on simultaneously however (though in reality far less), can anyone
enlighten me on what the possible impact will be of running many
transacations at the same time. I'm concerned about the performance and
demand on memory so does anyone know how SQL Server might react in a
situation like this (will it cap the number of transactions beyond a certain
threshold for instance, queuing any waiting users until resources become
available). Thanks in advance.