.NET database calls slow when using COM Interop, fast via VB6

tags:

views:

123

answers:

2

+1 Q:

.NET database calls slow when using COM Interop, fast via VB6

A:

Beware of caching and parameter sniffing. I had some weird performance problems with some stored procedures and was able to narrow it down to some bad optimizations. http://blogs.msdn.com/b/khen1234/archive/2005/06/02/424228.aspx

bugtussle 2010-10-07 21:35:17

If I test my query with SQL 2005 Server, I won't have no longer see this problem ?

Florian 2010-10-08 06:29:01

I test the query with SQL Server 2008 but I have the same result.

Florian 2010-10-08 07:15:32

@bugtussle -- it didn't directly answer the question, but I hate to see the bounty go to waste, and since I can't split the bounty, here you go.

LittleBobbyTables 2010-10-14 02:42:56

I have seen this problem before. It was slow in vb but fast via EM. It was parameter sniffing, not sure if the environment gave clues about how to process the request. Also, it is my understanding the com interop may be slow compared to a native solution since the data has to be marshalled.

bugtussle 2010-10-15 16:24:15

A:

Identical execution plans but different timings. Are the connection settings for both connections identical? Any difference in server load?

KristoferA - Huagati.com 2010-10-08 07:21:43

Regarding, the server load, there is no difference. It's the same server and queries are tested more times and each time I have the same result.

Florian 2010-10-08 07:30:17

Regarding the Connection settings, Normally there is no difference too. But, I read that an .NET application accessing data with ADO (or RDO ?) is slower than ADO.NET...

Florian 2010-10-08 07:33:14

ansaurus

tags:

views:

answers:

.NET database calls slow when using COM Interop, fast via VB6

related questions