Prev: Help finding first payment date and amount
Next: Database roles execute
From: Keith G Hicks on 4 Jun 2010 10:20
"Erland Sommarskog" <esquel(a)sommarskog.se> wrote in message
news:Xns9D8DA1ABA463Yazorman(a)127.0.0.1...
> Keith G Hicks (krh(a)comcast.net) writes:
>> "Erland Sommarskog" <esquel(a)sommarskog.se> wrote in message
>>> Personally, I use PRINT and SELECT in my code to debug. One reason is
>>> that I often want to see the contents of tables.
>>>
>>
>> Are you talking about when you run a procedure directly in SSMS or when
>> you run it from source code or from the VS sql debugger window?
>
> Directly from SSMS. (Or Query Analyzer, which I prefer to use at work.)
> I don't use Visual Studio to work with SQL Server. (Visual Studio leaves
> me in a complete maze.)
>

I was so happy when it became possible to step through code in sql
procedures. It's helped me out tremendously. I don't use it all the time but
once in a while if I'm stuck on something, it lets me pinpoint the problem
very quickly.

Isn't QA built into SSMS? Isn't it just a matter of hitting the "new query"
button or is there a separate tool like there was with EM? I thought they
were combined now.

> --
> Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx



From: Erland Sommarskog on 4 Jun 2010 18:17
Keith G Hicks (krh(a)comcast.net) writes:
> Isn't QA built into SSMS? Isn't it just a matter of hitting the "new
> query" button or is there a separate tool like there was with EM? I
> thought they were combined now.

Nah, what SSMS has is called the Query Editor.

You are right that SSMS in terms of functionality combines QA and EM.
But for running queris, Query Analyzer is simply more palatable in my
opinion. There are some irritating flaws in SSMS. (But viewing execution
plans and XML documents is best done in SSMS.)


--
Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

From: Keith G Hicks on 4 Jun 2010 20:58
"Erland Sommarskog" <esquel(a)sommarskog.se> wrote in message
news:Xns9D8E2EB398FEYazorman(a)127.0.0.1...
> Keith G Hicks (krh(a)comcast.net) writes:
>> Isn't QA built into SSMS? Isn't it just a matter of hitting the "new
>> query" button or is there a separate tool like there was with EM? I
>> thought they were combined now.
>
> Nah, what SSMS has is called the Query Editor.
>
> You are right that SSMS in terms of functionality combines QA and EM.
> But for running queris, Query Analyzer is simply more palatable in my
> opinion. There are some irritating flaws in SSMS. (But viewing execution
> plans and XML documents is best done in SSMS.)


Are you talking about the same QA that came with SQL 2000 or is it a
different one?



>
> --
> Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se
>
> Links for SQL Server Books Online:
> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
> SQL 2000:
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>


From: Erland Sommarskog on 5 Jun 2010 05:39
Keith G Hicks (krh(a)comcast.net) writes:
> Are you talking about the same QA that came with SQL 2000 or is it a
> different one?

I'm talking about QA2000, nothing else.


--
Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

First  |  Prev  | 
Pages: 1 2
Prev: Help finding first payment date and amount
Next: Database roles execute