Sorry, but this is probably a real "noob" question. I'm new to CR (using CRXI with a BOXI server). I'm accustomed to writing my own report SQL as stored procedures, but this is not an option for my current project.
I have an issue similar to the one posted by ddnh; that is, my reports involve massive recordsets, and any modification to the data fields locks CR for eons while it reprocesses the records. I've tried using a Record Selection Formula to limit the number of records, but the nature of the underlying query is such that this method is not proving to be effective.
What I really need is a way to return just the top n records. I've tried (unsuccessfully) to incorporate a SELECT statement in a SQL Expression to do this. The only workaround I've found is so far is to create a Command Object that uses the FETCH FIRST n ROWS ONLY clause (DB2 datasource) and link it to the main query. But, this is not very elegant. Plus, this linking nixes the use of server-side grouping and SQL Expressions — iow, it just ain't gonna fly.
Oh, and a test database containing a limited number of records is not an option. In fact, I'm actually forced to develop against production data, and I've been warned not to hose the network. Scary, huh?
Suggestions?
Thanks!
Mark
I have an issue similar to the one posted by ddnh; that is, my reports involve massive recordsets, and any modification to the data fields locks CR for eons while it reprocesses the records. I've tried using a Record Selection Formula to limit the number of records, but the nature of the underlying query is such that this method is not proving to be effective.
What I really need is a way to return just the top n records. I've tried (unsuccessfully) to incorporate a SELECT statement in a SQL Expression to do this. The only workaround I've found is so far is to create a Command Object that uses the FETCH FIRST n ROWS ONLY clause (DB2 datasource) and link it to the main query. But, this is not very elegant. Plus, this linking nixes the use of server-side grouping and SQL Expressions — iow, it just ain't gonna fly.
Oh, and a test database containing a limited number of records is not an option. In fact, I'm actually forced to develop against production data, and I've been warned not to hose the network. Scary, huh?
Suggestions?
Thanks!
Mark