Our database is growing very fast. Please help us

Hello all,
We have microsoft sql database abouit 18-19 Gb. After each big calculation
our database grows on 3-5 Gb (mdf-file) sometimes on 25-35Gb but we don't add
anything into database.
Please help us asap.Hi
Do you have any performance problem?
Have you tried using SQL Server Profiler to see what is going on the Server
during the calculation?
Do you backup the LOG file?
"AccessDevelopers" <AccessDevelopers@.discussions.microsoft.com> wrote in
message news:E238FB9F-534D-4569-9B21-1A552FAF2571@.microsoft.com...
> Hello all,
> We have microsoft sql database abouit 18-19 Gb. After each big calculation
> our database grows on 3-5 Gb (mdf-file) sometimes on 25-35Gb but we don't
add
> anything into database.
> Please help us asap.
>|||A database will not grow on its own.
What is a "big calculation"? Index rebuilds can add space to the
transaction log, are you sure it's the data file that is growing and not
the transaction log? Can you run sp_spacedused on every table in the
database to find out where your growth is occurring? You can then query
the tables that are growing the fastest to find out what is happening.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
AccessDevelopers wrote:
> Hello all,
> We have microsoft sql database abouit 18-19 Gb. After each big calculation
> our database grows on 3-5 Gb (mdf-file) sometimes on 25-35Gb but we don't add
> anything into database.
> Please help us asap.
>|||Hi
If it really is your mdf and not the ldf that is growing, I would suspect
that your "big calculation" is causing a lot of fragmentation. A lot of page
splits can cause your database to need a lot more space even though you have
the same amount of data.
Run DBCC SHOWCONTIG (see BOL for details) against your tables to see how
much fragmentation you have. If the fragmentation is high, schedule a time to
perform some index rebuilds on the affected tables.
If this is the case you may want to make index rebuilds a part of the
process that performs your "big calculation". (Make sure it runs after it.
Hope this helps.
John
"Mark Allison" wrote:
> A database will not grow on its own.
> What is a "big calculation"? Index rebuilds can add space to the
> transaction log, are you sure it's the data file that is growing and not
> the transaction log? Can you run sp_spacedused on every table in the
> database to find out where your growth is occurring? You can then query
> the tables that are growing the fastest to find out what is happening.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> AccessDevelopers wrote:
> > Hello all,
> > We have microsoft sql database abouit 18-19 Gb. After each big calculation
> > our database grows on 3-5 Gb (mdf-file) sometimes on 25-35Gb but we don't add
> > anything into database.
> >
> > Please help us asap.
> >
> >
>