Comments
Sort by recent activity
SSC 3.1.0.5208
SQL Server 10.50.4000
I have the same issue! After upgrading to 3.1.0.5208 I cannot work anymore. The following error occurs (translated):
The assembly "RedGate.SQLSourceControl.AtomicIO, Version=3.1.0.4829, Culture=neutral, PublicKeyToken=7f465a1c156d4d57" cannot be found.
Also uninstalling SSC, rebooting and installing 3.1.0.5208 did not succeed!
Please provide a link to download the version 3.1.0.4829! / comments
SSC 3.1.0.5208
SQL Server 10.50.4000
I have the same issue! After upgrading to 3.1.0.5208 I cannot work anymore. The following error occurs (translated):
The assembly "RedGate.SQLSourceControl.Atom...
Hello,
I am using SSC with Git and I had this error message when the repository was in the status of a merge conflict. In this case SSC apparently displays the code lines there the conflicts exist.
So, I advice you to check the status of your repository. / comments
Hello,
I am using SSC with Git and I had this error message when the repository was in the status of a merge conflict. In this case SSC apparently displays the code lines there the conflicts exist....
After adding the node to the configuration file it is acceptable. There are still deadlocks once in a while but I think that we can work with this configuration.
What is your default polling interval, 1000 ms?
Thank you. / comments
After adding the node to the configuration file it is acceptable. There are still deadlocks once in a while but I think that we can work with this configuration.
What is your default polling interv...
Hello,
Thank you for the answer.
Yes, it is the procedure dbo.RG_WhatsChanged processed by each user causing the deadlocks.
I am getting the deadlock information by WMI events, so I will not blow up my SQL Server error log by using the trace flag. And this is the problem of the current shared model version: Anyone who logs deadlock information will get thousands of log records (or emails like me) due to the SSC deadlocks.
So, please let me know, when you will deploy a new version of the shared model. We want to use the shared model.
Thank you. / comments
Hello,
Thank you for the answer.
Yes, it is the procedure dbo.RG_WhatsChanged processed by each user causing the deadlocks.
I am getting the deadlock information by WMI events, so I will not blow u...
SSC 3.1.0.4829
SQL Server 10.50.4000
The deadlock problems within the shared model database still occur with the new minor release 3.1.0.4829. We also get timeout messages opening the Commit Changes tab and for some objects (tables, procedures) the Changed By column shows "Unknown".
So we need a solution for the shared model as soon as possible. We are not using the trial version, we have paid for the product. / comments
SSC 3.1.0.4829
SQL Server 10.50.4000
The deadlock problems within the shared model database still occur with the new minor release 3.1.0.4829. We also get timeout messages opening the Commit Change...
Here are my answers:
- can you confirm ALL users have updated to the new build? A mixture of versions will cause problems.
Yes, all developers use build SSC 3.1.0.4829.
- is the SQL Instance you're working on local to you (i.e. on the same network) or are you running over a WAN link to a server out on the internet somewhere?
The SQL instance is on the same local network.
- how many users do you have using SQL Source Control typically?
Only two developers.
- how many objects are there in your database in total?
We have deadlocks with both a small test databases (10 objects) and big databases (hundreds of objects). / comments
Here are my answers:
- can you confirm ALL users have updated to the new build? A mixture of versions will cause problems.
Yes, all developers use build SSC 3.1.0.4829.
- is the SQL Instance you're...
SSC 3.1.0.4583
SQL Server 10.50.4000
Hello!
We are testing the shared model with the SSC changelog database implemented as described at http://www.red-gate.com/supportcenter/c ... ng_changes .
Without deep testing it seems to be necessary that each developer has to be a member of the sysadmin role. Otherwise SSC does not work and errors raise like:
System.Data.SqlClient.SqlException: The user does not have rights to perform this action. (Translated from German)
Can you confirm this statement and in case please update your guide? In this case the goal should be that developers can work with least privileged SQL Server logins.
Thanks! / comments
SSC 3.1.0.4583
SQL Server 10.50.4000
Hello!
We are testing the shared model with the SSC changelog database implemented as described at http://www.red-gate.com/supportcenter/c ... ng_changes .
With...
First, I am sorry but I wanted to refer to this topic and not the one linked in my first post. http://www.red-gate.com/messageboard/vi ... php?t=9691
In SQL Prompt 3.1 the default behaviour (in my reminiscence) was that the cursor always started at the first position in the new line – independent of the indention of the line above. With SQL Prompt 3.9 each new line starts at the position the level above is indented.
There is no difference whether I enable or disable this setting:
Inserted Candidates -> Formatting -> Insert new line at current indentation level
If I disable SQL Prompt I do not have this block formatting behaviour.
Example:
In the query below, when I press the return key after FROM the next line is automatically indented at the same level as the line above. But I want the cursor position at the first position of the next line. SELECT *
FROM
| <-- cursor position
-- I need this behaviour:
SELECT *
FROM
| <-- cursor position
/ comments
First, I am sorry but I wanted to refer to this topic and not the one linked in my first post.http://www.red-gate.com/messageboard/vi ... php?t=9691
In SQL Prompt 3.1 the default behaviour (in my r...