Hello ,Folks
SQL Server 2000 (sp3)
I have posted this question yesterday and still have not got an idea why it
is happening.
I have a database 11GB and every night I do a full backup (WITH INIT) of
the database that .BAK file was always around 11 GB as well
Two days ago it finnished (backup operation) with 16GB .bak file. The
.MDF,.LDF files have not grown since.
The question is WHY is my .BAK file grew so much? What could be a
reason?
ThanksHi Alex
From the sp_spaceused information you figures don't correspond
database_name database_size unallocated space
-- -- --
dbname 28511.69 MB 519.01 MB
reserved data index_size unused
-- -- -- --
23568632 KB 6408816 KB 6066240 KB 11093576 KB
This says your database is 27GB and there is 10GB unused space, so 16GB for
a backup seems reasonable.
John
"Alex" wrote:
> Hello ,Folks
> SQL Server 2000 (sp3)
> I have posted this question yesterday and still have not got an idea why
it
> is happening.
> I have a database 11GB and every night I do a full backup (WITH INIT) of
> the database that .BAK file was always around 11 GB as well
> Two days ago it finnished (backup operation) with 16GB .bak file. The
> ..MDF,.LDF files have not grown since.
> The question is WHY is my .BAK file grew so much? What could be a
> reason?
> Thanks
>
>|||John
Yes , you are right, the database contains three files , however , it has
been all time that the .BAK file was 11GB , so what happened at night to
grow to 16GB?
Thanks
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:0D7D6906-B6E8-47DD-AED0-21F101C1571C@.microsoft.com...[vbcol=seagreen]
> Hi Alex
> From the sp_spaceused information you figures don't correspond
> database_name database_size unallocated space
> -- -- --
> dbname 28511.69 MB 519.01 MB
> reserved data index_size unused
> -- -- -- --
> 23568632 KB 6408816 KB 6066240 KB 11093576 KB
>
> This says your database is 27GB and there is 10GB unused space, so 16GB
> for
> a backup seems reasonable.
> John
> "Alex" wrote:
>|||Hi Alex
The simple answer would be that there is more information in the file!
Unless you are archiving data from your database then you would expect a
steady growth. A 4GB increment would indicate something abnormal has
happened, such as someone copyied a large table. To find out space used by
each table you could run something like:
CREATE TABLE #spaceused ( name nvarchar(128),
rows char(11),
reserved varchar(18),
data varchar(18),
index_size varchar(18),
unused varchar(18),
reservedK AS CAST(LEFT(reserved,charindex(' ', reserved)-1) AS BIGINT) )
EXEC sp_msforeachtable 'INSERT INTO #spaceused ( name, rows, reserved, data,
index_size, unused ) EXEC sp_spaceused [?]'
SELECT * FROM #spaceused
ORDER BY reservedK DESC
DROP TABLE #spaceused
John
"Alex" wrote:
> John
> Yes , you are right, the database contains three files , however , it has
> been all time that the .BAK file was 11GB , so what happened at night to
> grow to 16GB?
> Thanks
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:0D7D6906-B6E8-47DD-AED0-21F101C1571C@.microsoft.com...
>
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment