Is there a way to remove the connection to a specific server when using the history?

Question

JO

Application Developer | Process Improvement | Data Analytics | Customer First Mentality

Is there a way to remove the connection to a specific server when using the history?

Asked almost 5 years ago

I sometimes run historical queries across different servers. If I copy the query to a window instead of the clipboard, it will run it against the server I originally ran the query against.

Database Management Systems (DBMS) Software

Comment

1 comment

1

Looks like you’re not logged in.

Users need to be logged in to answer questions

Log In

Jordan S. · Answer 1 · 2021-05-14T05:57:45-05:00

JS

Jordan S.

PR Manager at Devart

0

Answered about 4 years ago

Could you please explain what you mean by "to remove the connection to a specific server"? In the Execution History, you can filter the Server column so that only the required connections would be displayed. At the moment, the execution history records cannot be removed; instead, filters should be used.

delete edit

Looks like you’re not logged in.

Users need to be logged in to write comments

Log In

Reply

JO

Juan O.

Application Developer | Process Improvement | Data Analytics | Customer First Mentality

I'm usually working in three SQL Server environments. If I have SSMS open and run a query in Production, it's stored in History (no suprise). If I open SSMS tomorrow and connect to my dev server, I may want to run that same query against my open connection (dev). However if I go to history, and right-click the query and open in new window, it opens against my production server, and not the connection I'm actively on. When I was new to SQL Complete, this almost got me because I was expecting the query to run against dev.

delete edit

JO

Juan O.

Application Developer | Process Improvement | Data Analytics | Customer First Mentality

A similar feature that does the same thing is the open query feature, where when you launch SSMS it remembers the query windows you had open. This feature is great, however I wish the connection could be made against the SQL Server instance I'm opening and not the instance the query was run against. So if I worked in Prod yesterday and had 5 windows open, I wish I could launch SSMS, connect to dev and have those 5 windows that open up for me pointed to dev.

delete edit

Is there a way to remove the connection to a specific server when using the history?

About dbForge SQL Complete