Comments
Sort by recent activity
Hi
We have now got to the bottom of this problem and believe it is a bug in SQL Source Control related to case-sensitivity. The fix should be in the next build we release via Check For Updates - we expect this to be out next week.
Best regards,
Chris / comments
Hi
We have now got to the bottom of this problem and believe it is a bug in SQL Source Control related to case-sensitivity. The fix should be in the next build we release via Check For Updates - w...
Hi
Thanks for that. Unfortunately, that does not point to a Compatibility Level problem and we can't recreate your issue yet.
Can you please send us the entire 'database' and 'latest source control' scripts for your example below?
Also, if you have SQL Compare v10, would you be able to do a comparison between your source control repository and your database to see if the parentheses difference shows up there too?
Thanks
Chris / comments
Hi
Thanks for that. Unfortunately, that does not point to a Compatibility Level problem and we can't recreate your issue yet.
Can you please send us the entire 'database' and 'latest source contro...
Hi
We think the issue may be that SQL Source Control has not correctly picked-up the compatibility level of your datbase.
Could you please let us know a couple of pieces of information to help us confirm this?
1. What version of SQL Server is the database running on (2005, 2008, 2008 R2)?
2. What is the Combatibility Level for the db you are source controlling? To find out, go to the Database Properties dialog for the db and select the Options section.
3. What is the database version listed in the RedGateDatabaseInfo.xml file stored in your repository? This file is stored in the "Schema" folder SQL Source Control has created in your version control system.
Thanks,
Chris / comments
Hi
We think the issue may be that SQL Source Control has not correctly picked-up the compatibility level of your datbase.
Could you please let us know a couple of pieces of information to help us c...
Hi
An Early Access Release of SQL Source Control v3.1 is now available that includes a solution to the 'Changed by = Unknown' problem.
For more details, and a download link, please see: http://www.red-gate.com/MessageBoard/vi ... hp?t=15345
Thanks,
Chris / comments
Hi
An Early Access Release of SQL Source Control v3.1 is now available that includes a solution to the 'Changed by = Unknown' problem.
For more details, and a download link, please see:http://www.r...
Yep, it was an accident. Thanks for clearing that up. / comments
Yep, it was an accident. Thanks for clearing that up.
Hi Michael,
We have a feedback site where you can vote for changes you'd like to see in the product called UserVoice. There is already an entry for the ChangedBy = Unknown issue, which you can vote on.
In terms of priority - this is something that we are looking at right now. We want to make sure that our solution meets the requirements of as many users on the Shared Model as possible and have consulted a number of you regarding how best to do this. However, this feedback has indicated that we need to make a more significant change than we originally envisaged, so we don't expect to get the solution out until Q2 (2012).
I'll update this post when we have news on an Early Access or Release build that includes this work.
Best regards,
Chris / comments
Hi Michael,
We have a feedback site where you can vote for changes you'd like to see in the product called UserVoice. There is already an entry for the ChangedBy = Unknown issue, which you can vote...
Hi,
I'm afraid you cannot configure the trace SQL Source Control points to for 'Changed By' reporting. However, you can tune the frequency SQL Source Control polls the database which may help reduce how often the trace recycles - please see the thread below for details: http://www.red-gate.com/MessageBoard/vi ... hp?t=14503
We are currently working on a fix to reduce the frequency of the Unknown issue. When we have completed that fix, would you be interested in trying out a build to see it this resolves the problem?
Best regards
Chris / comments
Hi,
I'm afraid you cannot configure the trace SQL Source Control points to for 'Changed By' reporting. However, you can tune the frequency SQL Source Control polls the database which may help redu...
Hi
An Early Access Release of SQL Source Control v3.1 is now available that includes a solution to the 'Changed by = Unknown' problem.
For more details, and a download link, please see: http://www.red-gate.com/MessageBoard/vi ... hp?t=15345
Thanks,
Chris / comments
Hi
An Early Access Release of SQL Source Control v3.1 is now available that includes a solution to the 'Changed by = Unknown' problem.
For more details, and a download link, please see:http://www.r...
Hi
An Early Access Release of SQL Source Control v3.1 is now available that includes a solution to the 'Changed by = Unknown' problem.
For more details, and a download link, please see: http://www.red-gate.com/MessageBoard/vi ... hp?t=15345
Thanks,
Chris / comments
Hi
An Early Access Release of SQL Source Control v3.1 is now available that includes a solution to the 'Changed by = Unknown' problem.
For more details, and a download link, please see:http://www.r...
Hi
We use information in the the Default Trace to determine the value in the Changed By column. When you see an 'Unknown' value in that column it is because the database's Default Trace has filled up and has been rolled-over.
We are currently working on a fix to reduce the frequency of the Unknown issue. When we have completed that fix, would you be interested in trying out a build to see it this resolves the problem?
Also, we can put your name on our Early Access Build list, so that you get a chance to try any further improvements before they are released. Would you like me to add you to that list?
In the meantime, we believe that reducing the frequency of SQL Source Control's database polling (which contributes to the rolling-over of the default trace) will make the Unknown issue less common. For information on changing the frequency of polling see - http://www.red-gate.com/MessageBoard/vi ... hp?t=12837.
I hope this helps. / comments
Hi
We use information in the the Default Trace to determine the value in the Changed By column. When you see an 'Unknown' value in that column it is because the database's Default Trace has filled...