Comments
Sort by recent activity
Thanks James. Obviously it's not a serious issue fix, just a nice-to-have.
Fyi the version of SSC we are using is 3.5.6.338 standard / comments
Thanks James. Obviously it's not a serious issue fix, just a nice-to-have.
Fyi the version of SSC we are using is 3.5.6.338 standard
Yes that's exactly it.
I've done a screencast also to demonstrate: http://screencast-o-matic.com/watch/c2eTIyn3Eh
Of the three horizontal bars you can resize, the top two function fine, the bottom one lags behind the cursor when you drag up.
It's no showstopper obviously but happens on all our machines. Weird!! / comments
Yes that's exactly it.
I've done a screencast also to demonstrate: http://screencast-o-matic.com/watch/c2eTIyn3Eh
Of the three horizontal bars you can resize, the top two function fine, the bottom ...
Must have been either the version I was using or other issue with my PC as after restarting Management Studio and installing the latest update I no longer have the scrollbar hidden.
If it occurs again I'll grab a screenshot etc but looks like I'm a special-needs case.
:oops: / comments
Must have been either the version I was using or other issue with my PC as after restarting Management Studio and installing the latest update I no longer have the scrollbar hidden.
If it occurs ag...
James I haven't encountered this issue again however something else I've noticed with the History dialog which is consistent with all users is a problem with resizing the bottom panel.
If you click and drag the divider between the middle and bottom sections, moving down is fine, the divider line moves with the mouse. However if you want to move it up it doesn't move with the mouse and you have to make repeated attempts to resize the panes, painfully slow on a large screen! / comments
James I haven't encountered this issue again however something else I've noticed with the History dialog which is consistent with all users is a problem with resizing the bottom panel.
If you click...
Brian Donahue wrote:
Hello,
Sometimes an index needs to be dropped in order to facilitate a change to the underlying column. For instance if the column datatype changes or something, you can't alter the table to drop the column until the index based on the column is dropped.
Hi Brian thanks for the reply,
I understand that can sometimes be the case and other objects might need to be re-created depending on the change required.
In the situation I am seeing though, I am able to write drop constraint/create constraints individually without requiring any other modifications to the tables or indexes.
So for a number of tables where I have needed to sync a large number of differences with column constraints I have had to generate the change script then go through and manually edit it to remove all the index drop/creates (and sometimes even a full table rebuild with copy to tmp table and rename) before running it on the target server.
This has been a real pain lately since applying these unnecessary steps cannot be allowed on a production box where the affected tables sometimes have millions of rows, and it's entirely possible to make the required changes without a table or index rebuild - particularly as there are no other differences between the tables other than the constraints! / comments
Brian Donahue wrote:
Hello,
Sometimes an index needs to be dropped in order to facilitate a change to the underlying column. For instance if the column datatype changes or something, you can't a...
No, user A issued this t-sql from a Management Studio window:
Create table AnyTable (id int)
Go
User B issued this t-sql from a Management Studio window:
alter table AnyTable add Col1 int
Go / comments
No, user A issued this t-sql from a Management Studio window:
Create table AnyTable (id int)
Go
User B issued this t-sql from a Management Studio window:
alter table AnyTable add Col1 int
Go
Hi James
Ok thanks, would be extremely useful to get this resolved.
This will be the main reason why we are seeing lots of changes by unknown, since it seems any edits or modifications to existing objects are in the main not being captured. / comments
Hi James
Ok thanks, would be extremely useful to get this resolved.
This will be the main reason why we are seeing lots of changes by unknown, since it seems any edits or modifications to existing ...
Woo that was quick [image]
Yes certainly some of our activity will involve items from the list of objects shown as not [currently] logged.
However we've just done another quick test:
>User A, create a table using t-sql
>Refresh the commit changes tab, new table shows up and Changed by column shows "user A"
>User B create a proc using t-sql
>Refresh the commit changes tab, new proc shows up and Changed by column shows "user B"
> User B alters the table just created by user A and adds a column
> Refresh the commit changes tab, new table now shows changed by "Unknown"
I'm assuming (hoping) this is not the expected behaviour?
Thanks! / comments
Woo that was quick
Yes certainly some of our activity will involve items from the list of objects shown as not [currently] logged.
However we've just done another quick test:
>User A, create a tab...
Yes we implemented the dedicated DB some time ago, but we still have most changes showing as unknown.
In the RG_AllObjects and RG_AllObjects_v1 tables in the dedicated DB, the username column is mostly NULL.
My RG_AllObjects table currently has 11158 rows, only 961 rows have a username. / comments
Yes we implemented the dedicated DB some time ago, but we still have most changes showing as unknown.
In the RG_AllObjects and RG_AllObjects_v1 tables in the dedicated DB, the username column is m...
Hi James
We have about 30 Databases under source control in a shared DB environment between 10 developers, although 90% of usage is across 2-3 of these only.
Since posting above I have found details about the DefaultTraceMinimumInterQueryTimeInMillis option to add to the RedGate_SQLSourceControl_Engine_EngineOptions config file. We've greatly increased this above the default which has improved the situation for most users.
Interesting your comment about it being used to display the username of who made a change in shared mode - this has never worked for us, we sometimes see the odd name pop up but 99% of changes are made by "unknown".
It's a shame as our finger of blame is feeling very underused! / comments
Hi James
We have about 30 Databases under source control in a shared DB environment between 10 developers, although 90% of usage is across 2-3 of these only.
Since posting above I have found detail...