File->Open->File always opens new Connection/window

In Query Analyzer, a File->Open would replace the current query with a new query (after appropriate warning if necessary)

In Management Studio, File->Open->File always creates a new connection in a new query window. This is a pain a majority of the time as I want to replace current query with another. It seems like the File->Open->File with New Connection would be used for creating a new connection. I do see the difference between the two option, just that the first is too close to the second. It is annoying as I have to go find and then close my prior query window.

I've searched but cannot find a way around this. Any help would be most appreciated

Thanks

Carol

Download Service Pack 2:

http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/servicepacks/sp2.mspx

|||

Good thought but same behavior. I am running Microsoft SQL Server Management Studio 9.00.3042.00

But it sounds like this works differently for you than for me. Can you verify this and if so, can you think of anything you may have done to alter the default behavior?

Thanks
Carol

|||

I didn't read you question correctly. Sorry.

Before SP2 you had to connect. log in, for each file you opened. After SP2 you can open without loging in each time.

Each file opens in a new window.

|||

This doesn't feel like a very popular scenario to me. Most MDI interfaces these days open new windows instead of replacing the content of the current window. I'd suggest that if this is an important scenario to you that you report it on Microsoft Connect and have others vote on it.

Microsoft Connect:
http://connect.microsoft.com/SQLServer/Feedback/

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||

Paul,

Thanks for the response. I found an existing Microsoft Connect thread (127103) where the request stated "In SQL Server 2000 - Query Analyzer when you open a saved SQL script the script will open over the top of the current window. If the current window has an unsaved or modified script then it will prompt you to save before overwriting the contents of the window with the opened script. This has two advanatages to the user:
i) there are not multiple screens opened
ii) the script opens in the current database"

You posted a reponse on March 31, 2006 stating
"This has been addressed for SP2. Our fix should make it into CTP1 for Service Pack 2. If you could, please install the CTP1 when it is available and verify that your specific issue with Open File has been resolved. With this fix, we've also improved areas such as DDE, Drag and Drop and sqlwb.exe command line behavior."

There is a follow-up response by Microsoft on July 24, 2006 that goes into specifics. Reading this, I believe that SP2 provided improvements, but did not address the original request, which is to open a script over top of the current window. So while having it not always ask for connection info is definitely an improvement, we still would like it to not open a new window.

ID 127103 is closed but had a 4.56 rating. Would you recommend I open a new one?

Thanks
Carol

File output

I have read an Oracle article about the content management system they implemented, and was wondering whether a similar thing was possible with SQL Server.

The system basically stored the content of articles etc. in the database, as well as revisions etc., a stored procedure then generated an html page from the database content, my guess is that this then updated any necessary pages containing links etc.

My question is basically whether SQL Server (or T-SQL to be more precise) includes the ability to output the contents of fields into a file, so that when an SP was called it would generate the HTML for a page and output it to a file on the server. Thus avoiding the need to generate a page every time a request is received.

Thanks,
PaulI can think of a few ways to do this. I don't know of anything built in to SQL Server to handle this.

Do you want to call the sp from within the SQL server or from the command line?

Do you want the ability to (re)build only one file at a time or rebuild all files?

Do you have any metadata on the file names and locations?

Post back or "E" me directly.|||The idea would be that the stored procedure could be called when a record is inserted, thus when someone writes content it then creates the HTML page.

My guess is that there would also be the need to then update any linked pages, so if you wanted a link on the home page, the home page would also be re-written.

Anyway, it was nothing more than a thought, and was curious as to how SQL Server might support this kind of functionality.

Paul