Red Gate forums: SQL Source Control 3

Change user for TFS

JJB7 — Fri, 17 May 2013 10:25:33 GMT

I am trying to link SQL Source Control to a TFS server where I have a different set of credentials (and therefore single signon isn't going to work).

In Visual Studio, this appears to be possible, since Visual Studio attempts single signon, then asks for credentials. I've tested SQL Source Control and it simply gives me a permission denied message:

Access Denied: [my userid] needs the following permission(s) to perform this action: View collection-level information

Is there anyway to get Source Control to not use single signon?

RE: Sending Files to source control server failed

sproatba — Thu, 16 May 2013 13:48:16 GMT

I've made some progress with this. I installed sql server 2012 and if i use ssms 2012 i can check in and evaluate policies. It seems to be an issue with the other versions of management studio. I have 2005 and 2008R2 installed as well, and those two don't know where to find the check policy.

I would like to repair my 2008R2 in particular because we have some addons that don't function in 2012 that I would like to continue using.

RE: [Error] The execute permission was denied ...

JJB7 — Thu, 16 May 2013 09:59:57 GMT

I've come across a similar issue in my team, stumbled on this post and have fixed my issue as a result, thanks for the help. We've had to source control some databases in production as we don't have development / uat versions of them....yet. This issue doesn't arise in our dev area since my guys all have sa access to that box.

What I would add for anyone who stumbles across this, is that since tempdb is recreated every time SQL restarts, you will need to apply the required permission every time SQL is restarted. Easiest way is to have the permission applied by a SQL Agent job with a schedule of "Start automatically when SQL Agent starts".

Sending Files to source control server failed

sproatba — Wed, 15 May 2013 20:35:45 GMT

Now that I finally was able to update, I can't check in code anymore because the check in policy fails unless I add the #ignorePolicies to my comments. The error indicates an error loading the changeset comments policy policy. I have the policy installed (works correctly through visual studio). I've been through the troubleshooting on the website. We do not use 2012, but I installed the power tools and went through the registry editing and all that to no avail either. What am I missing?

RE: SQL Source Control 3.1 Failed to load or caused an exception

sproatba — Wed, 15 May 2013 20:31:09 GMT

The latest version 3.4 installed correctly for me. No more crash on startup.

RE: Bug? - Foreign keys dropped

Manfred.Castro — Wed, 15 May 2013 18:08:49 GMT

Sorry you are experiencing this.
It appears you are running into a known issue under the internal reference number of SOC-4814.
Unfortunately I am unable to provide a timeline for a fix.

RE: Recommended setup for Red-Gate SQL Source Control

james.billings — Wed, 15 May 2013 16:42:06 GMT

I see you've had one reply over on SSC- I couldn't tell from your original post if you do have just a subset of the database currently source controlled right now though?

One other option we came up with is to look at filters- you could add a filter to each customer database to effectively exclude all the customer-specific objects. You can read about filters here. This means you can safely get/commit objects and know they are just the shared ones (assuming you set it up correctly)

The downside of this of course, is setting up the filters requires some initial configuration (and possibly ongoing maintenance). Also, if there are dependencies between objects you're changing and the customer-specific ones, you may find that customer specific objects still get committed. You can turn off dependencies by editing the options

Hope that helps!

RE: Changed by "Unknown" when using Changelog

eddie davis — Wed, 15 May 2013 14:32:18 GMT

Using V3.4.0.103 of SQL Source Control I am unable to reproduce the error you have reported.

I simply created a table and committed the change. My account name appears in the Changed by column.

Altered the table I just created and added a Primary Key Constraint. When through the process to commit the change and again by account name is listed in the Changed By column.

So I can try to reproduce the error, can you please send an e-mail to Support@red-gate.com with your call reference number F0072780 in the subject field of the e-mail. Please include the table script and alteration that you made, the contents of your RedGate_SQLSourceControl_Engine_EngineOptions.xml and any screen shots you can produce showing the fault symptoms.

Many Thanks
Eddie

RE: Commit Changes Tab: Lock request time out period exceeded.

jvcampbell — Wed, 15 May 2013 13:07:49 GMT

Hi

I tried the suggestion by adding the trace interval line, but when I restart SSMS the line is automatically removed.

How do I get around this?

RE: Changed by "Unknown" when using Changelog

eddie davis — Tue, 14 May 2013 15:08:26 GMT

Hi

Thank you for your forum post. I have created a support call for you, call reference is F0072780. From your post and I quote:

Quote:

For example, a straight table creation will initially correctly show the user who created the table but a subsequent addition of a default constraint will cause the username to be replaced by unknown in the commit changes window (although the username will remain in the changelog table). All further table schema changes will not alter this situation until after the object is commited to our source control system (svn).

It looks simple enough to generate a reproduction, I will update this post when I have completed my investigation or require further information from you.

If you have any further information that you think maybe useful to me, please update this forum topic.
Many Thanks
Eddie

Bug? - Foreign keys dropped

element533 — Mon, 13 May 2013 17:24:29 GMT

Sorry if this is a duplicate. I searched but couldn't find any answers.

It seems that every time I commit changes, immediately after the commit when SQL Source is refreshing, it "detects" that foreign keys need to be added. The foreign keys it wants to add were ones that were mysteriously dropped in the prior check-in. I did not drop or change these foreign keys, it just happened silently on its own, and then suddenly wanted to add them back in.

This started happening as soon as I upgraded to version 3.4. Any ideas?

Recommended setup for Red-Gate SQL Source Control

mjharper — Mon, 13 May 2013 14:58:01 GMT

I have my databases in TFS using Red-Gates SQL Source Control � but I�m not convinced I�m using it in the best way.

My setup is that we have one �nearly� core database that gets replicated for each client. This core is probably 90% of the objects. There is then the 10% that are client specific. For example there may be a View that filters on different names for different clients, there is a user that is unique for each client database (but linked to a standard role).

At the moment I have each client database linked to the same TFS project (in dedicated model). If there is a bug found I fix it in one client database and check-in. Then I get latest for all of the other client databases. I have to be careful when getting latest not to get objects that are different for each client (there is a generic version of each object in TFS which I use initially, but once I�ve configured the database for the client I don�t want to overwrite the database version with the one from TFS). I also have to be careful when committing changes as I don�t want to overwrite the generic version with the client specific version.

I�m sure this kind of setup isn�t unique � how are other people handling this? Any advice is much appreciated. (I�ve posted this question on http://ask.sqlservercentral.com as well)

RE: Vault 6.0 server support

greg_burns — Fri, 10 May 2013 17:57:41 GMT

Works now.

http://www.red-gate.com/MessageBoard/viewtopic.php?p=61856#61856

RE: Any ETA on SQL Source working w/ Vault 6.1 ?

greg_burns — Fri, 10 May 2013 17:45:24 GMT

Hey thanks!

I tried relinking and it now it does indeed work. I know I've tried this in the past, so not sure what version they finally fixed this in. But it is working with Vault 6.1 and SQL Source v3.4.0.103.

RE: Any ETA on SQL Source working w/ Vault 6.1 ?

sgilboy — Fri, 10 May 2013 16:09:06 GMT

Greg

I did get this working by unlinking SQL Source Control from the database and then relinking it...

I ran into an issue when trying to adjust some advanced properties of SQL Source (couldn't find reference to "Microsoft.VisualBasic.PowerPacks.Vs"), but i fixed that here in this thread:

http://www.red-gate.com/messageboard/viewtopic.php?t=16520

I'm fully able to use the SQL Source again