Everytime when I open .SQL file using SQL 2005 management Studio, it ask me
about connection info. Is there any way to use the previous one like SQL
2000? For example, first time when I open .SQL file, I put connection info,
and if I open another .SQL file, it will default to the previous connection
info without pop up the "Connect to Server" screen.
Thanks
Yong
This behavior has been changed in SQL Server 2005 Service Pack 2. You can
checkout the December CTP: http://www.microsoft.com/sql/ctp.mspx
FAQ on SP2:
http://blogs.msdn.com/sqlrem/archive/2007/01/12/SP2-and-BPA-FAQ.aspx
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
"Yong" <Yong@.discussions.microsoft.com> wrote in message
news:1710CE37-0664-4A98-B0A8-CD84D16EECCD@.microsoft.com...
> Everytime when I open .SQL file using SQL 2005 management Studio, it ask
> me
> about connection info. Is there any way to use the previous one like SQL
> 2000? For example, first time when I open .SQL file, I put connection
> info,
> and if I open another .SQL file, it will default to the previous
> connection
> info without pop up the "Connect to Server" screen.
> Thanks
> Yong
|||Thanks
"Paul A. Mestemaker II [MSFT]" wrote:
> This behavior has been changed in SQL Server 2005 Service Pack 2. You can
> checkout the December CTP: http://www.microsoft.com/sql/ctp.mspx
> FAQ on SP2:
> http://blogs.msdn.com/sqlrem/archive/2007/01/12/SP2-and-BPA-FAQ.aspx
> Paul A. Mestemaker II
> Program Manager
> Microsoft SQL Server Manageability
> http://blogs.msdn.com/sqlrem/
> "Yong" <Yong@.discussions.microsoft.com> wrote in message
> news:1710CE37-0664-4A98-B0A8-CD84D16EECCD@.microsoft.com...
>
Showing posts with label everytime. Show all posts
Showing posts with label everytime. Show all posts
Wednesday, March 21, 2012
Tuesday, March 20, 2012
Open Sessions using MS Access as Front End
I'm using SQL server 7 on Win NT. I have Access 97 as a front end, with linked tables though ODBC to SQL Server. Everytime I open a table in Access, a session appears when I type sp_who2. I close that table in Access, but I when I type sp_who2 the table session is still present. Does anyone know a cause for this?
I am researching why sometimes when we close are queries and tables in Access we have sessions in SQL server that becomes orphans/ghost. I try to kill the session but can't, so therefore I have to recycle the database.
Any help would be appreciated.What happens if you kill your Access client or re-boot the client PC? If memory serves, ODBC Manager uses a cached connection and will hold a connection past a close. The idea is that you might want to re-connect very soon and by holding a connection the ODBC Manager can save a bit of time on the second connection.|||Originally posted by Paul Young
What happens if you kill your Access client or re-boot the client PC? If memory serves, ODBC Manager uses a cached connection and will hold a connection past a close. The idea is that you might want to re-connect very soon and by holding a connection the ODBC Manager can save a bit of time on the second connection.
If I close the Access client and reboot the machine the session will disappear, but there are times the session won't dissappear and that session becomes an orphan/ghost session . This ghost session then keeps a lock onto the table.
I am researching why sometimes when we close are queries and tables in Access we have sessions in SQL server that becomes orphans/ghost. I try to kill the session but can't, so therefore I have to recycle the database.
Any help would be appreciated.What happens if you kill your Access client or re-boot the client PC? If memory serves, ODBC Manager uses a cached connection and will hold a connection past a close. The idea is that you might want to re-connect very soon and by holding a connection the ODBC Manager can save a bit of time on the second connection.|||Originally posted by Paul Young
What happens if you kill your Access client or re-boot the client PC? If memory serves, ODBC Manager uses a cached connection and will hold a connection past a close. The idea is that you might want to re-connect very soon and by holding a connection the ODBC Manager can save a bit of time on the second connection.
If I close the Access client and reboot the machine the session will disappear, but there are times the session won't dissappear and that session becomes an orphan/ghost session . This ghost session then keeps a lock onto the table.
Subscribe to:
Posts (Atom)