Very Sow Performance

[BFSmith]

I have noticed some VERY slow performance...nearly unacceptably so...when
dealing with a DDLB that gets its data from a secondary data source...in this
case it is a SQL Server view of a Customer master table...just bringing back
~12 columns of data...if I use Access to link a table to the view
(vwCustomerInfo_basic) it is very fast...when I use IP to select a
CustomerName on the DDLB...it takes 4-7 seconds for IP to return to the DDLB
field from which it originated...now-if I restrict the SQL view to include
only 100 records...the IP DDLB performance is very fast...the entire table
only contains ~9000 records...What is going on here? This performance is
pitiful.

 

[BFSmith]

I was able to reduce the size of the Returned Data Set from the view and
performance is acceptable now...but WATCH OUT....large data sets will cripple
a DDLB!

 

[Sheetal D [MSFT]]

Also, have a look at the following article:
http://msdn.microsoft.com/office/understanding/infopath/default.aspx?pull=/library/en-us/odc_ip2003
_ta/html/officeinfopathtroubleshootperformancebestpracticeguidelines.asp

Best Regards,
Sheetal D, MCSD.NET
Microsoft Developer Support

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Thread-Topic: Very Sow Performance
thread-index: AcY72Lvlk+yPI6DhTGuOTK7aOexWhQ==
X-WBNR-Posting-Host: 65.242.108.146
From: "=?Utf-8?B?QkZTbWl0aA==?=" <[email protected]>
References: <[email protected]>
Subject: RE: Very Sow Performance
Date: Mon, 27 Feb 2006 12:02:27 -0800
Lines: 18
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.infopath
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.infopath:27243
X-Tomcat-NG: microsoft.public.infopath

I was able to reduce the size of the Returned Data Set from the view and
performance is acceptable now...but WATCH OUT....large data sets will cripple
a DDLB!