RE: DECLARE CURSOR via ADOdotNet does not work

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hello Frank,

According to your description, you failed to use Server Cursor via ADO.net.
Correct? If I misunderstood anything here, please don't hesitate to correct
me.

I'm afraid to say ADO.net doesn't support cursors. This is because cursors
are database-specific technology, and are also resource-intensive. Early
on, the ADO.NET team decided that performance would be a major
consideration throughout the design of ADO.NET. Also important was default
performance, also known as performance out of the box. As a result, ADO.NET
team decide not to support cursors. If your application really needs this
feature, ADO is the preferred choice, no matter if you're building a
NET-managed system.

Hope this helps. If there is anything unclear or you have any more concern,
please feel free to let us know. We are glad to assist you.

Have a great day,
Best regards,
Wen Yuan
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@xxxxxxxxxxxxxx
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

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.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

.

Relevant Pages

  • RE: ASP.Net timeouts
    ... There's no managed call stack on the thread that throws this exception. ... Microsoft Online Support ... You can send feedback directly to my manager at: ... nature are best handled working with a dedicated Microsoft Support Engineer ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Theming not working in DLL
    ... the resource ID for a manifest in a DLL is typically different ... Microsoft Online Community Support ... You can send feedback directly to my manager at: ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.win32.programmer.ui)
  • Re: Why does this XPath not work
    ... Regarding on the error "Namespace manager or XsltContext needed." ... components only implemented XPATH 1.0 and XSLT 1.0 function set, ... Microsoft MSDN Online Support Lead ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.xml)
  • RE: Linking Mixed Mode and Managed Assemblies
    ... public void f ... Microsoft Online Community Support ... You can send feedback directly to my manager at: ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.languages.vc)
  • RE: Fix 954345 does not resolve problem for VS 2008 SP1
    ... My name is Hongye and it ... Microsoft Online Community Support ... You can send feedback directly to my manager at: ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.vsnet.general)