default database for scripts in SSMS

When I write a script in SSMS (I'm using SQL Server 2005), generally the
database that pops up in the pulldown window on the menu, and which the
script runs against (unless/until I change the pulldown selection), is the
master database. I'm working with only one database I've created, and I
rarely run scripts against the master database, so is there an option to have
SSMS default to my database instead of the master database?
Ed
Change the user default database. Go to Security, Logins, right-clik your
login and select default database.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Ed White" wrote:

> When I write a script in SSMS (I'm using SQL Server 2005), generally the
> database that pops up in the pulldown window on the menu, and which the
> script runs against (unless/until I change the pulldown selection), is the
> master database. I'm working with only one database I've created, and I
> rarely run scripts against the master database, so is there an option to have
> SSMS default to my database instead of the master database?
> --
> Ed

Debugging SQL SERVER Stored Procedures

I don't see the option to debug a stored procedure. I right click onthe procedure and should'nt it appear in the properties window. Do Ineed to install some extra component to get the debugger.

I don't remember clearly but IMO it was dependant on the VS.NET version. But don't take that one as granted, I really don't remember. Try Google.

Anyways,here is explained what is needed to setup debugging and how to try it out. Andhere'salso a few words how to debug in Query Analyzer and again the instructions visualized for VS.NET.

|||Thanks for the reply.
I went to this link:http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vxlrfsettingupsqldebuggingenablingsqldebuggingonsql2000desktop.asp
And copied the .dll from the Visual Studio 2003/sqlserver it says put the file in the binn directory. Are they talking about the bin directory of the Asp.net Project.

|||okay so I copied the .dll file into SQL SERVEr Binn folder. But nowwhen I debug the strored procedure it just shows the Arrow => butwhen I press F11 so it can go to the next line It just exits
And prints the message :
// GEEK0001 is the name of my computer
The thread GEEK0001 has exicted with code 0 (0x0)
|||okay I got it to work !
:D

Debugging in SSIS - Immediate and Command windows

Hi everyone,
I am having a difficult time debugging a package that I'm working on. I read in BOL that the immediate window should be an option during debugging but I can't find it anywhere(nor can I enable it), and I was planning on using it to access an oledb source property that is using an expression. Is the command window the same as immediate? I didn't orignally think so but I'm not sure. What is the syntax to use for this once I find it?
Thanks,
Adrian

You can't access runtime values of an oledb source property but you can see what data going downstream using visualizers.

Command window isn't supported.

Can you give me a ref where in BOL you found about immediate window?

|||Nick, thanks for responding, I didn't see that anyone had responed until now.
I found it here:
ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.SQLSVR.v9.en/extran9/html/54a458cc-9f4f-4b48-8cf2-db2e0fa7756c.htm

Adrian

Debug output no longer displaying?

I must have hit some setting to turn off the debug output, but I can't find how to get it back on. The debug output window displays when I execute a package, I just don't get the execution output I had been getting. Sorry to bother you with such trivia, but any help you can provide is appreciated. Thanks.

If I understand you correctly, then what you are looking for is under 'View - Output'.

Pipo

|||That's what I am looking at, but the output window is empty - nothing is being generated in the window when I execute the package. It had been before - just not anymore.|||Got it. When I right click within the output window the option for program output was not checked. When I clicked on that option to set the check on, I then began to get the output trace again.