0

We're verifying legacy system in SQL Server 2000 and confirmed we can connect it from SQL Server Management Studio 2016 (Need to add TCP port though).

Now we'd like to connect SQL Server Profiler 2016 to 2000, since we'd like to capture running query for some critical reports, but it says :

Native Client 11.0 can't connect to SQL Server before 2000

I'm just wondering we can connect profiler by OLEDB or else, instead of native client.

Is there anyone know any better idea, please let us know about your solutions.

Thank you.

Attie Wagner
  • 1,312
  • 14
  • 28
Sachiko
  • 808
  • 1
  • 12
  • 31
  • This is not a programming question in the sense of SO's policies. You should post it on dba.stackexchange.com or similar sites. – Binarus Nov 18 '19 at 08:59
  • 1
    Why not use the tools designed for 2000? You can't expect a tool created 5+ years after a product became **completely** unsupported to support it. – Thom A Nov 18 '19 at 09:01
  • Thanks for your comment @Larnu. Since we don't get any connect information and approval to that regacy server by RDP connection so far, only sql server account and password. So, I asked such a sily question. – Sachiko Nov 18 '19 at 09:25
  • 1
    Can you install the SQL 2000 version of Profiler and use that? I have no idea where you would get it though. – Nick.Mc Nov 18 '19 at 13:38
  • No, we don’t have install media (I was also surprised to hear it’s still running !) We need to verify and migrate data before termination of that legacy system. Anyway thanks for your advice @Nick.McDermaid – Sachiko Nov 18 '19 at 22:02
  • 1
    I fond this torrent.... I suspect it's not longer active though http://www.picktorrent.com/download/29/836995/microsoft_sql_server_2000_standard_edition_(personal_edition).is/ – Nick.Mc Nov 19 '19 at 04:00
  • I really appreciated your kind advice again, @Nick.McDermaid. Let me try it right after we'll make it another urgent issues. Again, thank you so much for all of your considerations. – Sachiko Nov 19 '19 at 14:21

0 Answers0