How can we help you today? How can we help you today?

SQL Source Control breaks ability to see SQL Server 2000 in SSMS 2016

Hi,

When running SQL Source Control in SSMS 2016 I'm unable to expand any of my databases in object explorer on a 2000 server I have connected. If I open a second instance of SSMS (so SQL Source Control is disabled) it works. It's fair enough that SQL Source Control doesn't support SQL Server 2000, but couldn't it simply not attempt to control it instead of breaking the existing functionality?

Thanks,
Steve
Sxary
0

Comments

8 comments

Sort by
  • [Deleted User]
    Hi Sxary,

    This looks like a problem that will require investigation by one of our product support engineers. As you have a support contract I will raise a ticket for you and one of them will be in touch soon.
    [Deleted User]
    0
  • Rob C
    Hi Sxary,

    I've been able to replicate the problem and I've raised a bug report with id SOC-8800. Do you also get the error 
    'HAS_PERMS_BY_NAME' is not a recognized function name.
    when you try and expand the database node in the object explorer?

    I notice that Microsoft don't support using SSMS 2014 or later to manage a SQL 2000 database, although clearly it's doable to an extent.
    Rob C
    0
  • Sxary
    Hi, thank you for the responses and investigation. Yes I do get that error, which I can usually dismiss and continue using SSMS. I understand that newer SSMSes are not supported but as you say - it's doable, and it's still nicer to work in than the older versions. Hopefully at some point the database will be updated!
    Sxary
    0
  • Rob C
    Hi Sxary,

    Could you let me know what version of SQL 2000 you are running? I was able to reproduce the problem using the RTM version, but one of the developers tried SP4 and it seemed to work. If you're not already on SP4, it might be that installing SP4 is a workaround for this.
    Rob C
    0
  • Sxary
    Hi Rob,
    SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY('productlevel'), SERVERPROPERTY('edition')

8.00.2066	SP4	Enterprise Edition

    So SP4 plus a more recent hotfix.

    Sxary
    0
  • Rob C
    Thanks for the information! The developers have now reproduced the problem so I'll let you know as soon as I have any updates.
    Rob C
    0
  • Mike U
    I'm pleased to tell you this bug is now fixed in the latest Frequent Updates release of SQL Source Control, version 5.6.1.
    Mike U
    0
  • Sxary
    Awesome, thank you! :smile:
    Sxary
    0

Add comment

Please sign in to leave a comment.