Comments
Sort by recent activity
Sorry to hear that.
I understand this must be rather painful but I suggest to uninstall all Redgate products and reinstall them all (possibly the latest versions).
If you still have an issue afterwards, please contact support directly. / comments
Sorry to hear that.
I understand this must be rather painful but I suggest to uninstall all Redgate products and reinstall them all (possibly the latest versions).
If you still have an issue afterw...
Hi,
I am very sorry to hear that.
Could you please be more specific?
What sort of changes are you seeing?
Is this happening in the commit tab or get latest tab?
What sort of operations leaded you to see incorrect changes?
What version of SSMS and SQL Server are you using?
What version control system are you using?
If this problem is blocking you and you need a more personalised look at the problem, I invite you to get in contact with support.
Thanks,
Andrea / comments
Hi,
I am very sorry to hear that.
Could you please be more specific?
What sort of changes are you seeing?
Is this happening in the commit tab or get latest tab?
What sort of operations leaded you t...
For the first query
I believe this is a bug on our parts. We should check for the existence of the [Redgate] database before running that query.
As a workaround, you can fix the alerting problem by enabling object locking on the server or if you don't need object locking by just creating an empty Redgate database on the server you are connecting to. For the second query
You can disable "Indicate changed objects" in the Global Options. Unfortunately it is not possible to make this change only for a specific database server but can enable/disable this option as many times as you need. Remember that you need to restart SSMS in order to apply the changes.
For SQL Source Control up to version 5.7 you can find the option in the Setup Page. [image]
For SQL Source Control 5.8+ you can configure Global Options by clicking on "Options" in the top right corner (toolbar). / comments
For the first query
I believe this is a bug on our parts. We should check for the existence of the [Redgate] database before running that query.
As a workaround, you can fix the alerting problem by...
Hello,
Thank you for your suggestion!
How are you currently using SQL Source Control? What is your current workflow? Are you using the product as part of a team or individually?
I am interested to understand in more details your environment and how an auto commit feature might benefits you.
Best Regards,
Andrea / comments
Hello,
Thank you for your suggestion!
How are you currently using SQL Source Control? What is your current workflow? Are you using the product as part of a team or individually?
I am interested to ...
Hi,
Do you have other tools that runs as plugins in SSMS?
Do you have other Redgate tools like SQL Prompt installed?
What version of SSMS are you using?
What version of SQL Source Control?
Can you please try to uninstall all Redgate tools and reinstall them?
If the problem occurs again, please provide the SQL Source Control log. You can find it in %localappdata%\Red Gate\Logs\SQL Source Control
Thanks / comments
Hi,
Do you have other tools that runs as plugins in SSMS?
Do you have other Redgate tools like SQL Prompt installed?
What version of SSMS are you using?
What version of SQL Source Control?
Can you ...
I would suggest to try to un-link and re-link the database. / comments
I would suggest to try to un-link and re-link the database.
Hi Chris,
Strange. SQL Source Control does not create those objects immediately but only after the amount of time specified in the textbox in the global options (from my screenshot that is 23 seconds). I tested it with the latest version of the product.
There are two possibilities that might explain what you are seeing: tempdb has being reset after a server restart and you haven't run SQL Source Control on it afterwards or you have run SQL Source Control but checked the presence of those objects before the update script runt (you might have an higher value, it can be set up to 1 hour).
Anyway, yes giving execute rights is the best thing to do here.
We will consider adding this information to our documentation.
Thanks,
Andrea / comments
Hi Chris,
Strange. SQL Source Control does not create those objects immediately but only after the amount of time specified in the textbox in the global options (from my screenshot that is 23 secon...
Hi Chris,
Those objects are created by SQL Source Control only if you have the Global Option "Indicate changed objects in the Object Explorer and update indicators every X seconds" enabled. You can find it in the setup tab. If that option is disabled you won't find those objects in your tempdb database. [image]
The code that update the indicators and figure out "who changed what" is contained in that stored procedure so it should be the same issue as the one I linked. The permission is needed in order to access the default trace.
I believe every user who use SQL Source Control must have the permission enabled if you want to use this functionality.
Regards,
Andrea / comments
Hi Chris,
Those objects are created by SQL Source Control only if you have the Global Option "Indicate changed objects in the Object Explorer and update indicators every X seconds" enabled. You can...
Hi Chris,
Have you recently upgrade to SQL Source Control 5? What's version are you currently using?
Yes, the permission is required.
You can find more information and the solution here: https://forum.red-gate.com/discussion/80205/execute-permissions-error https://documentation.red-gate.com/display/SOC5/Object+changed+by+Unknown
Hope this help,
Andrea / comments
Hi Chris,
Have you recently upgrade to SQL Source Control 5? What's version are you currently using?
Yes, the permission is required.
You can find more information and the solution here:https://for...
I confirm that it is not possible to use the static data feature in this scenario. You can only source-control data in tables with a valid primary key. The primary key is used as the comparison key to identify corresponding rows.
More information here: https://documentation.red-gate.com/soc6/common-tasks/link-static-data
Regards / comments
I confirm that it is not possible to use the static data feature in this scenario.You can only source-control data in tables with a valid primary key. The primary key is used as the comparison key ...