It actually is not that low. I have a stored procedure does the activity
that I described and we will have about 500 call per second.
>> Hi,
>>
[quoted text clipped - 7 lines]
> this is a very low activity. DOn't optimize it unless you are
> experiencing slowness.
Charles Wang [MSFT] - 24 Jul 2008 06:29 GMT
Hi Max,
Do you have the requirement that you need to concurrently insert a large amount of data into your
database table? If so, using a heap table with only non-clustered index would be helpful for
improving INSERT performance. However if you just have one job insert a large amount of data, I
recommend that you create a clustered index on the table since not only it can bring better
performance on INSERT/UPDATE/DELETE operation but also on SELECT operation. I would like to
recommend the following article for your reference:
Comparing Tables Organized with Clustered Indexes versus Heaps
http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/clusivsh.mspx
Appreciate your understanding that for such performance advisory question, actually there is no
BEST setting. We can just give you some general suggestions and whether or not it is really helpful
for you, it requires your performing more tests to check if you encounter any performance issue.
If you have any other questions or concerns, please feel free to let us know.
Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@microsoft.com.
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notifications.
Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
Alex Kuznetsov - 24 Jul 2008 15:06 GMT
> It actually is not that low. I have a stored procedure does the activity
> that I described and we will have about 500 call per second.
[quoted text clipped - 10 lines]
> > this is a very low activity. DOn't optimize it unless you are
> > experiencing slowness.
Just a guess: is it something like a queue? If yes, have you tried any
ready made implementation of a queue?