Visual Studio or Report Manager for deploying SSRS Reports created using Visual Studio - Pros and Cons
I am a loser when it comes to jobs, what possibilities do I have?
Sets which are both Sum-free and Product-free.
How to deal with an underperforming colleague?
Minimum Viable Product for RTS game?
How bad is a Computer Science course that doesn't teach Design Patterns?
Why is perturbation theory used in quantum mechanics?
How to store all ctor parameters in fields
How can I prep for the Curse of Strahd adventure effectively?
Why do single electrical receptacles exist?
How can guns be countered by melee combat without raw-ability or exceptional explanations?
Is Screenshot Time-tracking Common?
typeof generic and casted type
Isn't a semicolon (';') needed after a function declaration in C++?
Why don't programs completely uninstall (remove all their files) when I remove them?
Buying a "Used" Router
What does an unprocessed RAW file look like?
What could cause an entire planet of humans to become aphasic?
How does holding onto an active but un-used credit card affect your ability to get a loan?
Is it possible to detect 100% of SQLi with a simple regex?
Can I legally make a website about boycotting a certain company?
What is formjacking?
Disk space full during insert, what happens?
What really causes series inductance of capacitors?
Coworker asking me to not bring cakes due to self control issue. What should I do?
Visual Studio or Report Manager for deploying SSRS Reports created using Visual Studio - Pros and Cons
Not sure if this is the best site for this question because I am looking for opinions rather than a technical answer. Sorry, in advance if this posting is not appropriate. Just let me know and I will remove it. I posted on another SQL Server site and have not received any opinions so I am trying this one.
We are running SQL Server 2012 EE SP3 and SSRS (2012).
I am looking for some opinions on the pros and cons of using Visual Studio (VS) or SSRS Report Manager for deploying SSRS Reports created using VS. I am a DBA and I have played with both methods however I prefer to use Report Manager and not a developer-centric tool. We are a small shop (2 developers).
With VS, I right click the Report Project, select Properties, fill out the Report Property Page by setting Overwrite Options, Target Folders and URL, TargetServerVersion, and click OK. Then right click the Report Project and click Deploy.
In playing around with deploying using VS, I was able to upload a higher version SSRS report (created with VS 2016) to the SSRS 2012 Report Server and the report worked (executed successfully); I do not want this type of thing to be allowed. This tells me that the VS deployment is doing something(s) behind the scenes to make things work. However, the same higher version SSRS report did NOT work when it was deployed with Report Manager (SSRS 2012). It failed with "The definition of this report is not valid or supported by this version of Reporting Services." In addition, I was able to upload an SSRS Report (created with VS 2012) which contained 'unused datasets'. I do not want this type of thing to be allowed. After further research, I found out that 'unused datasets' are not a 'good practice' because they are executed each time the SSRS Report is executed. Google "SQL Server Reporting Services Best Practices for Performance and Maintenance" by Ghanesh Prasad.
I prefer Report Manager because it is a one-stop shop in that it allows me to manage the entire report server reporting activities. I can manage folders/reports, set the security of folders and items, deploy and publish reports, create subscriptions, etc. With Report Manager, I use the following steps for a report that uses shared datasets. (There are less steps if the report has embedded datasets.) Of, course I create the data source.
- Upload each dataset (.rsd file).
- Link each dataset to the data source (creates shared datasets)
- Upload each report definition file (.rdl file)
- Link each report dataset to the shared dataset in SSRS
I also believe that using Report Manager, provides me (DBA) more control over what is being uploaded to our SSRS. It helps me keep the SSRS cleaned of clutter, reports created with higher versions of VS, and 'unused datasets' (I request the developers to list or identify the 'used datasets' in the report.) This is important since our SSRS runs on our database server.
Again, just looking for some opinions on the pros and cons of using Visual Studio (VS) or SSRS Report Manager for deploying SSRS Reports created using VS.
Thanks in advance.
ssrs visual-studio deployment
asked 1 min ago
HookSQLDBA7HookSQLDBA7
1
New contributor
HookSQLDBA7 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Not sure if this is the best site for this question because I am looking for opinions rather than a technical answer. Sorry, in advance if this posting is not appropriate. Just let me know and I will remove it. I posted on another SQL Server site and have not received any opinions so I am trying this one.
We are running SQL Server 2012 EE SP3 and SSRS (2012).
I am looking for some opinions on the pros and cons of using Visual Studio (VS) or SSRS Report Manager for deploying SSRS Reports created using VS. I am a DBA and I have played with both methods however I prefer to use Report Manager and not a developer-centric tool. We are a small shop (2 developers).
With VS, I right click the Report Project, select Properties, fill out the Report Property Page by setting Overwrite Options, Target Folders and URL, TargetServerVersion, and click OK. Then right click the Report Project and click Deploy.
In playing around with deploying using VS, I was able to upload a higher version SSRS report (created with VS 2016) to the SSRS 2012 Report Server and the report worked (executed successfully); I do not want this type of thing to be allowed. This tells me that the VS deployment is doing something(s) behind the scenes to make things work. However, the same higher version SSRS report did NOT work when it was deployed with Report Manager (SSRS 2012). It failed with "The definition of this report is not valid or supported by this version of Reporting Services." In addition, I was able to upload an SSRS Report (created with VS 2012) which contained 'unused datasets'. I do not want this type of thing to be allowed. After further research, I found out that 'unused datasets' are not a 'good practice' because they are executed each time the SSRS Report is executed. Google "SQL Server Reporting Services Best Practices for Performance and Maintenance" by Ghanesh Prasad.
I prefer Report Manager because it is a one-stop shop in that it allows me to manage the entire report server reporting activities. I can manage folders/reports, set the security of folders and items, deploy and publish reports, create subscriptions, etc. With Report Manager, I use the following steps for a report that uses shared datasets. (There are less steps if the report has embedded datasets.) Of, course I create the data source.
- Upload each dataset (.rsd file).
- Link each dataset to the data source (creates shared datasets)
- Upload each report definition file (.rdl file)
- Link each report dataset to the shared dataset in SSRS
I also believe that using Report Manager, provides me (DBA) more control over what is being uploaded to our SSRS. It helps me keep the SSRS cleaned of clutter, reports created with higher versions of VS, and 'unused datasets' (I request the developers to list or identify the 'used datasets' in the report.) This is important since our SSRS runs on our database server.
Again, just looking for some opinions on the pros and cons of using Visual Studio (VS) or SSRS Report Manager for deploying SSRS Reports created using VS.
Thanks in advance.
ssrs visual-studio deployment
asked 1 min ago
HookSQLDBA7HookSQLDBA7
1
New contributor
HookSQLDBA7 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Not sure if this is the best site for this question because I am looking for opinions rather than a technical answer. Sorry, in advance if this posting is not appropriate. Just let me know and I will remove it. I posted on another SQL Server site and have not received any opinions so I am trying this one.
We are running SQL Server 2012 EE SP3 and SSRS (2012).
I am looking for some opinions on the pros and cons of using Visual Studio (VS) or SSRS Report Manager for deploying SSRS Reports created using VS. I am a DBA and I have played with both methods however I prefer to use Report Manager and not a developer-centric tool. We are a small shop (2 developers).
With VS, I right click the Report Project, select Properties, fill out the Report Property Page by setting Overwrite Options, Target Folders and URL, TargetServerVersion, and click OK. Then right click the Report Project and click Deploy.
In playing around with deploying using VS, I was able to upload a higher version SSRS report (created with VS 2016) to the SSRS 2012 Report Server and the report worked (executed successfully); I do not want this type of thing to be allowed. This tells me that the VS deployment is doing something(s) behind the scenes to make things work. However, the same higher version SSRS report did NOT work when it was deployed with Report Manager (SSRS 2012). It failed with "The definition of this report is not valid or supported by this version of Reporting Services." In addition, I was able to upload an SSRS Report (created with VS 2012) which contained 'unused datasets'. I do not want this type of thing to be allowed. After further research, I found out that 'unused datasets' are not a 'good practice' because they are executed each time the SSRS Report is executed. Google "SQL Server Reporting Services Best Practices for Performance and Maintenance" by Ghanesh Prasad.
I prefer Report Manager because it is a one-stop shop in that it allows me to manage the entire report server reporting activities. I can manage folders/reports, set the security of folders and items, deploy and publish reports, create subscriptions, etc. With Report Manager, I use the following steps for a report that uses shared datasets. (There are less steps if the report has embedded datasets.) Of, course I create the data source.
- Upload each dataset (.rsd file).
- Link each dataset to the data source (creates shared datasets)
- Upload each report definition file (.rdl file)
- Link each report dataset to the shared dataset in SSRS
I also believe that using Report Manager, provides me (DBA) more control over what is being uploaded to our SSRS. It helps me keep the SSRS cleaned of clutter, reports created with higher versions of VS, and 'unused datasets' (I request the developers to list or identify the 'used datasets' in the report.) This is important since our SSRS runs on our database server.
Again, just looking for some opinions on the pros and cons of using Visual Studio (VS) or SSRS Report Manager for deploying SSRS Reports created using VS.
Thanks in advance.
ssrs visual-studio deployment
asked 1 min ago
HookSQLDBA7HookSQLDBA7
1
New contributor
HookSQLDBA7 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Not sure if this is the best site for this question because I am looking for opinions rather than a technical answer. Sorry, in advance if this posting is not appropriate. Just let me know and I will remove it. I posted on another SQL Server site and have not received any opinions so I am trying this one.
We are running SQL Server 2012 EE SP3 and SSRS (2012).
I am looking for some opinions on the pros and cons of using Visual Studio (VS) or SSRS Report Manager for deploying SSRS Reports created using VS. I am a DBA and I have played with both methods however I prefer to use Report Manager and not a developer-centric tool. We are a small shop (2 developers).
With VS, I right click the Report Project, select Properties, fill out the Report Property Page by setting Overwrite Options, Target Folders and URL, TargetServerVersion, and click OK. Then right click the Report Project and click Deploy.
In playing around with deploying using VS, I was able to upload a higher version SSRS report (created with VS 2016) to the SSRS 2012 Report Server and the report worked (executed successfully); I do not want this type of thing to be allowed. This tells me that the VS deployment is doing something(s) behind the scenes to make things work. However, the same higher version SSRS report did NOT work when it was deployed with Report Manager (SSRS 2012). It failed with "The definition of this report is not valid or supported by this version of Reporting Services." In addition, I was able to upload an SSRS Report (created with VS 2012) which contained 'unused datasets'. I do not want this type of thing to be allowed. After further research, I found out that 'unused datasets' are not a 'good practice' because they are executed each time the SSRS Report is executed. Google "SQL Server Reporting Services Best Practices for Performance and Maintenance" by Ghanesh Prasad.
I prefer Report Manager because it is a one-stop shop in that it allows me to manage the entire report server reporting activities. I can manage folders/reports, set the security of folders and items, deploy and publish reports, create subscriptions, etc. With Report Manager, I use the following steps for a report that uses shared datasets. (There are less steps if the report has embedded datasets.) Of, course I create the data source.
- Upload each dataset (.rsd file).
- Link each dataset to the data source (creates shared datasets)
- Upload each report definition file (.rdl file)
- Link each report dataset to the shared dataset in SSRS
I also believe that using Report Manager, provides me (DBA) more control over what is being uploaded to our SSRS. It helps me keep the SSRS cleaned of clutter, reports created with higher versions of VS, and 'unused datasets' (I request the developers to list or identify the 'used datasets' in the report.) This is important since our SSRS runs on our database server.
Again, just looking for some opinions on the pros and cons of using Visual Studio (VS) or SSRS Report Manager for deploying SSRS Reports created using VS.
Thanks in advance.
ssrs visual-studio deployment
ssrs visual-studio deployment
asked 1 min ago
HookSQLDBA7HookSQLDBA7
1
New contributor
HookSQLDBA7 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 1 min ago
HookSQLDBA7HookSQLDBA7
1
New contributor
HookSQLDBA7 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 1 min ago
HookSQLDBA7HookSQLDBA7
1
New contributor
HookSQLDBA7 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 1 min ago
HookSQLDBA7HookSQLDBA7
1
asked 1 min ago
HookSQLDBA7HookSQLDBA7
1
1
New contributor
HookSQLDBA7 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
HookSQLDBA7 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
HookSQLDBA7 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
HookSQLDBA7 is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f230507%2fvisual-studio-or-report-manager-for-deploying-ssrs-reports-created-using-visual%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
HookSQLDBA7 is a new contributor. Be nice, and check out our Code of Conduct.
HookSQLDBA7 is a new contributor. Be nice, and check out our Code of Conduct.
HookSQLDBA7 is a new contributor. Be nice, and check out our Code of Conduct.
HookSQLDBA7 is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f230507%2fvisual-studio-or-report-manager-for-deploying-ssrs-reports-created-using-visual%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
