Hi,

I am not sure if anyone else have noticed this, but as i am trying to resolve the peformance issue that my users are complaining about, i noticed that the duration shows many times more on the SQL proflier when these SP and query is being called from the application vs just running that same SP or query directly on the sql query window. This happens even if i am running the application on the same server that has the DB.

i am using LLBL with SQL 2005 DB (SP3) and Win Application (.Net 2.0)

Any Thoughts?

1) please don't post llblgen related questions in general chat, it's not monitored by the support team.

2) You're talking about an SP, which means a stored procedure? It is fetching data? Executing the stored proc is one thing, but retrieving the data into a datatable can take a long time, especially if there's network latency and if the data contains blobs/image/ntext/text fields as query tools don't retrieve blobs/image/ntext/text fields in general.

3) please post relevant llblgen pro version info. Thanks.

Sorry i will process it to the correct forum.

But even the Action Procedures that has a simple update statements seems to take long duration that is being called from app though.

LLBLGen wrote:

Sorry i will process it to the correct forum.

But even the Action Procedures that has a simple update statements seems to take long duration that is being called from app though.

Please use a profiler to determine what 'long time' means. So from the point where you call the method which will execute the stored procedure till that method exists: what is the exact time and what code is consuming it?

Also you really REALLY have to provide us more information, like llblgen pro version number, runtime lib buildnr, db type, ado.net provider type (if it's not in .net) and version etc.