David McAfee
davidmcafee at gmail.com
Wed Oct 3 13:07:01 CDT 2012
OK, now this is weird. Now it is working the way it is supposed to. I tried to recreate the problem by going to database1 and opening a sproc from database2. It now changes the db name, it wasn't doing that before either. I'm going to have to keep an eye on it and see if I am doing something to make this happen. It's happened to me a couple of times. D On Wed, Oct 3, 2012 at 11:02 AM, David McAfee <davidmcafee at gmail.com> wrote: > Exactly! > > I'm working on one, and get a call to modify something in another database. > I go back to the code I was working on and hit F5 and get a "table doesn't > exist" message, but it could easily have been a delete or update script. > > Scary! > > :) > > D > > > On Wed, Oct 3, 2012 at 10:51 AM, Francisco Tapia <fhtapia at gmail.com>wrote: > >> Wow!! That seems dangerous!! >> >> Sent from my mobile device >> >> On Oct 3, 2012, at 10:50 AM, David McAfee <davidmcafee at gmail.com> wrote: >> >> > Is anyone else playing with SQL Server 2012 yet? >> > >> > In 2005, you could open a tab and enter some TSQL against databaseA >> > You could then open a New Query tab and do something else against >> > databaseB. >> > >> > When you would switch back to the first tab, the drop down with the >> > database name would switch back to database A and vice versa. >> > >> > This doesn't seem to be the case with SSMS 2012. >> > >> > Is there a setting that I can't see? >> > >> > Thanks, >> > David >> >>