backup file to big

I have a database who's SQL Server backup file has been hovering around 33MB
and has been growing only a few hundred kilobytes week for a couple years.
I have since added a catalog and indexed a couple of tables and now this
database and another one on the server--that should be unrelated--have
backup files that are 140 and 170MB each. The indexes are really not that
big. The catalog is only about 20MB.
First, why would a 20MB catalog increase the size of this database so much.
Second, why would a catalog in one database affect one in another (if that's
what's really happening)
Third, how can I do a tally of the database elements that should comprise
the total so I can find out the true cause of the increase. Counting the
tables size in K + the indexes does not give me this huge file size.
_____
DC G
DC G,
Assuming that you're using SQL Sever 7.0 or SQL Server 2000 and no other
logged activity has occurred in the same database that you created the FT
Catalog and ran a Full Population, as the affect of only doing this type of
"read only" process should not of contributed to the growth in the size of
your database backup. Indeed, this has been one of the long outstanding
issues, i.e.. to include the FT Catalog with the database backup, that is
not included in either SQL 7.0 or 2000, but is only available as a new
feature in SQL Server 2005 (Yukon).
Q. why would a 20MB catalog increase the size of this database so much?
A. It should not. Did you make any other database &/or table changes? For
example alter a table and add a timestamp or other new column?
Q. why would a catalog in one database affect one in another?
A. It should not. Did you make any database changes &/or table schema
changes to either database?
Q. how can I do a tally of the database elements that should comprise the
total so I can find out the true cause of the increase?
A. You can use sp_spaceused or as well as the Enterprise Manager and the
Profiler.
FYI, for a KB article on how to Backup Full-Text Catalog Folders and Files,
see 240867 (Q240867) "INF: How to Move, Copy, and Backup Full-Text Catalog
Folders and Files" at
http://support.microsoft.com/default...b;EN-US;240867
Regards,
John
"DC Gringo" <dcgringo@.visiontechnology.net> wrote in message
news:ur3L#n92EHA.3596@.TK2MSFTNGP12.phx.gbl...
> I have a database who's SQL Server backup file has been hovering around
33MB
> and has been growing only a few hundred kilobytes week for a couple years.
> I have since added a catalog and indexed a couple of tables and now this
> database and another one on the server--that should be unrelated--have
> backup files that are 140 and 170MB each. The indexes are really not that
> big. The catalog is only about 20MB.
> First, why would a 20MB catalog increase the size of this database so
much.
> Second, why would a catalog in one database affect one in another (if
that's
> what's really happening)
> Third, how can I do a tally of the database elements that should comprise
> the total so I can find out the true cause of the increase. Counting the
> tables size in K + the indexes does not give me this huge file size.
>
> --
> _____
> DC G
>