SourceGear Support

Here goes. Run this SQL to get a list of all "active" users in Vault using your favorite SQL tool. use sgvault SELECT UPPER(login) FROM tblusers where active = 1 and CHARINDEX('admin', login) = 0 order by 1 Export/Save results as a CSV fle. That's the easy part. Now you want to spin thru t...

I have a solution to list users from Vault (active or not) and then taking that result into a spreadsheet and running a macro to spin thru it hitting AD to get names, etc. It's not pretty but it does the trick especially when we term employees and they still exist in Vault which uses up a license wh...

I had a similar need too. See my previous recent post, http://support.sourcegear.com/viewtopic.php?f=5&t=10863
It may help or provide some guidance in your situation.

Tom

I am using VS 2003 and VS 2008 with 3.5.3. I did some more investigation and it appears that the Projects and Solutions settings within VS 2008 were pointing to the folders for VS 2005. Once I corrected those settings to use the correct version in the IDE, things are behaving much better and as expe...

Update regarding the interaction of VS 2008 Pro SP1 and the 3.5.3 client: All was well until I tried an Add or Delete. Every other operation works fine. When adding or deleting an item, one gets this error: vs2008_err1.jpg Answering No yields this error: vs2008_err2.jpg If using the 3.5.3 client isn...

So far my initial testing of using the v3.5.3 client with VS 2008 Pro SP1 seems to be working fine. The basic operations work as expected. Will do some more thorough testing. I am interested in your workaround for having the 2 versions of the client connecting to a 3.5.3 and 4.1.x server from the sa...

Here is my scenario. Just upgraded to Vault 3.5.3 two weeks ago after months of planning and it was successful. Most of our .Net applications are on Visual Studio 2003. Now I am getting requests for Visual Studio 2008 and come to find out that the version of Vault which I just upgraded doesn't suppo...

Is it necessary to/should one stop the Vault web service prior to applying the patch to ensure all clients are disconnected? Even though it has been communicated that we are upgrading and Vault will be down, is there any harm if some clients were still connected and the patch is applied? I am concer...

Is there anything one needs to be concerned with regarding the client side cache files? Will the repository rename cause any ill-effect on the client side? Or does Vault it use GUID's internally to track repository names so the rename should not cause problems for the clients?

Thanks, Tom

Using v3.5.0, is it possible via the Admin tool to rename an existing repository? I don't see an option to do so.

Thanks, Tom

For the record, I inherited this setup :) In reality the second server is there for fail-over purposes only and is not use. Only the first server is hit for everyday production use. So in our current scenario, how can I update the 2nd server without affecting the database that was already upgraded? ...

We have 2 physical servers running the server software. So when we apply the patch to the first one, how do we answer the question regarding do you want to keep the existing database (yes) when upgrading the second server? Wouldn't the DB be patched at that point? Is the install smart enough to reco...

I have seen a number of posts regarding this. And I just want to understand why does one need to uninstall Vault and reinstall it again pointing to the new instance? Isn't Vault just a web service(s) and the location of the database is defined in the web.config? Why can't one just update that to the...

Client Information Vault Client Version: 3.5.0.4741 .Net Framework Version: 1.1.4322.2407 Operating System: Microsoft Windows XP Professional Service Pack: 2.0 OS Version: 5.1.2600 Total Physical Memory: 1.97 GB Time Zone: (GMT-06:00) Central Time (US & Canada) Server Information Vault Server Ve...

I just tried and opened our largest repository and it took about 8 minutes. Then I closed the client and reopened it and it took just seconds. So the first hit will always be "painful"? Are there some settings I can check to improve this? I will forward the article regarding DB maintenance...