SSRS - Bulk update datasources from dev to prod
up vote
0
down vote
favorite
We've been developing reports in a dev environment for a few months and we're ready for a data migration and to point these reports to a new location.
What I need to do is change the data source for all of these reports without having to go to each report, change the data source, and re-deploy the reports.
I'm thinking I could be able to just change the current data source from the SSRS portal to point to the new location, but I would still need to touch each report and update them in source control.
I also came across a page for the RS.exe utility here. Not sure if that is going to do what I'm looking for.
Is there a best practice for this or is touching each report the only way to accomplish what I'm looking for?
reporting-services ssrs-2016
asked Nov 7 at 15:43
jdids
84414
add a comment |
up vote
0
down vote
favorite
We've been developing reports in a dev environment for a few months and we're ready for a data migration and to point these reports to a new location.
What I need to do is change the data source for all of these reports without having to go to each report, change the data source, and re-deploy the reports.
I'm thinking I could be able to just change the current data source from the SSRS portal to point to the new location, but I would still need to touch each report and update them in source control.
I also came across a page for the RS.exe utility here. Not sure if that is going to do what I'm looking for.
Is there a best practice for this or is touching each report the only way to accomplish what I'm looking for?
reporting-services ssrs-2016
asked Nov 7 at 15:43
jdids
84414
If you update the datasource directly from the server to point to the new location, this will work fine.
– Alan Schofield
Nov 7 at 16:03
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We've been developing reports in a dev environment for a few months and we're ready for a data migration and to point these reports to a new location.
What I need to do is change the data source for all of these reports without having to go to each report, change the data source, and re-deploy the reports.
I'm thinking I could be able to just change the current data source from the SSRS portal to point to the new location, but I would still need to touch each report and update them in source control.
I also came across a page for the RS.exe utility here. Not sure if that is going to do what I'm looking for.
Is there a best practice for this or is touching each report the only way to accomplish what I'm looking for?
reporting-services ssrs-2016
asked Nov 7 at 15:43
jdids
84414
We've been developing reports in a dev environment for a few months and we're ready for a data migration and to point these reports to a new location.
What I need to do is change the data source for all of these reports without having to go to each report, change the data source, and re-deploy the reports.
I'm thinking I could be able to just change the current data source from the SSRS portal to point to the new location, but I would still need to touch each report and update them in source control.
I also came across a page for the RS.exe utility here. Not sure if that is going to do what I'm looking for.
Is there a best practice for this or is touching each report the only way to accomplish what I'm looking for?
reporting-services ssrs-2016
reporting-services ssrs-2016
asked Nov 7 at 15:43
jdids
84414
asked Nov 7 at 15:43
jdids
84414
asked Nov 7 at 15:43
jdids
84414
asked Nov 7 at 15:43
jdids
84414
asked Nov 7 at 15:43
jdids
84414
84414
If you update the datasource directly from the server to point to the new location, this will work fine.
– Alan Schofield
Nov 7 at 16:03
add a comment |
If you update the datasource directly from the server to point to the new location, this will work fine.
– Alan Schofield
Nov 7 at 16:03
If you update the datasource directly from the server to point to the new location, this will work fine.
– Alan Schofield
Nov 7 at 16:03
If you update the datasource directly from the server to point to the new location, this will work fine.
– Alan Schofield
Nov 7 at 16:03
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
In order to avoid manually configuring individual Data Sources, you will either have to use an existing 3rd party tool or create one yourself that wraps the reporting services api.
I have two suggestions that might not be useful now, since you are ready to deploy, however, they might prove useful in future report development.
Use Shared Data Sources. In your reports, configure each Data Set to point to one Shared Data Source. This would allow you to configure the connection information once per instance.
Use a dynamic connection string expression for your report Data Source configuration.
answered Nov 7 at 15:58
Ross Bush
10.6k21941
You are right, I'm too in the weeds. We already utilize the Shared Data Sources and dynamic connections for all solutions except this one :) Looks like I'm going to have to manually touch each report and deploy. Appreciate the response
– jdids
Nov 7 at 16:21
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
In order to avoid manually configuring individual Data Sources, you will either have to use an existing 3rd party tool or create one yourself that wraps the reporting services api.
I have two suggestions that might not be useful now, since you are ready to deploy, however, they might prove useful in future report development.
Use Shared Data Sources. In your reports, configure each Data Set to point to one Shared Data Source. This would allow you to configure the connection information once per instance.
Use a dynamic connection string expression for your report Data Source configuration.
answered Nov 7 at 15:58
Ross Bush
10.6k21941
You are right, I'm too in the weeds. We already utilize the Shared Data Sources and dynamic connections for all solutions except this one :) Looks like I'm going to have to manually touch each report and deploy. Appreciate the response
– jdids
Nov 7 at 16:21
add a comment |
up vote
0
down vote
accepted
In order to avoid manually configuring individual Data Sources, you will either have to use an existing 3rd party tool or create one yourself that wraps the reporting services api.
I have two suggestions that might not be useful now, since you are ready to deploy, however, they might prove useful in future report development.
Use Shared Data Sources. In your reports, configure each Data Set to point to one Shared Data Source. This would allow you to configure the connection information once per instance.
Use a dynamic connection string expression for your report Data Source configuration.
answered Nov 7 at 15:58
Ross Bush
10.6k21941
You are right, I'm too in the weeds. We already utilize the Shared Data Sources and dynamic connections for all solutions except this one :) Looks like I'm going to have to manually touch each report and deploy. Appreciate the response
– jdids
Nov 7 at 16:21
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
In order to avoid manually configuring individual Data Sources, you will either have to use an existing 3rd party tool or create one yourself that wraps the reporting services api.
I have two suggestions that might not be useful now, since you are ready to deploy, however, they might prove useful in future report development.
Use Shared Data Sources. In your reports, configure each Data Set to point to one Shared Data Source. This would allow you to configure the connection information once per instance.
Use a dynamic connection string expression for your report Data Source configuration.
answered Nov 7 at 15:58
Ross Bush
10.6k21941
In order to avoid manually configuring individual Data Sources, you will either have to use an existing 3rd party tool or create one yourself that wraps the reporting services api.
I have two suggestions that might not be useful now, since you are ready to deploy, however, they might prove useful in future report development.
Use Shared Data Sources. In your reports, configure each Data Set to point to one Shared Data Source. This would allow you to configure the connection information once per instance.
Use a dynamic connection string expression for your report Data Source configuration.
answered Nov 7 at 15:58
Ross Bush
10.6k21941
edited Nov 7 at 21:32
answered Nov 7 at 15:58
Ross Bush
10.6k21941
answered Nov 7 at 15:58
Ross Bush
10.6k21941
answered Nov 7 at 15:58
Ross Bush
10.6k21941
10.6k21941
You are right, I'm too in the weeds. We already utilize the Shared Data Sources and dynamic connections for all solutions except this one :) Looks like I'm going to have to manually touch each report and deploy. Appreciate the response
– jdids
Nov 7 at 16:21
add a comment |
You are right, I'm too in the weeds. We already utilize the Shared Data Sources and dynamic connections for all solutions except this one :) Looks like I'm going to have to manually touch each report and deploy. Appreciate the response
– jdids
Nov 7 at 16:21
You are right, I'm too in the weeds. We already utilize the Shared Data Sources and dynamic connections for all solutions except this one :) Looks like I'm going to have to manually touch each report and deploy. Appreciate the response
– jdids
Nov 7 at 16:21
You are right, I'm too in the weeds. We already utilize the Shared Data Sources and dynamic connections for all solutions except this one :) Looks like I'm going to have to manually touch each report and deploy. Appreciate the response
– jdids
Nov 7 at 16:21
add a comment |
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%2fstackoverflow.com%2fquestions%2f53192848%2fssrs-bulk-update-datasources-from-dev-to-prod%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
If you update the datasource directly from the server to point to the new location, this will work fine.
– Alan Schofield
Nov 7 at 16:03