Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Two SPS 03 questions - STSADM & Site size related

  Asked By: Jordan    Date: Nov 24    Category: Sharepoint    Views: 1894

Did an stsadm backup of a top level and to restore I had to create a
new content DB. The content DB size is now 1 3/4 times as large as
the site I backed up and the log file is larger than the logfile of
the portal that I backed up the individual site from. Any ideas why?

Second question might be easier. Anyone know of a query I can run to
get the size of a site and all subsites from x point on ie from
http://portal/sites/site1/x forward? I can query the DB and get the
total size for the top level but I dont know how to get the size for a
level below and further without going into frontpage or designer and
then looking at each site individually. None of the SQL reporting
tools are installed either :( There was one query I found on the web
but it didn't seem to work for some reason and now I cant find it
again to see if I can build on it (maybe because it didnt work.



6 Answers Found

Answer #1    Answered By: Corina Duran     Answered On: Nov 24

I do not know a way to query  all sites. The most likely reason  you had
to create  another content  database is that the original site  backed up
still existed, perhaps under a different name. Each Site Collection is
assigned a unique ID (guid) and two Site Collections with the same guid
cannot exist in the same content database.

This might help?

Answer #2    Answered By: Irving Hurley     Answered On: Nov 24

Sorry if I wasn't clear in my question. I knew why I had
to create  the new content  DB what I dont get is the growth. Why
would the new content DB, and the log  files, be larger than the
original? And not just a little bit. I'm talking a LOT larger.

Answer #3    Answered By: Vinay Thakur     Answered On: Nov 24

Since I didnt see a way to edit my original post let me use this to
add that I do understand why I had to create  the 2nd content  DB. We
didn't delete the old site  and you can't have duplicate IDs. What I
dont understand is why the new content DB and related  log file  are
larger than the old ones and not just by a little....

Answer #4    Answered By: Kristie Hardy     Answered On: Nov 24

Repeat after me, "Transaction log size  has NOTHING to do with database size."

The second transaction log  is probably so large  because it has all the
transaction from the STSADM restore  in it. Back it up, then shrink it if you're
concerned about size. If you never, ever, ever, plan on doing point  in time
restores of your data set your database recovery mode to Simple, then shrink the
Transaction log.

Answer #5    Answered By: Faith Delgado     Answered On: Nov 24

Out of curiosity, do you see any value in keeping the Config DB's in Full
recovery mode or would it be just as good to set those to Simple?

Answer #6    Answered By: Alisha Itagi     Answered On: Nov 24

It depends on what your recovery metrics are. We're currently comfortable with
being limited to the last backup, so Simple Mode works for us. I don't have a
good idea of how large  the transaction logs can get for the config logs, so I
can't really make much in the way of recommendations.

Didn't find what you were looking for? Find more on Two SPS 03 questions - STSADM & Site size related Or get search suggestion and latest updates.