if i created many processes with multithreads writing and reading to
my single SQL table every half a second or a hundred miliseconds, can
the server still perform well as it supposed to under such a
situation? Any limitation to this?

<panabong [at] gmail.com> wrote in message
news:89cf4dfb-45bd-40e8-b4ad-daf0b4994ebe [at] d2g2000pra.googleg roups.com...
>
> if i created many processes with multithreads writing and reading to
> my single SQL table every half a second or a hundred miliseconds, can
> the server still perform well as it supposed to under such a
> situation? Any limitation to this?

'it depends'

Keep in mind SQL Server is designed to have many people accessing it at
once.

And depending on how your indexes are and what your queries look like you
may be just fine.

However, if you're looking to insert a lot of data as quickly as possible,
you may want to look at something like Bulk Copy.


--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html