Hello:
I am having a problem with a production database that has
run out of space. The database was configured by the
sofware manufacturer with 269mb of allocated space. The
current size is 450mb with 0% free space available. The
database has the Autogrow option turned on and is set for
Unrestricted file growth. There are 48GB of free space
available on the physical disk on which the database
resides. None of my users have reported any problems so
far.
I have a monitoring tool that is throwing up an alarm
because of this problem. I have shrank the database
several times, indicating that I want to have 10% free
space available after shrinking. Whenever I check the
database properties however, the sizes remain the same.
How can I correct this issue before it becomes a real
problem.
Thanks for any assistance
BrennanThis is a multi-part message in MIME format.
--=_NextPart_000_0427_01C3CE18.E52CA0B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Well, 48GB is just about 10% of 450GB. I would start looking for more disk
space, unless you can actually purge data out of your database.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Brennan" <anonymous@.discussions.microsoft.com> wrote in message
news:00e101c3ce41$563d7450$a501280a@.phx.gbl...
Hello:
I am having a problem with a production database that has
run out of space. The database was configured by the
sofware manufacturer with 269mb of allocated space. The
current size is 450mb with 0% free space available. The
database has the Autogrow option turned on and is set for
Unrestricted file growth. There are 48GB of free space
available on the physical disk on which the database
resides. None of my users have reported any problems so
far.
I have a monitoring tool that is throwing up an alarm
because of this problem. I have shrank the database
several times, indicating that I want to have 10% free
space available after shrinking. Whenever I check the
database properties however, the sizes remain the same.
How can I correct this issue before it becomes a real
problem.
Thanks for any assistance
Brennan
--=_NextPart_000_0427_01C3CE18.E52CA0B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Well, 48GB is just about 10% of =450GB. I would start looking for more disk space, unless you can actually =purge data out of your database.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"Brennan" wrote in message news:00e101c3ce41$56=3d7450$a501280a@.phx.gbl...Hello:I am having a problem with a production database that has run out of space. The database was configured by the sofware manufacturer =with 269mb of allocated space. The current size is 450mb with 0% =free space available. The database has the Autogrow option turned on and =is set for Unrestricted file growth. There are 48GB of free space =available on the physical disk on which the database resides. None of my =users have reported any problems so far.I have a monitoring tool that =is throwing up an alarm because of this problem. I have shrank =the database several times, indicating that I want to have 10% free =space available after shrinking. Whenever I check the database =properties however, the sizes remain the same.How can I correct this issue =before it becomes a real problem.Thanks for any assistanceBrennan
--=_NextPart_000_0427_01C3CE18.E52CA0B0--|||Hi Tom:
The DB is 450MB not 450GB. I have plenty of space
available on the volume. Total size is 90+GB and 48GB
are free.
Am I missing something?
Brennan
>--Original Message--
>Well, 48GB is just about 10% of 450GB. I would start
looking for more disk
>space, unless you can actually purge data out of your
database.
>--
>Tom
>----
--
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com/sql
>
>"Brennan" <anonymous@.discussions.microsoft.com> wrote in
message
>news:00e101c3ce41$563d7450$a501280a@.phx.gbl...
>Hello:
>I am having a problem with a production database that has
>run out of space. The database was configured by the
>sofware manufacturer with 269mb of allocated space. The
>current size is 450mb with 0% free space available. The
>database has the Autogrow option turned on and is set for
>Unrestricted file growth. There are 48GB of free space
>available on the physical disk on which the database
>resides. None of my users have reported any problems so
>far.
>I have a monitoring tool that is throwing up an alarm
>because of this problem. I have shrank the database
>several times, indicating that I want to have 10% free
>space available after shrinking. Whenever I check the
>database properties however, the sizes remain the same.
>How can I correct this issue before it becomes a real
>problem.
>Thanks for any assistance
>Brennan
>
>|||This is a multi-part message in MIME format.
--=_NextPart_000_04D6_01C3CE1E.D1605D00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Oops, sorry about that. It looks then that you will soon reach a point
where if someone goes to add data, it will have to autogrow. All pending
inserts - and maybe some updates - will have to wait until that happens.
I'd just expand the database by, say, 100 MB, so that the users wouldn't
have to wait for the autogrow to complete.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
<anonymous@.discussions.microsoft.com> wrote in message
news:010101c3ce47$61893e10$a601280a@.phx.gbl...
Hi Tom:
The DB is 450MB not 450GB. I have plenty of space
available on the volume. Total size is 90+GB and 48GB
are free.
Am I missing something?
Brennan
>--Original Message--
>Well, 48GB is just about 10% of 450GB. I would start
looking for more disk
>space, unless you can actually purge data out of your
database.
>--
>Tom
>----
--
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com/sql
>
>"Brennan" <anonymous@.discussions.microsoft.com> wrote in
message
>news:00e101c3ce41$563d7450$a501280a@.phx.gbl...
>Hello:
>I am having a problem with a production database that has
>run out of space. The database was configured by the
>sofware manufacturer with 269mb of allocated space. The
>current size is 450mb with 0% free space available. The
>database has the Autogrow option turned on and is set for
>Unrestricted file growth. There are 48GB of free space
>available on the physical disk on which the database
>resides. None of my users have reported any problems so
>far.
>I have a monitoring tool that is throwing up an alarm
>because of this problem. I have shrank the database
>several times, indicating that I want to have 10% free
>space available after shrinking. Whenever I check the
>database properties however, the sizes remain the same.
>How can I correct this issue before it becomes a real
>problem.
>Thanks for any assistance
>Brennan
>
>
--=_NextPart_000_04D6_01C3CE1E.D1605D00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#d4d0c8>
<DIV><FONT face=3DTahoma size=3D2>Oops, sorry about that. It looks =then that you will soon reach a point where if someone goes to add data, it will =have to autogrow. All pending inserts - and maybe some updates - will have =to wait until that happens. I'd just expand the database by, say, 100 MB, =so that the users wouldn't have to wait for the autogrow to =complete.</FONT></DIV>
<DIV><BR>-- <BR>Tom</DIV>
<DIV> </DIV>
<DIV>---<BR>T=homas A. Moreau, BSc, PhD, MCSE, MCDBA<BR>SQL Server MVP<BR>Columnist, SQL =Server Professional<BR>Toronto, ON Canada<BR><A href=3D"www.pinnaclepublishing.com=">http://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=
/sql</A></DIV>
<DIV><FONT face=3DTahoma size=3D2></FONT> </DIV>
<DIV> </DIV>
<DIV><<A href=3D"mailto:anonymous@.discussions.microsoft.com">anonymous@.discussions=.microsoft.com</A>> wrote in message <A href=3D"news:010101c3ce47$61893e10$a601280a@.phx.gbl">news:010101c3ce47$61=893e10$a601280a@.phx.gbl</A>...</DIV>Hi Tom:<BR><BR>The DB is 450MB not 450GB. I have plenty of =space <BR>available on the volume. Total size is 90+GB and 48GB <BR>are free.<BR><BR>Am I missing =something?<BR><BR>Brennan<BR><BR><BR>>--Original Message--<BR>>Well, 48GB is just about 10% of 450GB. I would =
start <BR>looking for more disk<BR>>space, unless you can =actually purge data out of your <BR>database.<BR>><BR>>--<BR>>Tom<BR>><BR>>--=---<BR>--<BR>>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA<BR>>SQL Server MVP<BR>>Columnist, =SQL Server Professional<BR>>Toronto, ON Canada<BR>>www.pinnaclepublishing.com/sql<BR>><BR>><BR>>"Bren=nan" <<A href=3D"mailto:anonymous@.discussions.microsoft.com">anonymous@.discussions=.microsoft.com</A>> wrote in <BR>message<BR>>news:00e101c3ce41$563d7450$a501280a@.phx.gbl...<BR>>=Hello:<BR>><BR>>I am having a problem with a production database that has<BR>>run out =of space. The database was configured by the<BR>>sofware =manufacturer with 269mb of allocated space. The<BR>>current size is 450mb with 0% =free space available. The<BR>>database has the Autogrow option =turned on and is set for<BR>>Unrestricted file growth. There are 48GB of free space<BR>>available on the physical disk on which the database<BR>>resides. None of my users have reported any =problems so<BR>>far.<BR>><BR>>I have a monitoring tool that is throwing =up an alarm<BR>>because of this problem. I have shrank the database<BR>>several times, indicating that I want to have 10% free<BR>>space available after shrinking. Whenever I check the<BR>>database properties however, the sizes remain the same.<BR>><BR>>How can I correct this issue before it becomes a real<BR>>problem.<BR>><BR>>Thanks for any assistance<BR>><BR>>Brennan<BR>><BR>><BR>><BR>></BODY><=/HTML>
--=_NextPart_000_04D6_01C3CE1E.D1605D00--
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment