cache in sql server 2000

There is a command or option that let me change or manipulate
the size of procedure and data cache in order to obtain better
performance ratios in sql server 2000?
--
ThanksNo there is not one for the procedure cache. You can set the MAX size the
memory pool uses with MAX Server Memory but you can't actually control the
individual sizes. Your best bet is to make sure you optimize the calls so
that the plans are reused and the proc cache will stay small and manageable.
--
Andrew J. Kelly SQL MVP
"byteman" <byteman@.discussions.microsoft.com> wrote in message
news:7944D92A-F413-49ED-8DED-6F7B50968889@.microsoft.com...
> There is a command or option that let me change or manipulate
> the size of procedure and data cache in order to obtain better
> performance ratios in sql server 2000?
> --
> Thanks|||Just to add to Andrew's reply, please write to sqlwish@.microsoft.com and let
them know if this is something you'd like to see... It would be nice to put
some pressure on the SQL Server team to get this feature in.
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"byteman" <byteman@.discussions.microsoft.com> wrote in message
news:7944D92A-F413-49ED-8DED-6F7B50968889@.microsoft.com...
> There is a command or option that let me change or manipulate
> the size of procedure and data cache in order to obtain better
> performance ratios in sql server 2000?
> --
> Thanks|||"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:ui4$dIv5FHA.2560@.TK2MSFTNGP12.phx.gbl...
> Just to add to Andrew's reply, please write to sqlwish@.microsoft.com and
> let them know if this is something you'd like to see... It would be nice
> to put some pressure on the SQL Server team to get this feature in.
>
I think it's a philosophy thing. It's best to have that managed
automatically. You have one knob to turn (total server memory). Other than
that tune your application, not the database server.
David|||If you want that "feature," go back to version 6.5 or earlier. Better yet,
convert to Oracle, then you can spend all day twiddling knobs, EVERY DAY.
That will be the only work you will ever get to do.
As for me, I would rather spend more of my time helping the developers build
better designs, access methods, and scaling our architecture.
Sincerely,
Anthony Thomas
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:u11NMOv5FHA.1420@.TK2MSFTNGP09.phx.gbl...
> "Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
> news:ui4$dIv5FHA.2560@.TK2MSFTNGP12.phx.gbl...
> > Just to add to Andrew's reply, please write to sqlwish@.microsoft.com and
> > let them know if this is something you'd like to see... It would be nice
> > to put some pressure on the SQL Server team to get this feature in.
> >
> I think it's a philosophy thing. It's best to have that managed
> automatically. You have one knob to turn (total server memory). Other
than
> that tune your application, not the database server.
> David
>|||If you work on an enterprise-level application you'll quickly find that
certain "automatic" management features just don't do a good enough job.
They're great for small to medium applications, but it's nice to tweak
things for larger setups.
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:uNrSwBw5FHA.444@.TK2MSFTNGP11.phx.gbl...
> If you want that "feature," go back to version 6.5 or earlier. Better
> yet,
> convert to Oracle, then you can spend all day twiddling knobs, EVERY DAY.
> That will be the only work you will ever get to do.
> As for me, I would rather spend more of my time helping the developers
> build
> better designs, access methods, and scaling our architecture.
>|||Yea, well, I currently work on more than 200 of those applications across
more than 50 SQL Server installations, with 6 or more of those on
medium-scaled clustered configurations.
So, I would push SQLWISH to keep driving at making those autonomic features
more reliable so there would be less need for the missing knobs.
We run Oracle in this shop too, and that is all I see those poor guys do all
day long.
Sincerely,
Anthony Thomas
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:ueZqAxw5FHA.2716@.TK2MSFTNGP11.phx.gbl...
> If you work on an enterprise-level application you'll quickly find that
> certain "automatic" management features just don't do a good enough job.
> They're great for small to medium applications, but it's nice to tweak
> things for larger setups.
>
> --
> Adam Machanic
> Pro SQL Server 2005, available now
> http://www.apress.com/book/bookDisplay.html?bID=457
> --
>
> "Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
> news:uNrSwBw5FHA.444@.TK2MSFTNGP11.phx.gbl...
> > If you want that "feature," go back to version 6.5 or earlier. Better
> > yet,
> > convert to Oracle, then you can spend all day twiddling knobs, EVERY
DAY.
> > That will be the only work you will ever get to do.
> >
> > As for me, I would rather spend more of my time helping the developers
> > build
> > better designs, access methods, and scaling our architecture.
> >
>|||Let's not confuse "automation" with "defaults." I'll agree with Adam in
that as you get into larger and more critical systems, the system
configuration and database object defaults become less and less useful;
however, the concept that the system parameters are dynamically set and
"automatically" managed remains valid. I would go as far as to say that the
dynamic configuration management becomes even more critical with larger
scale systems.
The whole point of computing platforms and solutions is the drive to
systematically apply logical algorithms to manual processes in an automation
mechanism. The DBMS is no less critical to this function: manual, labor
intensive processes are automated freeing up time to redirect human
resources to higher level, abstracted tasks and functions such as design and
architecture.
Sincerely,
Anthony Thomas
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:u8uq99w5FHA.1184@.TK2MSFTNGP12.phx.gbl...
> Yea, well, I currently work on more than 200 of those applications across
> more than 50 SQL Server installations, with 6 or more of those on
> medium-scaled clustered configurations.
> So, I would push SQLWISH to keep driving at making those autonomic
features
> more reliable so there would be less need for the missing knobs.
> We run Oracle in this shop too, and that is all I see those poor guys do
all
> day long.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
> news:ueZqAxw5FHA.2716@.TK2MSFTNGP11.phx.gbl...
> > If you work on an enterprise-level application you'll quickly find that
> > certain "automatic" management features just don't do a good enough job.
> > They're great for small to medium applications, but it's nice to tweak
> > things for larger setups.
> >
> >
> > --
> > Adam Machanic
> > Pro SQL Server 2005, available now
> > http://www.apress.com/book/bookDisplay.html?bID=457
> > --
> >
> >
> > "Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
> > news:uNrSwBw5FHA.444@.TK2MSFTNGP11.phx.gbl...
> > > If you want that "feature," go back to version 6.5 or earlier. Better
> > > yet,
> > > convert to Oracle, then you can spend all day twiddling knobs, EVERY
> DAY.
> > > That will be the only work you will ever get to do.
> > >
> > > As for me, I would rather spend more of my time helping the developers
> > > build
> > > better designs, access methods, and scaling our architecture.
> > >
> >
> >
>