Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.databases.ms-sqlserver > #498

Re: SSMS Query Designer chokes on ANSI Analytic Functions. Any Workaround?

From bill <billmaclean1@gmail.com>
Newsgroups comp.databases.ms-sqlserver
Subject Re: SSMS Query Designer chokes on ANSI Analytic Functions. Any Workaround?
Date 2011-07-07 12:05 -0700
Organization http://groups.google.com
Message-ID <811c7fc2-1e73-4dfd-8705-2c485644faef@v11g2000prn.googlegroups.com> (permalink)
References <fd6bcad5-5c3d-4523-a86b-3910f96b3df4@em7g2000vbb.googlegroups.com> <Xns9F15ED02A6F24Yazorman@127.0.0.1> <a2b4a290-67cb-4a9a-8bb4-429fc44cb2e9@x12g2000yql.googlegroups.com> <Xns9F166AD2268E4Yazorman@127.0.0.1>

Show all headers | View raw


I agree that graphics are inherantly limited.  Trying to graphically
build an analytic function would be difficult.  I would just like the
designer not to choke on a query (that may or may not be inside of a
CTE) that is created with valid SQL syntax.

The idea would be this:  Someone comfortable with advanced SQL could
write whatever they need for a query / view.  But  if, say, a column
from an already joined table needs to be added later, a less
experienced person ought to be able to open the query in Designer
without trashing it.

The designer currently represents CTE's (that don't use analytic
functions) as just another box on the painter surface, which is fine.
They need to make it so that designer will recognize the code for
analytic functions and put the resulting column in the appropriate
box.  I don't think that is all that different than SELECT A + B AS C
from <table>

THanks,

Bill

On Jul 2, 1:30 am, Erland Sommarskog <esq...@sommarskog.se> wrote:
> bill (billmacle...@gmail.com) writes:
> > Has anyone heard if the Designer will be improved in Denali?
>
> I doubt.
>
> One problem with a thing like the Designer is that there is only so much
> you can do with a graphical interface. How would you visualise a row number?
> A running sum (improvement to the OVER() clause added in Denali.)
>
> Of course it doesn't help if what you have is rotten from the bottom up.
>
> Personally, I think the best improvement that Microsoft could do is to
> pull it. Alas, it is still there.
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@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

Back to comp.databases.ms-sqlserver | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

SSMS Query Designer chokes on ANSI Analytic Functions.  Any Workaround? bill <billmaclean1@gmail.com> - 2011-07-01 11:17 -0700
  Re: SSMS Query Designer chokes on ANSI Analytic Functions. Any Workaround? Erland Sommarskog <esquel@sommarskog.se> - 2011-07-01 23:17 +0200
    Re: SSMS Query Designer chokes on ANSI Analytic Functions. Any Workaround? bill <billmaclean1@gmail.com> - 2011-07-02 01:05 -0700
      Re: SSMS Query Designer chokes on ANSI Analytic Functions. Any Workaround? Erland Sommarskog <esquel@sommarskog.se> - 2011-07-02 10:30 +0200
        Re: SSMS Query Designer chokes on ANSI Analytic Functions. Any Workaround? bill <billmaclean1@gmail.com> - 2011-07-07 12:05 -0700
    Re: SSMS Query Designer chokes on ANSI Analytic Functions. Any Workaround? "Fred." <ghrno-google@yahoo.com> - 2011-07-04 16:31 -0700

csiph-web