Bring back Query Analyser

Hi,
I am using 2005 SQL Management to edit my T-SQL stuff but it reformats all
of my SQL statements (just like Enterprise Manager) making complex
statements impossible to read.
Can anyone tell me if there any options to turn this off and/or an
alternative?
Thanks for any help,
Steve.I am using 2K5 SQL Management, your problem doesn't occur at my site.
Do you use query builder?
Steve Lloyd wrote:
> Hi,
> I am using 2005 SQL Management to edit my T-SQL stuff but it reformats all
> of my SQL statements (just like Enterprise Manager) making complex
> statements impossible to read.
> Can anyone tell me if there any options to turn this off and/or an
> alternative?
> Thanks for any help,
> Steve.|||Hi, thanks for the reply,
Ok, find out a few more things... Stored procedures open using query builder
and I can retain the formatting but Views open Enterpise Manager style and I
can't work out how to stop it...
Thanks again
Steve
<navyzhu@.gmail.com> wrote in message
news:1149757541.865478.194360@.h76g2000cwa.googlegroups.com...
>I am using 2K5 SQL Management, your problem doesn't occur at my site.
> Do you use query builder?
> Steve Lloyd wrote:
>|||Steve Lloyd (steve.remove@.livenowpaylater.this.co.uk) writes:
> Ok, find out a few more things... Stored procedures open using query
> builder and I can retain the formatting but Views open Enterpise Manager
> style and I can't work out how to stop it...
Stop using the Query Designer.
After all, since the subject line says bring back "Query Analyzer", you
should be used to be without the Query Designer as it is not present in
Query Analyzer.
As long as you stick to the regular query editor in Mgmt Studio, there
should be no reformatting.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||In addition to Erland's post:
Keep your DDL scripts somewhere safe, and only use them to create/alter/drop
SQL objects.
ML
http://milambda.blogspot.com/|||OK, it think I'm not making myself clear.. I want to be able to edit my
Views, Query Analyzer style, but when I open them in SQL Management they
default to the Query Builder and I can't work out how to open them without.
Sorry for the confusion...
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns97DC7DAD2FAEBYazorman@.127.0.0.1...
> Steve Lloyd (steve.remove@.livenowpaylater.this.co.uk) writes:
> Stop using the Query Designer.
> After all, since the subject line says bring back "Query Analyzer", you
> should be used to be without the Query Designer as it is not present in
> Query Analyzer.
> As long as you stick to the regular query editor in Mgmt Studio, there
> should be no reformatting.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||Right click on the view
DO NOT select modify view
Instead choose Script View as -->ALTER To--> New Query window
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Steve Lloyd wrote:
> OK, it think I'm not making myself clear.. I want to be able to edit my
> Views, Query Analyzer style, but when I open them in SQL Management they
> default to the Query Builder and I can't work out how to open them without
.
> Sorry for the confusion...
> "Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
> news:Xns97DC7DAD2FAEBYazorman@.127.0.0.1...|||> Right click on the view
> DO NOT select modify view
> Instead choose Script View as -->ALTER To--> New Query window
This is easily in my top ten of pet peeves in Management Studio. Not just
because Modify does this weird thing with a useless Access-style view
designer that drives me bonkers, but combined with the slowness and the
frequency that I click the wrong menu item, it is maddening.
I was told off the cuff that they're going to add some options to the
immediate right-click menu for views, but I don't know when they'll be
implemented...

BPA - SQL 2005 - T-SQL

Hi there

I am looking for some help with the BPA on SQL 2005, I can not seem to get it to recognise any T-SQL best practices, I can deliberately sneak in a SELECT * or INSERT INTO with no feild list into SP's but the BPA does not pick them up.

Am I missing something ?

Thanks

Tim

i hope this helps u

http://vyaskn.tripod.com/coding_conventions.htm

http://vyaskn.tripod.com/sql_server_administration_best_practices.htm

http://vyaskn.tripod.com/sql_server_administration_best_practices.htm

Madhu

|||

BPA is primarily concerned with security issues. It is NOT a code analysis tool. It does not check for coding standards and practices.

I suggest that you may wish to explore "SQL Refractor" from www.RedGate.com.

|||

Tim Hatcher wrote:

I am looking for some help with the BPA on SQL 2005, I can not seem to get it to recognise any T-SQL best practices, I can deliberately sneak in a SELECT * or INSERT INTO with no feild list into SP's but the BPA does not pick them up.

I've answered this and other questions in this blog post:

http://blogs.msdn.com/sqlrem/archive/2007/01/12/SP2-and-BPA-FAQ.aspx

"We used SQL Server 2000 Best Practices Analyzer 1.0 to check our T-SQL code. It is very useful in our development process. Why are you getting rid of it?
The best practices utilities across Microsoft are more focused toward operations/management. We are aligning SQL Server’s BPA to the corporate standard. We agree that there should be aids in checking best practices in code, but don’t feel that BPA is the right tool for the job. Software like FxCop or plug-ins to Visual Studio and Management Studio would be the ideal location for such checks."

There are also technical challenges around why we could not do it in this release. I apologize for the inconvenience.

Paul A. Mestemaker II

Program Manager

Microsoft SQL Server Manageability

http://blogs.msdn.com/sqlrem/