Microsoft Content Management Server - Node table in database out of proportion

This is Interesting: Free IT Magazines  
Home > Archive > Microsoft Content Management Server > December 2004 > Node table in database out of proportion





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 Node table in database out of proportion
John Boghossian

2004-12-22, 2:46 am

Hi there,

We have an set up where content on our cms site is altered on a cms-box on
the inside of our firewall. A deployment script then exports all changes on
the inside to an production server on the outside of the firewall. This
keeps the cms site updated to the latest changes.

The strange thing is that the database files on the production server is 5
times larger that the one on the inside. And when i look at the tables in
the database i see that the table "node" contains 144500 rows on the
production machine and only 6100 rows on the machine on the inside.

If i look at the content via site manager i cannot see any difference
between the two machines. I forst thought that there was a lot of deleted
postings on the production machine. But there are none.

Any ideas?

Regards
John Boghossian


Stefan [MSFT]

2004-12-22, 7:46 am

Hi John,

it seems you never deleted the historical revisions.
Every time you import the postings on the production server you will create
a new revision.
And all the revisions are kept till you choose the Clear Revision history
option in SiteManager.
After this you also have to ensure that background processing is configured
to run against the production database to remove the deleted items.
An additional thing might be that there are lots of expired postings (if you
use this option). Per default background processing does not delete expired
content.
This can be changed by activating the first step in the background
processing job.

Cheers,
Stefan.

"John Boghossian" <john.boghossian@investorab.com> wrote in message
news:OityL3$5EHA.1264@TK2MSFTNGP12.phx.gbl...
> Hi there,
>
> We have an set up where content on our cms site is altered on a cms-box on
> the inside of our firewall. A deployment script then exports all changes

on
> the inside to an production server on the outside of the firewall. This
> keeps the cms site updated to the latest changes.
>
> The strange thing is that the database files on the production server is 5
> times larger that the one on the inside. And when i look at the tables in
> the database i see that the table "node" contains 144500 rows on the
> production machine and only 6100 rows on the machine on the inside.
>
> If i look at the content via site manager i cannot see any difference
> between the two machines. I forst thought that there was a lot of deleted
> postings on the production machine. But there are none.
>
> Any ideas?
>
> Regards
> John Boghossian
>
>



John Boghossian

2004-12-22, 5:52 pm

I see,

Thanks Stefan, for pointing this out. I will surely try this.

Regards
John Boghossian

and by the way

Merry christmas



"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:%23oXEtfA6EHA.3612@TK2MSFTNGP14.phx.gbl...
> Hi John,
>
> it seems you never deleted the historical revisions.
> Every time you import the postings on the production server you will

create
> a new revision.
> And all the revisions are kept till you choose the Clear Revision history
> option in SiteManager.
> After this you also have to ensure that background processing is

configured
> to run against the production database to remove the deleted items.
> An additional thing might be that there are lots of expired postings (if

you
> use this option). Per default background processing does not delete

expired
> content.
> This can be changed by activating the first step in the background
> processing job.
>
> Cheers,
> Stefan.
>
> "John Boghossian" <john.boghossian@investorab.com> wrote in message
> news:OityL3$5EHA.1264@TK2MSFTNGP12.phx.gbl...
on[vbcol=seagreen]
> on
5[vbcol=seagreen]
in[vbcol=seagreen]
deleted[vbcol=seagreen]
>
>



Stefan [MSFT]

2004-12-22, 5:52 pm

Hi John,

same to you and your family!

Cheers,
Stefan.

"John Boghossian" <john.boghossian@investorab.com> wrote in message
news:OkJ1xLD6EHA.3336@TK2MSFTNGP11.phx.gbl...
> I see,
>
> Thanks Stefan, for pointing this out. I will surely try this.
>
> Regards
> John Boghossian
>
> and by the way
>
> Merry christmas
>
>
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:%23oXEtfA6EHA.3612@TK2MSFTNGP14.phx.gbl...
> create
history[vbcol=seagreen]
> configured
> you
> expired
cms-box[vbcol=seagreen]
> on
changes[vbcol=seagreen]
This[vbcol=seagreen]
is[vbcol=seagreen]
> 5
> in
> deleted
>
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com