David Burrows wrote:
Jeff Moden wrote:
I know it doesn't contribute to the conversation at hand but it's just fascinating to me that this type of thing is still an issue since the release in 2005 and that one still has to resort to things like PowerShell to do this. To be sure, I'm using the word "fascinating" as a "suitable for work" replacement for all the expletives that I believe would be more appropriate behind closed doors. 😀
Couldn't agree more Jeff 🙂
In the past I did use some MS software to migrate from 2005 to 2008 but it was PITA and POS 🙁
Not that this excuses having the ability to export/import fully - but I think the reason is the assumption that everyone is using some type of code repository (git - for example) where everything is saved off ready for redeployment if needed.
The reality is that there are a lot of organizations where report writing and ETL processes are not part of a development team and they do not have access to these repositories (or the training to use them appropriately). Or - the organization is small and setting up a repository isn't seen as necessary.
So we see a lot of situations where the person who developed the report is the only one that has that project - and it is stored locally on the workstation. Or - that employee has left the organization and no one has access to that users local files.