|
Home > Archive > Microsoft Content Management Server > March 2004 > Database replication and caching
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 |
Database replication and caching
|
|
| Samer Mas 2004-03-30, 10:07 am |
| Dear All
First of all, let me explain what we have done:
We have 2 CMS servers, one that is used locally to add and edit postings,
and another one -readonly- which is used to service online visitors to our
web site.
Now instead of doing continuous SDO exports/imports between the 2 servers,
we decided to do a database replication between the SQL Servers of both CMS
servers.
Everything seems to be working fine so far, but I have a big question about
caching, and that is, on the online server, and since the data is being
changed on the database level, will the CMS default caching ever notice that
teh data has changed, and the cache might need to be refreshed.
In other words if we created a posting on our local server, and it gets
replicated to the online server and it gets cached (becuase someone visited
it), and then we modifed the posting on the local server, and the
modification gets replicated online via SQL, will the online users see the
cached version or the new one?
Thanks
| |
| Stefan [MSFT] 2004-03-30, 12:46 pm |
| Hi Samer,
database replication is a no-go! It can cause database inconsistancies
exactly due to the fact that the cache is running out of sync with the
database.
See the following KB article.
http://support.microsoft.com/default.aspx?id=315532
Logshipping would be a supported scenario:
http://support.microsoft.com/default.aspx?id=322742
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Samer Mas" <samer.maslamani@ihorizons.com> wrote in message
news:#V$oNhmFEHA.4084@TK2MSFTNGP11.phx.gbl...
> Dear All
>
> First of all, let me explain what we have done:
>
> We have 2 CMS servers, one that is used locally to add and edit postings,
> and another one -readonly- which is used to service online visitors to our
> web site.
>
> Now instead of doing continuous SDO exports/imports between the 2 servers,
> we decided to do a database replication between the SQL Servers of both
CMS
> servers.
>
> Everything seems to be working fine so far, but I have a big question
about
> caching, and that is, on the online server, and since the data is being
> changed on the database level, will the CMS default caching ever notice
that
> teh data has changed, and the cache might need to be refreshed.
>
> In other words if we created a posting on our local server, and it gets
> replicated to the online server and it gets cached (becuase someone
visited
> it), and then we modifed the posting on the local server, and the
> modification gets replicated online via SQL, will the online users see the
> cached version or the new one?
>
> Thanks
>
>
|
|
|
|
|