SQL server 2000 is no longer supported error message

• 
  Hi @Remko1981
  
  Is this message stopping you from using SQL Prompt?
  
  Are you able to cancel it and continue?

  Victoria W February 08, 2022 11:47

  - 0 +
• 
  I can cancel the message and continue using SQL prompt. It looks like all functionality keeps working.
  

  Remko1981 February 08, 2022 13:31

  - 0 +
• 
  I am also getting this message.  I've had it pop up twice now, both times when connecting to SQL 2019 servers.  Everything works in SQL Prompt, but it's a distraction and annoyance to have to stop what I'm doing and dismiss a message that is not applicable to me at all.  Please fix.  I am using SQL Prompt 10.11.2.26629 and SSMS 18.10.
  
  

  DROP_TABLE_Students February 10, 2022 21:05

  - 0 +
• 
  Do you have any linked servers? If so, and they are SQL Server 2000, you will also get this message.

  AdrianB February 14, 2022 11:11

  - 0 +
• 
  All linked servers are SQL server 2016 or higher. Could the linked server for Active Directory ServiceInterfaces(ADSI) cause this pop-up?
  

  Remko1981 February 14, 2022 13:20

  - 0 +
• 
  I have linked servers, but none are SQL 2000.

  DROP_TABLE_Students February 14, 2022 14:17

  - 0 +
• 
  I've managed to replicate this from using the full path when selecting from a table:
  
  Example:
  
  SELECT * FROM [SERVERNAME].[DATABASE].[SCHEMA].[TABLE]
  
  The issue specifically occurs when you list the "[SERVERNAME]." portion.
  
  Can I ask if you all have queries using this? 
  
  In the meantime, I've escalated this one to be looked into.

  Kurt_M February 16, 2022 03:34

  - 0 +
• 
  @Kurt_M Yes, sometimes i query the linked servers in the way you describe.
  

  Remko1981 February 16, 2022 06:01

  - 0 +
• 
  Like @Remko1981, I also run linked server queries like that at times.  However, if I recall correctly, the last time I saw this message was when I had just connected to a server in the Object Explorer and was not running any query against it yet.
  
  In any case, I see you've published a presumed fix for this in 10.11.3.  I've installed that version and will report back if I see the message again.  Thank you.

  DROP_TABLE_Students February 16, 2022 17:46

  - 0 +
• 
  Hi @DROP_TABLE_Students @Remko1981
  
  Yes, this issue was fixed in the latest release. Please let us know if that fixes it.

  Kurt_M February 17, 2022 00:23

  - 0 +

Add comment

Please sign in to leave a comment.