SQL Source Control breaks ability to see SQL Server 2000 in SSMS 2016
Sxary
Posts: 4
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
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
Tagged:
Comments
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.
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 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.
Redgate Software
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.
Redgate Software
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY('productlevel'), SERVERPROPERTY('edition') 8.00.2066 SP4 Enterprise EditionSo SP4 plus a more recent hotfix.
Redgate Software
Redgate Software