I just compacted a central repository and in the process lost a large number of the permissions that had been set on objects, majority now only have a permission of READ, regardless of the central repo group, which isn’t overly helpful…
Are the permissions on objects in the Central Repo only linked to the original/first added object?
Ouch, sorry to hear that. There isn’t much information out there regarding compacting of central repos. I would have thought that new object versions would inherit the authorisations from the previous version, but it sounds like that is not the case. All I can say is that I have read somewhere that compacting a central repo is not recommended, but the main reason for that recommendation was that obviously you lose your object version history, which is extremely useful to have. The other recommendation I have read is to always back up a repo before compacting (as far as I know you can log into it just like a local repo and then export the repo to file - just make sure no-one else is using it, or back it up at the database level) - I hope you have a recent database backup you can fall back on.
I was looking at re-base lining activity as part of a migration to a new host, so had a copy of the schema, so was able to recover to the pre-compact point.
After watching Werner’s DS4.0 install video, I’m looking forward to what will come of support for (integration with) SubVersion (and hopefully Bamboo too).
This is not the case. As far as I remember, from version 11.0 we cannot login to Central Repository. Before to that we can actually do that.
This is a real question about the Rights for the groups. I would say that what it does is centainly not expected.
By the way, what version of DI/DS are you referring to? I would go ahead and see what happens on this? And yes, compact Local but I too recommend don’t compact central.
But as ClintL says, make it as a rule that you take .atl backup of whatever changes you do on objects level.
But on the level of repository, then may be you should submit a DBA request to schedule a DB level backup of your repository database
My apologies. You are correct Ganesh, just tried it and it’s no longer possible to login to central repo from the Designer, whether secure or not. It was a long time ago that I last did that so must have been before ver 11, probably when it was still called Acta
Thanks I found it yesterday and watched it already. Looks dead easy, especially when it’s a new installation as opposed to an upgrade - which mine basically is because the client wants to keep the old version in place for a while as a fall back option while we test all the jobs on the new version on a new server with a separate SQL instance. So hopefully my installation goes as smoothly as Werner’s
Mine was absolutely smooth - after the third try. You need to be careful at the prerequisites and don’t select a custom installation, use the standard one. The standard lets you configure every important option anyhow.