Kind of an obscure question, but here goes.
SQL2000 SP4
I have a E: drive on my SQL server that is ~400gb. On it you'll find
a ~100gb live DB file and last night's 100gb .bak file (maintenance
plan is set for one day retention). The vendor is telling me that I
am going to run out of space doing the SQL backups because 100gb is
used by the live DB, 100gb is used by last nights .bak file, 100gb
will be used to write today's .bak file, and the last 100gb will be
used in the deletion process of removing the old .bak file.
I can't say I know how SQL handles the removal of the old .bak file
but is this a true statement that SQL will need equal free space to
delete the old .bak file?SQL deletes old backups AFTER creating new ones, so you will need space for
at least two backups.
Look at it this way, what happens if your database blows up during a backup.
If you have an older backup, you are fine. If you are overwriting your only
backup, it is time to polish up the resume.
Personally, I would go out and buy a couple of USB drives and back up to
there. Last week my mother purchased a 500GB model for $99. If that is not
an option, you could look into one of the commercially available backup
compression tools. The three major ones are SQLSafe (www.idera.com),
LiteSpeed for SQL (www.quest.com), and SQL Backup (www.red-gate.com).
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:04b97215-0ec7-4545-a43b-f072fb3c47a2@.e6g2000prf.googlegroups.com...
> Kind of an obscure question, but here goes.
> SQL2000 SP4
> I have a E: drive on my SQL server that is ~400gb. On it you'll find
> a ~100gb live DB file and last night's 100gb .bak file (maintenance
> plan is set for one day retention). The vendor is telling me that I
> am going to run out of space doing the SQL backups because 100gb is
> used by the live DB, 100gb is used by last nights .bak file, 100gb
> will be used to write today's .bak file, and the last 100gb will be
> used in the deletion process of removing the old .bak file.
> I can't say I know how SQL handles the removal of the old .bak file
> but is this a true statement that SQL will need equal free space to
> delete the old .bak file?|||Right, I aggree. In your scenario I need 300gb, not 400gb as the
vendor claims.
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
--
300gb Total to perform the whole operation
Vendor is saying:
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
100gb - extra needed to delete last nights backup after a successful
backup
--
400gb Total to perform the whole operation
I just don't understand why that extra 100gb is needed.
On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> SQL deletes old backups AFTER creating new ones, so you will need space fo
r
> at least two backups.
> Look at it this way, what happens if your database blows up during a backu
p.
> If you have an older backup, you are fine. If you are overwriting your on
ly
> backup, it is time to polish up the resume.|||Also, a backup on the same disk as the primary is pretty useless when you
think about it.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...[vbcol=seagreen]
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:|||Only if it's not getting written to tape ;)
On Nov 28, 11:28 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Also, a backup on the same disk as the primary is pretty useless when you
> think about it.|||I've never seen Windows needing temp storage in order to delete a file. Perh
aps your vendor somehow
confuses the windows Recycle Bin functionality somehow...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...[vbcol=seagreen]
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
Showing posts with label space. Show all posts
Showing posts with label space. Show all posts
Thursday, March 29, 2012
Equal disk space needed to delete .bak file?
Kind of an obscure question, but here goes.
SQL2000 SP4
I have a E: drive on my SQL server that is ~400gb. On it you'll find
a ~100gb live DB file and last night's 100gb .bak file (maintenance
plan is set for one day retention). The vendor is telling me that I
am going to run out of space doing the SQL backups because 100gb is
used by the live DB, 100gb is used by last nights .bak file, 100gb
will be used to write today's .bak file, and the last 100gb will be
used in the deletion process of removing the old .bak file.
I can't say I know how SQL handles the removal of the old .bak file
but is this a true statement that SQL will need equal free space to
delete the old .bak file?SQL deletes old backups AFTER creating new ones, so you will need space for
at least two backups.
Look at it this way, what happens if your database blows up during a backup.
If you have an older backup, you are fine. If you are overwriting your only
backup, it is time to polish up the resume.
Personally, I would go out and buy a couple of USB drives and back up to
there. Last week my mother purchased a 500GB model for $99. If that is not
an option, you could look into one of the commercially available backup
compression tools. The three major ones are SQLSafe (www.idera.com),
LiteSpeed for SQL (www.quest.com), and SQL Backup (www.red-gate.com).
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:04b97215-0ec7-4545-a43b-f072fb3c47a2@.e6g2000prf.googlegroups.com...
> Kind of an obscure question, but here goes.
> SQL2000 SP4
> I have a E: drive on my SQL server that is ~400gb. On it you'll find
> a ~100gb live DB file and last night's 100gb .bak file (maintenance
> plan is set for one day retention). The vendor is telling me that I
> am going to run out of space doing the SQL backups because 100gb is
> used by the live DB, 100gb is used by last nights .bak file, 100gb
> will be used to write today's .bak file, and the last 100gb will be
> used in the deletion process of removing the old .bak file.
> I can't say I know how SQL handles the removal of the old .bak file
> but is this a true statement that SQL will need equal free space to
> delete the old .bak file?|||Right, I aggree. In your scenario I need 300gb, not 400gb as the
vendor claims.
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
--
300gb Total to perform the whole operation
Vendor is saying:
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
100gb - extra needed to delete last nights backup after a successful
backup
--
400gb Total to perform the whole operation
I just don't understand why that extra 100gb is needed.
On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> SQL deletes old backups AFTER creating new ones, so you will need space for
> at least two backups.
> Look at it this way, what happens if your database blows up during a backup.
> If you have an older backup, you are fine. If you are overwriting your only
> backup, it is time to polish up the resume.|||Also, a backup on the same disk as the primary is pretty useless when you
think about it.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>> SQL deletes old backups AFTER creating new ones, so you will need space
>> for
>> at least two backups.
>> Look at it this way, what happens if your database blows up during a
>> backup.
>> If you have an older backup, you are fine. If you are overwriting your
>> only
>> backup, it is time to polish up the resume.|||Only if it's not getting written to tape ;)
On Nov 28, 11:28 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Also, a backup on the same disk as the primary is pretty useless when you
> think about it.|||I've never seen Windows needing temp storage in order to delete a file. Perhaps your vendor somehow
confuses the windows Recycle Bin functionality somehow...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>> SQL deletes old backups AFTER creating new ones, so you will need space for
>> at least two backups.
>> Look at it this way, what happens if your database blows up during a backup.
>> If you have an older backup, you are fine. If you are overwriting your only
>> backup, it is time to polish up the resume.sql
SQL2000 SP4
I have a E: drive on my SQL server that is ~400gb. On it you'll find
a ~100gb live DB file and last night's 100gb .bak file (maintenance
plan is set for one day retention). The vendor is telling me that I
am going to run out of space doing the SQL backups because 100gb is
used by the live DB, 100gb is used by last nights .bak file, 100gb
will be used to write today's .bak file, and the last 100gb will be
used in the deletion process of removing the old .bak file.
I can't say I know how SQL handles the removal of the old .bak file
but is this a true statement that SQL will need equal free space to
delete the old .bak file?SQL deletes old backups AFTER creating new ones, so you will need space for
at least two backups.
Look at it this way, what happens if your database blows up during a backup.
If you have an older backup, you are fine. If you are overwriting your only
backup, it is time to polish up the resume.
Personally, I would go out and buy a couple of USB drives and back up to
there. Last week my mother purchased a 500GB model for $99. If that is not
an option, you could look into one of the commercially available backup
compression tools. The three major ones are SQLSafe (www.idera.com),
LiteSpeed for SQL (www.quest.com), and SQL Backup (www.red-gate.com).
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:04b97215-0ec7-4545-a43b-f072fb3c47a2@.e6g2000prf.googlegroups.com...
> Kind of an obscure question, but here goes.
> SQL2000 SP4
> I have a E: drive on my SQL server that is ~400gb. On it you'll find
> a ~100gb live DB file and last night's 100gb .bak file (maintenance
> plan is set for one day retention). The vendor is telling me that I
> am going to run out of space doing the SQL backups because 100gb is
> used by the live DB, 100gb is used by last nights .bak file, 100gb
> will be used to write today's .bak file, and the last 100gb will be
> used in the deletion process of removing the old .bak file.
> I can't say I know how SQL handles the removal of the old .bak file
> but is this a true statement that SQL will need equal free space to
> delete the old .bak file?|||Right, I aggree. In your scenario I need 300gb, not 400gb as the
vendor claims.
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
--
300gb Total to perform the whole operation
Vendor is saying:
100gb - live DB
100gb - last nights backup
100gb - to create tonights backup
100gb - extra needed to delete last nights backup after a successful
backup
--
400gb Total to perform the whole operation
I just don't understand why that extra 100gb is needed.
On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> SQL deletes old backups AFTER creating new ones, so you will need space for
> at least two backups.
> Look at it this way, what happens if your database blows up during a backup.
> If you have an older backup, you are fine. If you are overwriting your only
> backup, it is time to polish up the resume.|||Also, a backup on the same disk as the primary is pretty useless when you
think about it.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>> SQL deletes old backups AFTER creating new ones, so you will need space
>> for
>> at least two backups.
>> Look at it this way, what happens if your database blows up during a
>> backup.
>> If you have an older backup, you are fine. If you are overwriting your
>> only
>> backup, it is time to polish up the resume.|||Only if it's not getting written to tape ;)
On Nov 28, 11:28 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Also, a backup on the same disk as the primary is pretty useless when you
> think about it.|||I've never seen Windows needing temp storage in order to delete a file. Perhaps your vendor somehow
confuses the windows Recycle Bin functionality somehow...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<rockemhard@.gmail.com> wrote in message
news:b1987afa-2fde-4bcc-9e25-4d2632f7c009@.j44g2000hsj.googlegroups.com...
> Right, I aggree. In your scenario I need 300gb, not 400gb as the
> vendor claims.
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> --
> 300gb Total to perform the whole operation
>
> Vendor is saying:
> 100gb - live DB
> 100gb - last nights backup
> 100gb - to create tonights backup
> 100gb - extra needed to delete last nights backup after a successful
> backup
> --
> 400gb Total to perform the whole operation
> I just don't understand why that extra 100gb is needed.
> On Nov 28, 10:46 am, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
>> SQL deletes old backups AFTER creating new ones, so you will need space for
>> at least two backups.
>> Look at it this way, what happens if your database blows up during a backup.
>> If you have an older backup, you are fine. If you are overwriting your only
>> backup, it is time to polish up the resume.sql
Monday, March 19, 2012
Enterprise manager reporting Free Space
I 'm running sql server 2k, with service pak3a, Win2k with lastest service
pak. We have a database that shows as being 9gig, with 0.00 MB free when
looking at the properties of it in Enterprise manager. The hdisk where that
database resides has 45gig free, with no disk quotes. Also, the database is
set to auto grow by 10%, both the tran log and data file. I have no idea why
it's not seeing more the 0.00mb free...any thoughts or ideas would be
greatly appreciated..
-Bob
That reports the space free in the MDF file, not on the drive.
http://www.aspfaq.com/
(Reverse address to reply.)
"BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
news:BEAF570A-FE36-4BCA-8B16-A980D0621926@.microsoft.com...
> I 'm running sql server 2k, with service pak3a, Win2k with lastest service
> pak. We have a database that shows as being 9gig, with 0.00 MB free when
> looking at the properties of it in Enterprise manager. The hdisk where
that
> database resides has 45gig free, with no disk quotes. Also, the database
is
> set to auto grow by 10%, both the tran log and data file. I have no idea
why
> it's not seeing more the 0.00mb free...any thoughts or ideas would be
> greatly appreciated..
> -Bob
|||how can I increase that space...do i need to?
"Aaron [SQL Server MVP]" wrote:
> That reports the space free in the MDF file, not on the drive.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
> news:BEAF570A-FE36-4BCA-8B16-A980D0621926@.microsoft.com...
> that
> is
> why
>
>
|||If you have it set to autogrow, it will increase the space when it needs to.
http://www.aspfaq.com/
(Reverse address to reply.)
"BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
news:8C9B48B3-4737-4A2C-A21F-A7A9095154DC@.microsoft.com...[vbcol=seagreen]
> how can I increase that space...do i need to?
> "Aaron [SQL Server MVP]" wrote:
service[vbcol=seagreen]
when[vbcol=seagreen]
database[vbcol=seagreen]
idea[vbcol=seagreen]
pak. We have a database that shows as being 9gig, with 0.00 MB free when
looking at the properties of it in Enterprise manager. The hdisk where that
database resides has 45gig free, with no disk quotes. Also, the database is
set to auto grow by 10%, both the tran log and data file. I have no idea why
it's not seeing more the 0.00mb free...any thoughts or ideas would be
greatly appreciated..
-Bob
That reports the space free in the MDF file, not on the drive.
http://www.aspfaq.com/
(Reverse address to reply.)
"BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
news:BEAF570A-FE36-4BCA-8B16-A980D0621926@.microsoft.com...
> I 'm running sql server 2k, with service pak3a, Win2k with lastest service
> pak. We have a database that shows as being 9gig, with 0.00 MB free when
> looking at the properties of it in Enterprise manager. The hdisk where
that
> database resides has 45gig free, with no disk quotes. Also, the database
is
> set to auto grow by 10%, both the tran log and data file. I have no idea
why
> it's not seeing more the 0.00mb free...any thoughts or ideas would be
> greatly appreciated..
> -Bob
|||how can I increase that space...do i need to?
"Aaron [SQL Server MVP]" wrote:
> That reports the space free in the MDF file, not on the drive.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
> news:BEAF570A-FE36-4BCA-8B16-A980D0621926@.microsoft.com...
> that
> is
> why
>
>
|||If you have it set to autogrow, it will increase the space when it needs to.
http://www.aspfaq.com/
(Reverse address to reply.)
"BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
news:8C9B48B3-4737-4A2C-A21F-A7A9095154DC@.microsoft.com...[vbcol=seagreen]
> how can I increase that space...do i need to?
> "Aaron [SQL Server MVP]" wrote:
service[vbcol=seagreen]
when[vbcol=seagreen]
database[vbcol=seagreen]
idea[vbcol=seagreen]
Enterprise manager reporting Free Space
I 'm running sql server 2k, with service pak3a, Win2k with lastest service
pak. We have a database that shows as being 9gig, with 0.00 MB free when
looking at the properties of it in Enterprise manager. The hdisk where that
database resides has 45gig free, with no disk quotes. Also, the database is
set to auto grow by 10%, both the tran log and data file. I have no idea why
it's not seeing more the 0.00mb free...any thoughts or ideas would be
greatly appreciated..
-BobThat reports the space free in the MDF file, not on the drive.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
news:BEAF570A-FE36-4BCA-8B16-A980D0621926@.microsoft.com...
> I 'm running sql server 2k, with service pak3a, Win2k with lastest service
> pak. We have a database that shows as being 9gig, with 0.00 MB free when
> looking at the properties of it in Enterprise manager. The hdisk where
that
> database resides has 45gig free, with no disk quotes. Also, the database
is
> set to auto grow by 10%, both the tran log and data file. I have no idea
why
> it's not seeing more the 0.00mb free...any thoughts or ideas would be
> greatly appreciated..
> -Bob|||how can I increase that space...do i need to?
"Aaron [SQL Server MVP]" wrote:
> That reports the space free in the MDF file, not on the drive.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
> news:BEAF570A-FE36-4BCA-8B16-A980D0621926@.microsoft.com...
> > I 'm running sql server 2k, with service pak3a, Win2k with lastest service
> > pak. We have a database that shows as being 9gig, with 0.00 MB free when
> > looking at the properties of it in Enterprise manager. The hdisk where
> that
> > database resides has 45gig free, with no disk quotes. Also, the database
> is
> > set to auto grow by 10%, both the tran log and data file. I have no idea
> why
> > it's not seeing more the 0.00mb free...any thoughts or ideas would be
> > greatly appreciated..
> >
> > -Bob
>
>|||If you have it set to autogrow, it will increase the space when it needs to.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
news:8C9B48B3-4737-4A2C-A21F-A7A9095154DC@.microsoft.com...
> how can I increase that space...do i need to?
> "Aaron [SQL Server MVP]" wrote:
> > That reports the space free in the MDF file, not on the drive.
> >
> > --
> > http://www.aspfaq.com/
> > (Reverse address to reply.)
> >
> >
> >
> >
> > "BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
> > news:BEAF570A-FE36-4BCA-8B16-A980D0621926@.microsoft.com...
> > > I 'm running sql server 2k, with service pak3a, Win2k with lastest
service
> > > pak. We have a database that shows as being 9gig, with 0.00 MB free
when
> > > looking at the properties of it in Enterprise manager. The hdisk where
> > that
> > > database resides has 45gig free, with no disk quotes. Also, the
database
> > is
> > > set to auto grow by 10%, both the tran log and data file. I have no
idea
> > why
> > > it's not seeing more the 0.00mb free...any thoughts or ideas would be
> > > greatly appreciated..
> > >
> > > -Bob
> >
> >
> >
pak. We have a database that shows as being 9gig, with 0.00 MB free when
looking at the properties of it in Enterprise manager. The hdisk where that
database resides has 45gig free, with no disk quotes. Also, the database is
set to auto grow by 10%, both the tran log and data file. I have no idea why
it's not seeing more the 0.00mb free...any thoughts or ideas would be
greatly appreciated..
-BobThat reports the space free in the MDF file, not on the drive.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
news:BEAF570A-FE36-4BCA-8B16-A980D0621926@.microsoft.com...
> I 'm running sql server 2k, with service pak3a, Win2k with lastest service
> pak. We have a database that shows as being 9gig, with 0.00 MB free when
> looking at the properties of it in Enterprise manager. The hdisk where
that
> database resides has 45gig free, with no disk quotes. Also, the database
is
> set to auto grow by 10%, both the tran log and data file. I have no idea
why
> it's not seeing more the 0.00mb free...any thoughts or ideas would be
> greatly appreciated..
> -Bob|||how can I increase that space...do i need to?
"Aaron [SQL Server MVP]" wrote:
> That reports the space free in the MDF file, not on the drive.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
> news:BEAF570A-FE36-4BCA-8B16-A980D0621926@.microsoft.com...
> > I 'm running sql server 2k, with service pak3a, Win2k with lastest service
> > pak. We have a database that shows as being 9gig, with 0.00 MB free when
> > looking at the properties of it in Enterprise manager. The hdisk where
> that
> > database resides has 45gig free, with no disk quotes. Also, the database
> is
> > set to auto grow by 10%, both the tran log and data file. I have no idea
> why
> > it's not seeing more the 0.00mb free...any thoughts or ideas would be
> > greatly appreciated..
> >
> > -Bob
>
>|||If you have it set to autogrow, it will increase the space when it needs to.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
news:8C9B48B3-4737-4A2C-A21F-A7A9095154DC@.microsoft.com...
> how can I increase that space...do i need to?
> "Aaron [SQL Server MVP]" wrote:
> > That reports the space free in the MDF file, not on the drive.
> >
> > --
> > http://www.aspfaq.com/
> > (Reverse address to reply.)
> >
> >
> >
> >
> > "BobJones1967" <BobJones1967@.discussions.microsoft.com> wrote in message
> > news:BEAF570A-FE36-4BCA-8B16-A980D0621926@.microsoft.com...
> > > I 'm running sql server 2k, with service pak3a, Win2k with lastest
service
> > > pak. We have a database that shows as being 9gig, with 0.00 MB free
when
> > > looking at the properties of it in Enterprise manager. The hdisk where
> > that
> > > database resides has 45gig free, with no disk quotes. Also, the
database
> > is
> > > set to auto grow by 10%, both the tran log and data file. I have no
idea
> > why
> > > it's not seeing more the 0.00mb free...any thoughts or ideas would be
> > > greatly appreciated..
> > >
> > > -Bob
> >
> >
> >
Friday, February 17, 2012
Enterprise Manager
Hi All,
When I view the database properties using Enterprise Manager, some of the databases on the server are reporting that there is zero space available while others have space available. Does anybody know why?in the database properties section go to the data files tab...over there in the location column check out what are the options available...if you say restrict file growth and if the database is full the space available will be zero.....also check whether there is any space available on the drive where the mdf file is created...might be the case that the drive is full...|||I've checked the options in the Database Properties and the option selected is unrestricted file growth. Also, the disk have enough space available on the drive where the mdf file is created. What else can it be?
When I view the database properties using Enterprise Manager, some of the databases on the server are reporting that there is zero space available while others have space available. Does anybody know why?in the database properties section go to the data files tab...over there in the location column check out what are the options available...if you say restrict file growth and if the database is full the space available will be zero.....also check whether there is any space available on the drive where the mdf file is created...might be the case that the drive is full...|||I've checked the options in the Database Properties and the option selected is unrestricted file growth. Also, the disk have enough space available on the drive where the mdf file is created. What else can it be?
Subscribe to:
Posts (Atom)