Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Creating IQD files in Framework Manager - Long run times

Status
Not open for further replies.

Vivarto

Programmer
Nov 27, 2005
43
AU
Hi,

I'm building IQD files from Framework Manager and I've found that it's taking longer and longer for the .IQD files to be written to the file system. The more complex the SQL generated the longer it takes. It appears as if the SQL statements are actually being run rather than just written to the file (which sort of makes sense). I currently have all of my IQD files being built from a single package which is rapidly becoming impractical.

So, could anyone confirm that the SQL is being run and if so is there anyway to either stop this or limit the test to a few rows? The documentation I've found doesn't give much insight.

Thanks in advance.
 
I am having a very similar problem. It does appear that the SQL statements are being run on IQD creation, maybe to identify problems/conflicts sooner than later. We're up to a 2 hour IQD creation now, so it's pretty painful.
 
Are you both running Cognos 8? I haven't seen this behavior in ReportNet, our IQDs generate quickly.
 
I'm getting the long times generating the IQDs with Framework Manager 8.2
 
One of our iqd's is taking over 2 hours running 8.1. The model does include 104 columns, a number of calculated fields, group by's, etc. I don't remember ever seeing an iqd take near this long when creating iqds with Impromptu 7.3.

Thanks!
 
My group is having the same issue. We have a prod. env of Cognos 8.1 mr2 with an oracle 10g backend; also have a test env of 8.2 with and oracle 10g backend. Creating the publishing the model (complex model) to the db just takes a minute or two. Externalizing the iqd appears to run the query in the db (takes an hour and a half). Why would it run the whole query? Why would it not just validate the syntax? Why would it be different writing to a file vs writing the same stuff to the content store?

Has anyone else experienced this? Any solutions or workarounds?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top