Hi,
Let me start by saying that I like what I've seen so far in SQL Prompt. I used it successfully in SQL 2000 Query Analyzer and SQL 2005 Management Studio.
I'm a Developer/DBA, so I don't use the graphical query designer in SQL 2000. However, many people here use it exclusively, so I thought that SQL Prompt could help them in the designer.
On my box, I'm running Windows Server 2003 SP1, SQL 2000 SP4, and SQL 2005 SP1. In SQL 2000 Enterprise Manager, I've got about 64 registered servers. I connect to a server, expand a database, open a table in Enterprise Manager graphical query designer, and say the table name is Orders, in the top pane where the tables are displayed, I get a table named Orders_1 with no columns. I add another table, call it OrderDetails, I get a table named OrderDetails_1 with no columns.
I then un-installed SQL Prompt and re-booted my box. If I connect to any server, any database where I tried to write a query in the graphical designer with SQL Prompt installed, I still get the same behavior as detailed above. However, if I connect to a server that I did not test with yesterday, the correct table names and column lists appear.
I physically walked to one of the servers that I tested on yesterday (from my desk), opened Enterprise Manager graphical query designer I get the same undesirable behavior described above. SQL Prompt was never installed on this server.
It seems that SQL Prompt installed some server-level metadata on every server that I connected to yesterday. Please tell me how to fix this. I never expected that if I installed SQL Prompt on my development box, it would be able to corrupt SQL on a Production Server in another office.
Thanks,
Mike
Let me start by saying that I like what I've seen so far in SQL Prompt. I used it successfully in SQL 2000 Query Analyzer and SQL 2005 Management Studio.
I'm a Developer/DBA, so I don't use the graphical query designer in SQL 2000. However, many people here use it exclusively, so I thought that SQL Prompt could help them in the designer.
On my box, I'm running Windows Server 2003 SP1, SQL 2000 SP4, and SQL 2005 SP1. In SQL 2000 Enterprise Manager, I've got about 64 registered servers. I connect to a server, expand a database, open a table in Enterprise Manager graphical query designer, and say the table name is Orders, in the top pane where the tables are displayed, I get a table named Orders_1 with no columns. I add another table, call it OrderDetails, I get a table named OrderDetails_1 with no columns.
I then un-installed SQL Prompt and re-booted my box. If I connect to any server, any database where I tried to write a query in the graphical designer with SQL Prompt installed, I still get the same behavior as detailed above. However, if I connect to a server that I did not test with yesterday, the correct table names and column lists appear.
I physically walked to one of the servers that I tested on yesterday (from my desk), opened Enterprise Manager graphical query designer I get the same undesirable behavior described above. SQL Prompt was never installed on this server.
It seems that SQL Prompt installed some server-level metadata on every server that I connected to yesterday. Please tell me how to fix this. I never expected that if I installed SQL Prompt on my development box, it would be able to corrupt SQL on a Production Server in another office.
Thanks,
Mike