Steve, I no longer have a Visual Studio project for reports (used to do it that way in early days), I guess you'd say the report server is our master repository now. When a change has been made we download the rdl from the server and check it into source control via local rep as you describe. When doing so, also we look for modified reports and do the same. Everyone has different operating conditions, our in company the IS team can, and do update reports using Report Builder but they do not operate Visual Studio or have licences for TFS (too expensive), thus why we are working this way. So for us, with the infrequent changes we make to reports these days (been using GP long time and reporting is mostly bedded in, excel power query and BI used for ad-hoc and operational reporting needs), this is appropriate balance of risk vs control vs effort. We've been considering using Git or other "free" source control solutions for reporting so that everyone can run it, or can automate a sweep of the report server nightly to auto check-in the current state using automation, but it is not a big issue compared to others we have on the backlog, so is down the list somewhat. Tim
↧