Who's On?

	Membership:
	Latest: SLockhart
	Past 24 Hours: 2
	Prev. 24 Hours: 0
	Overall: 5208

	People Online:
	Visitors: 361
	Members: 0
	Total: 361

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chesca	1042

access the sql created by default index

2 Replies

0 Subscribed to this topic

12 Subscribed to this forum

Sort:

Author

Messages

clpclp

New Member

Posts: 0

12/1/2010 6:02 PM

I'm new to Design Studio, so these questions may sound simple but I don't get it. Our problem: Our tech folks did a trace while a user was accessing inbasket data in Portal. The trace shows all the sql statements used in the process. When I open the .xml in Design Studio we only see a generic select statement in the Source, we do not see all the sql. How do we see it so we can change it? We want to select an index rather than letting it default to an index?
Another question, is the Script display available? I get an error about a script control component not being available, but I find no reference to it in the documentation I found. Thank you for any help.

Jason Beard

Veteran Member

Posts: 125

New Poster

Engaged Reader

Avid Reader

12/2/2010 4:07 PM

What action is the user taking? Is this just when logging in? When clicking the inbasket link? When clicking on an inbasket, or when clicking on a workunit within an inbasket?

Is this a delivered Lawson service or custom?
Is this a delivered Lawson displayexec or custom?

thanks,

clpclp

New Member

Posts: 0

12/2/2010 7:49 PM

A custom design studio which did not select any index in the Conditions tab; I have set the conditions to an index; I was hoping to see the expanded sql somewhere, but the only way we see it is when Tech Support/DBA puts a "trace" on it. Thank you. Everything is very slow when the user selects a workunit and it is being retrieved, they seem to wait forever! We thought since an index wasn't selected in the "detail" conditions we could select an index and it may be faster. It seems when an index is not selected that it defaults to the first defined index.