|
Home > Archive > Microsoft Content Management Server > March 2004 > Forcing CMS 2001 to Refresh
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Forcing CMS 2001 to Refresh
|
|
| William 2004-03-02, 5:37 am |
| Hi
Does anyone know of a way to force CMS 2001 to refresh
it's cache. We are replicating data from one CMS database
to another but the target isn't picking up some of the
changes for a while (couple of hours to recognise a new
page).
Restarting IIS works but is there something (functions)
within the CMS API that I could use to force it to refresh?
Thanks in advance
William
| |
| Stefan [MSFT] 2004-03-02, 6:35 am |
| Hi William,
how do you "replicate" the database?
Using ROP files?
If you really mean SQL replication: this is a "no-go" with CMS.
Not supported and can cause database inconsistancies.
See here for details:
http://support.microsoft.com/default.aspx?id=315532
Btw: there is no documented API available to clear the memory cache.
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"William" <anonymous@discussions.microsoft.com> wrote in message
news:544601c40040$578cd1d0$a401280a@phx.gbl...
> Hi
>
> Does anyone know of a way to force CMS 2001 to refresh
> it's cache. We are replicating data from one CMS database
> to another but the target isn't picking up some of the
> changes for a while (couple of hours to recognise a new
> page).
>
> Restarting IIS works but is there something (functions)
> within the CMS API that I could use to force it to refresh?
>
> Thanks in advance
> William
| |
| William 2004-03-02, 6:35 am |
| Hi Stefan
It is SQL replication we're trying. It seems to work fine
and we know it's not 100%, but I was just wondering how to
refresh the cache. I wasn't aware of the KB article you
mentioned. The site's too big for ROP files, the
alternative was an unsupport ROP file solution which would
affect not only our target database, but also the source
database, which was too risky
Thanks
William
>-----Original Message-----
>Hi William,
>
>how do you "replicate" the database?
>Using ROP files?
>
>If you really mean SQL replication: this is a "no-go"
with CMS.
>Not supported and can cause database inconsistancies.
>See here for details:
>http://support.microsoft.com/default.aspx?id=315532
>
>Btw: there is no documented API available to clear the
memory cache.
>
>Cheers,
>Stefan.
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"William" <anonymous@discussions.microsoft.com> wrote in
message
>news:544601c40040$578cd1d0$a401280a@phx.gbl...
database[color=darkred]
refresh?[color=darkred]
>
>
>.
>
| |
| Stefan [MSFT] 2004-03-02, 6:35 am |
| You are risking database inconsistancies.
I would not go this way for a production system.
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"William" <anonymous@discussions.microsoft.com> wrote in message
news:597001c40045$94800da0$a101280a@phx.gbl...
> Hi Stefan
>
> It is SQL replication we're trying. It seems to work fine
> and we know it's not 100%, but I was just wondering how to
> refresh the cache. I wasn't aware of the KB article you
> mentioned. The site's too big for ROP files, the
> alternative was an unsupport ROP file solution which would
> affect not only our target database, but also the source
> database, which was too risky
>
> Thanks
> William
>
> with CMS.
> memory cache.
> confers no rights.
> message
> database
> refresh?
>
|
|
|
|
|