[dba-SQLServer] Optimizing Stored Procedures and Views

Charlotte Foust cfoust at infostatsystems.com
Fri Apr 7 17:28:51 CDT 2006


Sounds like they replaced your leads as well as the unit itself.  I got
off lightly this time, they just unzipped my chest pocket and clipped in
a new pacer, no need to replace any of the wiring.  I felt pretty seedy
for a week, but you will feel much better with a lot of rest ... And no
early morning/late night programming! LOL 


Charlotte Foust

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of David
Emerson
Sent: Friday, April 07, 2006 2:11 PM
To: dba-sqlserver at databaseadvisors.com; accessd at databaseadvisors.com
Subject: Re: [dba-SQLServer] Optimizing Stored Procedures and Views

Dear all,

Thanks for all your suggestions.  I was given 18 hours notice to turn up
to our hospital for a pacemaker replacement (I wore out the old one -
too much late night/early morning programming).

Operation successful but I feel as if someone hit my shoulder with a
sledgehammer (which they well might have done considering the banging
that was going on during the operation).

Hope to be back on deck next week to follow up the suggestions.

David

At 6/04/2006, you wrote:
>If this is a very busy table you can generally use table hints to 
>prevent locking the table, and is generally very fast, simplay add a
>WITH(NOLOCK) at the end of your table names (not variable tables).
>
>
>On 4/5/06, David Lewis <DavidL at sierranevada.com> wrote:
> > Well, there is a lot there to begin to look through...
> >
> > One thing that sticks out is the
> >
> > "SELECT TOP 100 PERCENT"   in the underlying view.  Remove that and
the
> > "ORDER BY" clause and you will do much to streamline the execution 
> > of the view.  Also consider making as many of the queries covered as

> > possible by either adding indexes or removing columns from the views

> > that are not needed in the final query.
> >
> > I am not very experienced with streamline execution plans by 
> > optimizing joins, but I do try to read what comes my way and I have 
> > read that all joins are NOT created equal.  Because your joins are 
> > relatively complex, it may be that there is much to do in that area.

> > When I find a good reference I will pass it on...
> >
> > D. Lewis
> > _______________________________________________
> > dba-SQLServer mailing list
> > dba-SQLServer at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> > http://www.databaseadvisors.com
> >
> >
>
>
>--
>-Francisco
>http://pcthis.blogspot.com |PC news with out the jargon!
>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




More information about the dba-SQLServer mailing list