Comments
1 comment
-
Thanks for you post.
I haven't been able to reproduce this myself using SSMS 2008 R2. Does this only happen with databases that you have linked to source control, or does it happen with other databases too? As far as I know we don't change the behaviour of the object explorer at apart from adding the blobs when the object changes.
When a new object is added, SSMS normally puts it at the bottom if the list until you refresh, but an altered object should stay where it is.
What kind of modification are you performing? Would you be able to post some steps that reproduce it on you system? Can you also send me the exact version of SSMS you're using?
Add comment
Please sign in to leave a comment.
(SSC 3.0.12.3695 on a SQL Server 2008 R2 database 10.50.1600)