|
|
You're in the
sql server reporting services
group:Reasonable size of rdl file?
sql server reporting services:
Undo/Redo in Report Designer is somewhat memory intensive. You may find that
you need to restart Report Designer if you use this feature extensively during a single editing session. Another aspect is that very large RDLs, especially those that contain a large number of images, can impact the Report Designer's editing experience. In general, Report Designer should be able handle this report. -- Bruce Johnson [MSFT] Microsoft SQL Server Reporting Services This posting is provided "AS IS" with no warranties, and confers no rights. "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in message news:eDPik7ymEHA.3944@TK2MSFTNGP10.phx.gbl... [quoted text, click to view] > I'm working with a report that will produce 5 printed pages with key data > for a company. Each page will contain from 3 to 12 diagrams, there will be > 39 diagrams totally in the rdl file. Plus some text boxes etc. > Each diagram has a dataset, plus some support datasets. Totally about 45 > datasets (all using stored procedures). > > I currently have 15 diagrams, and the rdl file is 140kB. > > Am I stretching it? Experiences? > > > More detailed information: > The reason for keeping it in one rdl file is that a scheduled data driven > subscription will produce one PDF file per department (about 100 > departments). The PDF file will be send to a printing shop which then will > mail the papers to each department. Each PDF file has 5 A3 pages with the > diagrams. > > Keeping it in one RDL file allow for me to have one subscription. > > Also, I have text boxes with values for colors for diagram bars etc (I pick > the values for the diagrams from the text boxes using an expression). When > people will start fiddling with changing colors, I can do it in one place, > instead of setting it in all 39 diagrams. > > (I want to keep the work in Report Designer as much as possible. Even if I > can edit the RDL file, I don't want that the customer need to do this then > the project is rolled out and I'm out of here... :-). ) > > TIA > Tibor Karaszi > SQL Server MVP > >
140 KB is certainly reasonable.
BTW: IIS 6.0 has a security restriction of a default 4 MB file upload/download limit. This is due to a buffering restriction implemented in IIS 6.0 (AspMaxRequestEntityAllowed setting in MetaBase.xml). Therefore, if RDL files get larger than 4 MB, you might run into an issue when uploading them on the report server. -- This posting is provided "AS IS" with no warranties, and confers no rights. "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in message news:eDPik7ymEHA.3944@TK2MSFTNGP10.phx.gbl... [quoted text, click to view] > I'm working with a report that will produce 5 printed pages with key data > for a company. Each page will contain from 3 to 12 diagrams, there will be > 39 diagrams totally in the rdl file. Plus some text boxes etc. > Each diagram has a dataset, plus some support datasets. Totally about 45 > datasets (all using stored procedures). > > I currently have 15 diagrams, and the rdl file is 140kB. > > Am I stretching it? Experiences? > > > More detailed information: > The reason for keeping it in one rdl file is that a scheduled data driven > subscription will produce one PDF file per department (about 100 > departments). The PDF file will be send to a printing shop which then will > mail the papers to each department. Each PDF file has 5 A3 pages with the > diagrams. > > Keeping it in one RDL file allow for me to have one subscription. > > Also, I have text boxes with values for colors for diagram bars etc (I pick > the values for the diagrams from the text boxes using an expression). When > people will start fiddling with changing colors, I can do it in one place, > instead of setting it in all 39 diagrams. > > (I want to keep the work in Report Designer as much as possible. Even if I > can edit the RDL file, I don't want that the customer need to do this then > the project is rolled out and I'm out of here... :-). ) > > TIA > Tibor Karaszi > SQL Server MVP > >
I'm working with a report that will produce 5 printed pages with key data
for a company. Each page will contain from 3 to 12 diagrams, there will be 39 diagrams totally in the rdl file. Plus some text boxes etc. Each diagram has a dataset, plus some support datasets. Totally about 45 datasets (all using stored procedures). I currently have 15 diagrams, and the rdl file is 140kB. Am I stretching it? Experiences? More detailed information: The reason for keeping it in one rdl file is that a scheduled data driven subscription will produce one PDF file per department (about 100 departments). The PDF file will be send to a printing shop which then will mail the papers to each department. Each PDF file has 5 A3 pages with the diagrams. Keeping it in one RDL file allow for me to have one subscription. Also, I have text boxes with values for colors for diagram bars etc (I pick the values for the diagrams from the text boxes using an expression). When people will start fiddling with changing colors, I can do it in one place, instead of setting it in all 39 diagrams. (I want to keep the work in Report Designer as much as possible. Even if I can edit the RDL file, I don't want that the customer need to do this then the project is rolled out and I'm out of here... :-). ) TIA Tibor Karaszi SQL Server MVP
OK, sounds good. Good tips. I don't use much UNDO/REDO in the first place, at least not at this
stage. :-) One thing I do is to copy a whole measurement (three diagrams plus a few text boxes) and then start work on the new sets of diagrams. This has worked fine so far, and I understand if RD becomes a bit sluggish. So far I haven't noticed any problems. I'd just hate to be on the last sets of diagram and I'm going beyond some boundary and RD or RS comes crashing on me. Even with frequent backups it will take a little while to recover from such, and if necessary I would then prefer doing it right from the beginning. Thanks Bruce! -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ [quoted text, click to view] "Bruce Johnson [MSFT]" <brucejoh@online.microsoft.com> wrote in message news:eCj97r0mEHA.596@TK2MSFTNGP11.phx.gbl... > Undo/Redo in Report Designer is somewhat memory intensive. You may find that > you need to restart Report Designer if you use this feature extensively > during a single editing session. Another aspect is that very large RDLs, > especially those that contain a large number of images, can impact the > Report Designer's editing experience. In general, Report Designer should be > able handle this report. > > -- > Bruce Johnson [MSFT] > Microsoft SQL Server Reporting Services > > This posting is provided "AS IS" with no warranties, and confers no rights. > > > "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in > message news:eDPik7ymEHA.3944@TK2MSFTNGP10.phx.gbl... >> I'm working with a report that will produce 5 printed pages with key data >> for a company. Each page will contain from 3 to 12 diagrams, there will be >> 39 diagrams totally in the rdl file. Plus some text boxes etc. >> Each diagram has a dataset, plus some support datasets. Totally about 45 >> datasets (all using stored procedures). >> >> I currently have 15 diagrams, and the rdl file is 140kB. >> >> Am I stretching it? Experiences? >> >> >> More detailed information: >> The reason for keeping it in one rdl file is that a scheduled data driven >> subscription will produce one PDF file per department (about 100 >> departments). The PDF file will be send to a printing shop which then will >> mail the papers to each department. Each PDF file has 5 A3 pages with the >> diagrams. >> >> Keeping it in one RDL file allow for me to have one subscription. >> >> Also, I have text boxes with values for colors for diagram bars etc (I > pick >> the values for the diagrams from the text boxes using an expression). When >> people will start fiddling with changing colors, I can do it in one place, >> instead of setting it in all 39 diagrams. >> >> (I want to keep the work in Report Designer as much as possible. Even if I >> can edit the RDL file, I don't want that the customer need to do this then >> the project is rolled out and I'm out of here... :-). ) >> >> TIA >> Tibor Karaszi >> SQL Server MVP >> >> > >
Assuming the size of the file is roughly proportional to what I have now, I will probably end up
with a 0.5 MB file after adding the rest of the diagrams and some fluff. Even with lots of fluff, I will most probably not go over 0.6-0.7 MB. Seems I have some margin, then. And thanks for the tip about IIS size restriction, good to know if I happen to run into this at some point. Not something I'd find easily myself. :-) -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ [quoted text, click to view] "Robert Bruckner [MSFT]" <robruc@online.microsoft.com> wrote in message news:u8LLCp1mEHA.2076@TK2MSFTNGP15.phx.gbl... > 140 KB is certainly reasonable. > BTW: IIS 6.0 has a security restriction of a default 4 MB file > upload/download limit. This is due to a buffering restriction implemented in > IIS 6.0 (AspMaxRequestEntityAllowed setting in MetaBase.xml). Therefore, if > RDL files get larger than 4 MB, you might run into an issue when uploading > them on the report server. > > -- > This posting is provided "AS IS" with no warranties, and confers no rights. > > > "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in > message news:eDPik7ymEHA.3944@TK2MSFTNGP10.phx.gbl... >> I'm working with a report that will produce 5 printed pages with key data >> for a company. Each page will contain from 3 to 12 diagrams, there will be >> 39 diagrams totally in the rdl file. Plus some text boxes etc. >> Each diagram has a dataset, plus some support datasets. Totally about 45 >> datasets (all using stored procedures). >> >> I currently have 15 diagrams, and the rdl file is 140kB. >> >> Am I stretching it? Experiences? >> >> >> More detailed information: >> The reason for keeping it in one rdl file is that a scheduled data driven >> subscription will produce one PDF file per department (about 100 >> departments). The PDF file will be send to a printing shop which then will >> mail the papers to each department. Each PDF file has 5 A3 pages with the >> diagrams. >> >> Keeping it in one RDL file allow for me to have one subscription. >> >> Also, I have text boxes with values for colors for diagram bars etc (I > pick >> the values for the diagrams from the text boxes using an expression). When >> people will start fiddling with changing colors, I can do it in one place, >> instead of setting it in all 39 diagrams. >> >> (I want to keep the work in Report Designer as much as possible. Even if I >> can edit the RDL file, I don't want that the customer need to do this then >> the project is rolled out and I'm out of here... :-). ) >> >> TIA >> Tibor Karaszi >> SQL Server MVP >> >> > >
Just as an FYI:
The rdl file ended up in size 330kB. RD was sluggish but worked. Howeverm the data-driven subscription did not work. I don't have exact error message here, but the service logged error messages about memory allocation. The service terminated. I suspect this was in the PDF rendering (which worked OK, but was slow both in VS and RM). So I splitted the report up in 5 files (one per printed page) and it work fine now. The job finished (for 37 PDF files) in about 5-7 minutes. So, I now have 5 such jobs, one for each printed file. Tibor [quoted text, click to view] "Robert Bruckner [MSFT]" <robruc@online.microsoft.com> wrote in message news:u8LLCp1mEHA.2076@TK2MSFTNGP15.phx.gbl... > 140 KB is certainly reasonable. > BTW: IIS 6.0 has a security restriction of a default 4 MB file > upload/download limit. This is due to a buffering restriction implemented in > IIS 6.0 (AspMaxRequestEntityAllowed setting in MetaBase.xml). Therefore, if > RDL files get larger than 4 MB, you might run into an issue when uploading > them on the report server. > > -- > This posting is provided "AS IS" with no warranties, and confers no rights. > > > "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in > message news:eDPik7ymEHA.3944@TK2MSFTNGP10.phx.gbl... > > I'm working with a report that will produce 5 printed pages with key data > > for a company. Each page will contain from 3 to 12 diagrams, there will be > > 39 diagrams totally in the rdl file. Plus some text boxes etc. > > Each diagram has a dataset, plus some support datasets. Totally about 45 > > datasets (all using stored procedures). > > > > I currently have 15 diagrams, and the rdl file is 140kB. > > > > Am I stretching it? Experiences? > > > > > > More detailed information: > > The reason for keeping it in one rdl file is that a scheduled data driven > > subscription will produce one PDF file per department (about 100 > > departments). The PDF file will be send to a printing shop which then will > > mail the papers to each department. Each PDF file has 5 A3 pages with the > > diagrams. > > > > Keeping it in one RDL file allow for me to have one subscription. > > > > Also, I have text boxes with values for colors for diagram bars etc (I > pick > > the values for the diagrams from the text boxes using an expression). When > > people will start fiddling with changing colors, I can do it in one place, > > instead of setting it in all 39 diagrams. > > > > (I want to keep the work in Report Designer as much as possible. Even if I > > can edit the RDL file, I don't want that the customer need to do this then > > the project is rolled out and I'm out of here... :-). ) > > > > TIA > > Tibor Karaszi > > SQL Server MVP > > > > > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |