[dba-SQLServer] Being helpful

Having said this, and having used both 2.0 and 3.0... I really prefer 3.0 it
is a very robust and very helpful tool.  Not to mention it is lightning
fast, it does a much better job of caching and updating as you add new
objects to the database.  in 2.0 the only way to see your new objects was to
manually refresh the cache for 2.0, in 3.0 this seems to have been taken
care of in the background for you.



On Thu, Mar 27, 2008 at 10:51 AM, Francisco Tapia <fhtapia at gmail.com> wrote:

> you can find it here:
>
>
> http://www.bustercollings.com/blog/2006/06/14/m-sql-query-analyzer-auto-complete-intellisense/
>
>
> On Thu, Mar 27, 2008 at 10:45 AM, jwcolby <jwcolby at colbyconsulting.com>
> wrote:
>
> > SQL Prompt 2.0 still free?  I am not finding it.
> >
> >
> > John W. Colby
> > Colby Consulting
> > www.ColbyConsulting.com
> > -----Original Message-----
> > From: dba-sqlserver-bounces at databaseadvisors.com
> > [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of
> > Francisco
> > Tapia
> > Sent: Thursday, March 27, 2008 1:25 PM
> > To: Discussion concerning MS SQL Server
> > Subject: Re: [dba-SQLServer] Being helpful
> >
> > it would seem that you may look forward to the ever upgrade path from
> > M$.
> > while there are current purchasable apps you can get for Sql Server such
> > as
> > Sql Prompt (2.0 free or 3.0purchase) that provide intellisense and
> > really
> > help speed up much of the syntax building process there are also other
> > tools
> > from similar vendors that will help with syntax problems etc.  The
> > follow up
> > upgrade to sql server, that is SqlServer 2008 will provide a lot of
> > really
> > cool tools such as intellisense, and the ability to run the same script
> > accross multiple servers etc. neat stuff, along w/ things like db
> > comrpession etc.
> >
> > Until then, I think the community has been helpful, and so long as we
> > all
> > try to stay ontopic we can avoid another rant gone wrong.
> > --
> > Francisco
> >
> > On Thu, Mar 27, 2008 at 10:16 AM, jwcolby <jwcolby at colbyconsulting.com>
> > wrote:
> >
> > > Much of my frustrations come from switching from a development
> > > environment like .Net or Access to the query editor in SQL Server.
> > > Even in the relatively basic Access we have modules and classes,
> > > intellisense, syntax checking, error handlers, compile time errors
> > > that actually mean something and so forth.
> > > What a jarring contrast to switch to SQL Server query editor.
> > >
> > > But I am making progress.
> > >
> > > John W. Colby
> > > Colby Consulting
> > > www.ColbyConsulting.com
> > >
> > >
> >
> >
> > --
> > -Francisco
> > http://sqlthis.blogspot.com | Tsql and More...
> > _______________________________________________
> > dba-SQLServer mailing list
> > dba-SQLServer at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> > http://www.databaseadvisors.com
> >
> > _______________________________________________
> > dba-SQLServer mailing list
> > dba-SQLServer at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> > http://www.databaseadvisors.com
> >
> >
>
>
> --
> -Francisco
> http://sqlthis.blogspot.com | Tsql and More...
>



-- 
-Francisco
http://sqlthis.blogspot.com | Tsql and More...