Re: Avoiding the use of CACHE in SQL2000
From: AA (aa_at_personal.net.py)
Date: 06/08/04
- Next message: Hari: "Re: Convert Oracle 'create index' to SQLServer"
- Previous message: Stefan Olofsson: "Cascading delete on self referenced table"
- In reply to: Uri Dimant: "Re: Avoiding the use of CACHE in SQL2000"
- Next in thread: Tibor Karaszi: "Re: Avoiding the use of CACHE in SQL2000"
- Reply: Tibor Karaszi: "Re: Avoiding the use of CACHE in SQL2000"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 8 Jun 2004 06:04:58 -0400
I'll read each command. :)
Thanks a lot Uri
AA
"Uri Dimant" <urid@iscar.co.il> wrote in message
news:%23Lzhe0TTEHA.3944@TK2MSFTNGP12.phx.gbl...
> AA
> I see what you mean
> DBCC FREEPROCCACHE clears the procedure cache and causes ad hoc queries to
> be recompiled
>
> if you want a stored procedure to be compiled you will need to use the
WITH
> RECOMPILE option
>
> if you want to clear the data cache you will need to use DBCC
> DROPCLEANBUFFERS
>
> DBCC FLUSHPROCINDB: Used to clear out the stored procedure cache for a
> specific database on a SQL Server, not the entire SQL Server. The database
> ID number to be affected must be entered as part of the command.
>
> You may want to use this command before testing to ensure that previous
> stored procedure plans won't negatively affect testing results.
>
> Example:
>
> DECLARE @intDBID INTEGER SET @intDBID = (SELECT dbid FROM
> master.dbo.sysdatabases WHERE name = 'database_name')
> DBCC FLUSHPROCINDB (@intDBID)
>
>
>
>
> "AA" <aa@personal.net.py> wrote in message
> news:%23VV77tTTEHA.1232@TK2MSFTNGP09.phx.gbl...
> > To the production /live database has only access the user of our System
> > but to the historical database has access peoples of marketing etc, to
> make
> > simple query, usually two or three times per week, and that is the
> problem,
> > I don't want that any query (including not optimized queries) in the
> > historical database affect the live (production) database.
> >
> > I can't limit the CPU and I can't limit the use of Memory so, I want to
> > limit at least the use of CACHE
> >
> > Any suggest?
> >
> > Two instances?
> >
> > I have a SQL2000 and Windows 2003 in cluster.
> >
> > Thanks a lot
> >
> > AA
> >
> >
> > "Uri Dimant" <urid@iscar.co.il> wrote in message
> > news:e6OfBNSTEHA.1368@TK2MSFTNGP11.phx.gbl...
> > > AA
> > > I think if you do a query against your historical database for
instance
> > > some stored procedure so optimyzer will insert into the cache the
> > execution
> > > plan and you cannot prevent it. What do you try to accomplish? Don't
you
> > > have enough memory for your live database?
> > >
> > >
> > > "AA" <aa@personal.net.py> wrote in message
> > > news:OmG0RESTEHA.332@TK2MSFTNGP11.phx.gbl...
> > > > Do exists the possibility to avoid the use of cache for certain
> Database
> > > or
> > > > Query
> > > >
> > > > I have a production Database and a historical database.
> > > > I want to cache all transaction in the production database, but
avoid
> > the
> > > > cache in the historical database.
> > > >
> > > > Is possible to do that with SQL2000?
> > > >
> > > >
> > > > Thanks a lot
> > > >
> > > > AA
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Next message: Hari: "Re: Convert Oracle 'create index' to SQLServer"
- Previous message: Stefan Olofsson: "Cascading delete on self referenced table"
- In reply to: Uri Dimant: "Re: Avoiding the use of CACHE in SQL2000"
- Next in thread: Tibor Karaszi: "Re: Avoiding the use of CACHE in SQL2000"
- Reply: Tibor Karaszi: "Re: Avoiding the use of CACHE in SQL2000"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|