General Basic SSRS 2008 questions
To the SSRS experts out there, I have some basic questions that have eluded me when searching for answers, so if you would.....
1. Is it really necessary to reload data each time a design change is made? For instance, often only the output format is changing (e.g. number with 2 decimals to number with 0 decimals). This is a waste of time, plus I have to re-input parameter data every time.
2. How do general defaults get set (e.g. number with 2 decimals; ‘-‘ for negative values; etc.)? I'd like to set my own defaults rather than the native ones for the various objects.
3. When editing reports, changes get saved when I am not ready which overwrites the existing version. Is there a way to turn this off? The system has overwritten a well running report with test changes I'm making that haven't been fully vetted.
4. Along the lines of Q3 above: What is the recommended way to save incremental revisions of reports? In Crystal, I would save new copies with a .01,.02, etc. rev # at the end.
5. Why is it that the Details group can be deleted and then not restored? I inadvertently did this and had to recreate the whole detail row.
1. Is it really necessary to reload data each time a design change is made? For instance, often only the output format is changing (e.g. number with 2 decimals to number with 0 decimals). This is a waste of time, plus I have to re-input parameter data every time.
2. How do general defaults get set (e.g. number with 2 decimals; ‘-‘ for negative values; etc.)? I'd like to set my own defaults rather than the native ones for the various objects.
3. When editing reports, changes get saved when I am not ready which overwrites the existing version. Is there a way to turn this off? The system has overwritten a well running report with test changes I'm making that haven't been fully vetted.
4. Along the lines of Q3 above: What is the recommended way to save incremental revisions of reports? In Crystal, I would save new copies with a .01,.02, etc. rev # at the end.
5. Why is it that the Details group can be deleted and then not restored? I inadvertently did this and had to recreate the whole detail row.
Hi Makingitbig,
I can answer a few of these questions, but not all. I'm wondering though if you're using the report builder, or visual studio, to create your reports.
1. No, usually if the change is minor like layout changes it would not rerun the query as far as I know. A good practice is to set default values for your parameters while you're developing, which should make the reports load quicker and allows you to refresh the data without having to enter the parameters every time. You can set default values in the report parameters program. Just remember to take them out before you deploy your report if you don't want to keep the defaults in the final version.
2. Default number formats can be set in the textbox properties (select the field, then right click, select properties). On the Format tab you see a Format code field. Here you can enter your custom formatting. It's similar to the custom formatting used in Excel, but I'm not too familiar with the syntax myself. Google can help you here.
3. Normally nothing gets saved unless you tell it to. What program are you using to build your reports? Do you have a dedicated report server to which the reports are deployed?
4. Same as what you mentioned, I would save it under different file names. If you work with a report server, depending on whether or not you want to overwrite an existing report or keep both versions side by side you might have to update the report file name before deploying it to the server to make sure the correct report is replaced.
5. As with removing any detail or group line, if you add it back in it will add an empty line. What is on that line is not cast in stone so you'll have to add it back in. I'd assume the undo function could be used to recover an accidentally deleted line though. In any case I would never delete the details line, just hide it if you don't want to display it.
Hope this helps.
I can answer a few of these questions, but not all. I'm wondering though if you're using the report builder, or visual studio, to create your reports.
1. No, usually if the change is minor like layout changes it would not rerun the query as far as I know. A good practice is to set default values for your parameters while you're developing, which should make the reports load quicker and allows you to refresh the data without having to enter the parameters every time. You can set default values in the report parameters program. Just remember to take them out before you deploy your report if you don't want to keep the defaults in the final version.
2. Default number formats can be set in the textbox properties (select the field, then right click, select properties). On the Format tab you see a Format code field. Here you can enter your custom formatting. It's similar to the custom formatting used in Excel, but I'm not too familiar with the syntax myself. Google can help you here.
3. Normally nothing gets saved unless you tell it to. What program are you using to build your reports? Do you have a dedicated report server to which the reports are deployed?
4. Same as what you mentioned, I would save it under different file names. If you work with a report server, depending on whether or not you want to overwrite an existing report or keep both versions side by side you might have to update the report file name before deploying it to the server to make sure the correct report is replaced.
5. As with removing any detail or group line, if you add it back in it will add an empty line. What is on that line is not cast in stone so you'll have to add it back in. I'd assume the undo function could be used to recover an accidentally deleted line though. In any case I would never delete the details line, just hide it if you don't want to display it.
Hope this helps.
Hi Makingitbig,
I can answer a few of these questions, but not all. I'm wondering though if you're using the report builder, or visual studio, to create your reports.
1. No, usually if the change is minor like layout changes it would not rerun the query as far as I know. A good practice is to set default values for your parameters while you're developing, which should make the reports load quicker and allows you to refresh the data without having to enter the parameters every time. You can set default values in the report parameters program. Just remember to take them out before you deploy your report if you don't want to keep the defaults in the final version.
2. Default number formats can be set in the textbox properties (select the field, then right click, select properties). On the Format tab you see a Format code field. Here you can enter your custom formatting. It's similar to the custom formatting used in Excel, but I'm not too familiar with the syntax myself. Google can help you here.
3. Normally nothing gets saved unless you tell it to. What program are you using to build your reports? Do you have a dedicated report server to which the reports are deployed?
4. Same as what you mentioned, I would save it under different file names. If you work with a report server, depending on whether or not you want to overwrite an existing report or keep both versions side by side you might have to update the report file name before deploying it to the server to make sure the correct report is replaced.
5. As with removing any detail or group line, if you add it back in it will add an empty line. What is on that line is not cast in stone so you'll have to add it back in. I'd assume the undo function could be used to recover an accidentally deleted line though. In any case I would never delete the details line, just hide it if you don't want to display it.
Hope this helps.
I can answer a few of these questions, but not all. I'm wondering though if you're using the report builder, or visual studio, to create your reports.
1. No, usually if the change is minor like layout changes it would not rerun the query as far as I know. A good practice is to set default values for your parameters while you're developing, which should make the reports load quicker and allows you to refresh the data without having to enter the parameters every time. You can set default values in the report parameters program. Just remember to take them out before you deploy your report if you don't want to keep the defaults in the final version.
2. Default number formats can be set in the textbox properties (select the field, then right click, select properties). On the Format tab you see a Format code field. Here you can enter your custom formatting. It's similar to the custom formatting used in Excel, but I'm not too familiar with the syntax myself. Google can help you here.
3. Normally nothing gets saved unless you tell it to. What program are you using to build your reports? Do you have a dedicated report server to which the reports are deployed?
4. Same as what you mentioned, I would save it under different file names. If you work with a report server, depending on whether or not you want to overwrite an existing report or keep both versions side by side you might have to update the report file name before deploying it to the server to make sure the correct report is replaced.
5. As with removing any detail or group line, if you add it back in it will add an empty line. What is on that line is not cast in stone so you'll have to add it back in. I'd assume the undo function could be used to recover an accidentally deleted line though. In any case I would never delete the details line, just hide it if you don't want to display it.
Hope this helps.
ASKER
First of all, thank you for taking the time to give this some thought and write back.
To clarify, I'm in the BIDS 2008 R2 environment and I'm coming from a Crystal Reports one so I've got quite a bit of re-learning to do.
1. I know that I can put in default parameters, but that still doesn't solve the 'Loading' each time switching to the Design tab then back to the Preview tab. Each time it appears to reload data rather than just keeping the most recent load (as it does in CR).
2. I can change the text box properties of each text box individually with no issues (and also create custom), but that isn't what I'm asking. Rather, I'd like to set the defaults for each type of data - for example, rather than a numeric field having 4 decimal places by default system wide, change it to 2 decimal places. Alternatively, I could highlight several fields at once to change the format, but SSRS doesn't seem to do this. (this can be done in CR).
3. The report 'source code' (the .rdl) is getting updated without my command. Deployment is not an issue as it only occurs when I specify.
4. Deployment isn't the issue; saving as another file name replaces the initial copy in the solution, which isn't a big deal as it can be added back, if needed. But, when Saving As, SSRS doesn't automatically save the file as .rdl, which, again, isn't a serious issue, but seems odd that it wouldn't be assumed.
5. As I mentioned, I deleted it accidentally - just seems like there could be an easy mechanism to restore it.
More comments are welcome from you and others.
To clarify, I'm in the BIDS 2008 R2 environment and I'm coming from a Crystal Reports one so I've got quite a bit of re-learning to do.
1. I know that I can put in default parameters, but that still doesn't solve the 'Loading' each time switching to the Design tab then back to the Preview tab. Each time it appears to reload data rather than just keeping the most recent load (as it does in CR).
2. I can change the text box properties of each text box individually with no issues (and also create custom), but that isn't what I'm asking. Rather, I'd like to set the defaults for each type of data - for example, rather than a numeric field having 4 decimal places by default system wide, change it to 2 decimal places. Alternatively, I could highlight several fields at once to change the format, but SSRS doesn't seem to do this. (this can be done in CR).
3. The report 'source code' (the .rdl) is getting updated without my command. Deployment is not an issue as it only occurs when I specify.
4. Deployment isn't the issue; saving as another file name replaces the initial copy in the solution, which isn't a big deal as it can be added back, if needed. But, when Saving As, SSRS doesn't automatically save the file as .rdl, which, again, isn't a serious issue, but seems odd that it wouldn't be assumed.
5. As I mentioned, I deleted it accidentally - just seems like there could be an easy mechanism to restore it.
More comments are welcome from you and others.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
My pleasure.
1. I think it depends on the change. I've noticed that if the only thing I change in a report is for instance the numeric format, the data won't load again. But if a part of the report is changed which could result in different numbers it does seem to reload the data. I'm not entirely sure either about this mechanism, but I don't think you have influence on its behaviour.
2. Again, I don't think this can be done. It seems to me that RS uses the datatype from the database as a default. Changes to this default have to happen inside the formulas or through the field properties.
3. I've done some digging in the options of Visual Studio. Have a look at Tools - Options, then select Projects and Solutions - Build and Run. There is an option here labeled "Before building" which is default set to "save all changes". I'm not sure if it rebuilds the report every time you preview, but this could explain why your rdl is being overwritten. Try to change this to "Prompt to save all changes" and see if it makes a difference.
No further thoughts on point 4 and 5 I'm afraid. Perhaps someone else knows?
PS. Sorry for the triple posts. Still trying to figure out how this happens, but it's done automatically for some reason.
1. I think it depends on the change. I've noticed that if the only thing I change in a report is for instance the numeric format, the data won't load again. But if a part of the report is changed which could result in different numbers it does seem to reload the data. I'm not entirely sure either about this mechanism, but I don't think you have influence on its behaviour.
2. Again, I don't think this can be done. It seems to me that RS uses the datatype from the database as a default. Changes to this default have to happen inside the formulas or through the field properties.
3. I've done some digging in the options of Visual Studio. Have a look at Tools - Options, then select Projects and Solutions - Build and Run. There is an option here labeled "Before building" which is default set to "save all changes". I'm not sure if it rebuilds the report every time you preview, but this could explain why your rdl is being overwritten. Try to change this to "Prompt to save all changes" and see if it makes a difference.
No further thoughts on point 4 and 5 I'm afraid. Perhaps someone else knows?
PS. Sorry for the triple posts. Still trying to figure out how this happens, but it's done automatically for some reason.
My pleasure.
1. I think it depends on the change. I've noticed that if the only thing I change in a report is for instance the numeric format, the data won't load again. But if a part of the report is changed which could result in different numbers it does seem to reload the data. I'm not entirely sure either about this mechanism, but I don't think you have influence on its behaviour.
2. Again, I don't think this can be done. It seems to me that RS uses the datatype from the database as a default. Changes to this default have to happen inside the formulas or through the field properties.
3. I've done some digging in the options of Visual Studio. Have a look at Tools - Options, then select Projects and Solutions - Build and Run. There is an option here labeled "Before building" which is default set to "save all changes". I'm not sure if it rebuilds the report every time you preview, but this could explain why your rdl is being overwritten. Try to change this to "Prompt to save all changes" and see if it makes a difference.
No further thoughts on point 4 and 5 I'm afraid. Perhaps someone else knows?
PS. Sorry for the triple posts. Still trying to figure out how this happens, but it's done automatically for some reason.
1. I think it depends on the change. I've noticed that if the only thing I change in a report is for instance the numeric format, the data won't load again. But if a part of the report is changed which could result in different numbers it does seem to reload the data. I'm not entirely sure either about this mechanism, but I don't think you have influence on its behaviour.
2. Again, I don't think this can be done. It seems to me that RS uses the datatype from the database as a default. Changes to this default have to happen inside the formulas or through the field properties.
3. I've done some digging in the options of Visual Studio. Have a look at Tools - Options, then select Projects and Solutions - Build and Run. There is an option here labeled "Before building" which is default set to "save all changes". I'm not sure if it rebuilds the report every time you preview, but this could explain why your rdl is being overwritten. Try to change this to "Prompt to save all changes" and see if it makes a difference.
No further thoughts on point 4 and 5 I'm afraid. Perhaps someone else knows?
PS. Sorry for the triple posts. Still trying to figure out how this happens, but it's done automatically for some reason.
ASKER
I was wondering about the triple posts!
Anyone else who cares to comment on my questions, please do so.
Anyone else who cares to comment on my questions, please do so.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
I thought about separating the questions, but figured these were basic operational questions rather than a single, more complex issue. I'm still in learning mode (I guess we always are!) and sometimes the simplest things are not obvious to figure out.
Any additional pointers to good basic links, books, etc. would also be nice. I really appreciate the help. Thanks.
Any additional pointers to good basic links, books, etc. would also be nice. I really appreciate the help. Thanks.
Books:
Microsoft SQL Server 2012 Reporting Services 4/E by Brian Larson
Professional Microsoft SQL Server 2012 Reporting Services by Paul Turley, Robert M. Bruckner, Thiago Silva and Ken Withee (Jun 5, 2012)
BTW: why the B-grade? As far as I can tell we've done our best to answer your Qs?
Microsoft SQL Server 2012 Reporting Services 4/E by Brian Larson
Professional Microsoft SQL Server 2012 Reporting Services by Paul Turley, Robert M. Bruckner, Thiago Silva and Ken Withee (Jun 5, 2012)
BTW: why the B-grade? As far as I can tell we've done our best to answer your Qs?
I can answer a few of these questions, but not all. I'm wondering though if you're using the report builder, or visual studio, to create your reports.
1. No, usually if the change is minor like layout changes it would not rerun the query as far as I know. A good practice is to set default values for your parameters while you're developing, which should make the reports load quicker and allows you to refresh the data without having to enter the parameters every time. You can set default values in the report parameters program. Just remember to take them out before you deploy your report if you don't want to keep the defaults in the final version.
2. Default number formats can be set in the textbox properties (select the field, then right click, select properties). On the Format tab you see a Format code field. Here you can enter your custom formatting. It's similar to the custom formatting used in Excel, but I'm not too familiar with the syntax myself. Google can help you here.
3. Normally nothing gets saved unless you tell it to. What program are you using to build your reports? Do you have a dedicated report server to which the reports are deployed?
4. Same as what you mentioned, I would save it under different file names. If you work with a report server, depending on whether or not you want to overwrite an existing report or keep both versions side by side you might have to update the report file name before deploying it to the server to make sure the correct report is replaced.
5. As with removing any detail or group line, if you add it back in it will add an empty line. What is on that line is not cast in stone so you'll have to add it back in. I'd assume the undo function could be used to recover an accidentally deleted line though. In any case I would never delete the details line, just hide it if you don't want to display it.
Hope this helps.