It doesn't, but I think we should add it to the Release & Package Deployment .. so I added BM-3149
So, it will come in a future maintenance release, since it's additive and seems to pose minor risk.
It doesn't, but I think we should add it to the Release & Package Deployment .. so I added BM-3149
So, it will come in a future maintenance release, since it's additive and seems to pose minor risk.
There isn't currently, but there will be soon! Please see PG-1221
I can't imagine any reason at all this wouldn't be done, and it can go it the next maintenance release assuming it passes code review etc!
Thanks much for the specific suggestion!
Mostly it's goign to be the PlanVersions table. Plan_Bytes is UTF8-encoded , so you can do "CAST(Plan_Bytes as VARCHAR(MAX))". The ConfigurationFileInstances table may reference it, if you use configuration file assets. IssueSources are another destination.
Note you should never directly update the database.
Hey Clint;
This was intentional in the infrastructure sync; credentials are a bit trickier, because of the encryption key and fact that some credentials aren't supported.
That said, this is definitely on our roadmap and will (likely) come in the form of a new (free) product that manages multiple instances of our tools:
In the mean time, it's possible to do with a database script / simple tool that just updates rows from one database to another (ResourceCredentials table). We can certainly help with that if needed.