Hello,
I've configured SQL Server 2005 express to use autogrowth by 5mb.
After a few weeks the autogrowth option automatically switched to 640
percent what will lead to performance problems.
After is set back the autogrowth to 5mb, a few weeks later the same
problem occurs.
Does anyone know what can cause this problem?
Thanks in advance,
PimWhich servicepack is installed?
You can disable autogrow and set the database size manually as temporarly
workaround.
greetz
"Pim75" wrote:
> Hello,
> I've configured SQL Server 2005 express to use autogrowth by 5mb.
> After a few weeks the autogrowth option automatically switched to 640
> percent what will lead to performance problems.
> After is set back the autogrowth to 5mb, a few weeks later the same
> problem occurs.
> Does anyone know what can cause this problem?
> Thanks in advance,
> Pim
>|||hi
make sure no one else is playing with the server
Regards
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"Pim75" <p.megens@.tiscali.nl> wrote in message
news:1181732495.637264.178440@.d30g2000prg.googlegroups.com...
> Hello,
> I've configured SQL Server 2005 express to use autogrowth by 5mb.
> After a few weeks the autogrowth option automatically switched to 640
> percent what will lead to performance problems.
> After is set back the autogrowth to 5mb, a few weeks later the same
> problem occurs.
> Does anyone know what can cause this problem?
> Thanks in advance,
> Pim
>|||We use Microsoft SQL Server Express Edition, version 9.00.1399.06
Windows 2003 webserver edition, servicepack 1.
We have some more servers but this is the only one where the problem
occurs.
On 13 jun, 13:37, Hate_orphaned_users
<Hateorphanedus...@.discussions.microsoft.com> wrote:
> Which servicepack is installed?
> You can disable autogrow and set the database size manually as temporarly
> workaround.
> greetz
>
> "Pim75" wrote:
> > Hello,
> > I've configured SQL Server 2005 express to use autogrowth by 5mb.
> > After a few weeks the autogrowth option automatically switched to 640
> > percent what will lead to performance problems.
> > After is set back the autogrowth to 5mb, a few weeks later the same
> > problem occurs.
> > Does anyone know what can cause this problem?
> > Thanks in advance,
> > Pim- Tekst uit oorspronkelijk bericht niet weergeven -
> - Tekst uit oorspronkelijk bericht weergeven -|||Pim75 wrote:
> Hello,
> I've configured SQL Server 2005 express to use autogrowth by 5mb.
> After a few weeks the autogrowth option automatically switched to 640
> percent what will lead to performance problems.
> After is set back the autogrowth to 5mb, a few weeks later the same
> problem occurs.
> Does anyone know what can cause this problem?
> Thanks in advance,
> Pim
>
Hi
Not that it helps you a lot, but we see the same thing happening on one
specific database. Occasionally the mdf file for this database is being
set to a growth rate of 12800% and then the file is around 258 GB.
This has started after we moved this database from a SQL2000 server to a
SQL2005 server. The vendor knows about the issue and they has the same
problem with a few other customers. Since it happens quite seldom, they
haven't been able to figure out what it is that causes it to happen. As
a temporary workaround, I'v written a little sql script that runs every
15 minuttes to check the filesize and filegrowth. If one of them has
changed since last run it sends me an email. I can then go in an correct
the values.
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||Personally I would just set the job to issue the necessary ALTER DATABASE
statement to fix the growth increment when identified (as well as send an
email that it had been done).
Also, I didn't investigate, but it may be possible to use a DDL trigger to
trap ALTER DATABASE calls on this database to 1) prevent the growth factor
change and 2) identify the offending code and get it fixed.
--
TheSQLGuru
President
Indicium Resources, Inc.
""Steen Schlüter Persson (DK)"" <steen@.REMOVE_THIS_asavaenget.dk> wrote in
message news:%23lpkSXbrHHA.1296@.TK2MSFTNGP06.phx.gbl...
> Pim75 wrote:
>> Hello,
>> I've configured SQL Server 2005 express to use autogrowth by 5mb.
>> After a few weeks the autogrowth option automatically switched to 640
>> percent what will lead to performance problems.
>> After is set back the autogrowth to 5mb, a few weeks later the same
>> problem occurs.
>> Does anyone know what can cause this problem?
>> Thanks in advance,
>> Pim
> Hi
> Not that it helps you a lot, but we see the same thing happening on one
> specific database. Occasionally the mdf file for this database is being
> set to a growth rate of 12800% and then the file is around 258 GB.
> This has started after we moved this database from a SQL2000 server to a
> SQL2005 server. The vendor knows about the issue and they has the same
> problem with a few other customers. Since it happens quite seldom, they
> haven't been able to figure out what it is that causes it to happen. As a
> temporary workaround, I'v written a little sql script that runs every 15
> minuttes to check the filesize and filegrowth. If one of them has changed
> since last run it sends me an email. I can then go in an correct the
> values.
>
> --
> Regards
> Steen Schlüter Persson
> Database Administrator / System Administrator
Showing posts with label percent. Show all posts
Showing posts with label percent. Show all posts
Saturday, February 25, 2012
Autogrowth automatically set to 640 percent
Hello,
I've configured SQL Server 2005 express to use autogrowth by 5mb.
After a few weeks the autogrowth option automatically switched to 640
percent what will lead to performance problems.
After is set back the autogrowth to 5mb, a few weeks later the same
problem occurs.
Does anyone know what can cause this problem?
Thanks in advance,
Pim
Which servicepack is installed?
You can disable autogrow and set the database size manually as temporarly
workaround.
greetz
"Pim75" wrote:
> Hello,
> I've configured SQL Server 2005 express to use autogrowth by 5mb.
> After a few weeks the autogrowth option automatically switched to 640
> percent what will lead to performance problems.
> After is set back the autogrowth to 5mb, a few weeks later the same
> problem occurs.
> Does anyone know what can cause this problem?
> Thanks in advance,
> Pim
>
|||We use Microsoft SQL Server Express Edition, version 9.00.1399.06
Windows 2003 webserver edition, servicepack 1.
We have some more servers but this is the only one where the problem
occurs.
On 13 jun, 13:37, Hate_orphaned_users
<Hateorphanedus...@.discussions.microsoft.com> wrote:
> Which servicepack is installed?
> You can disable autogrow and set the database size manually as temporarly
> workaround.
> greetz
>
> "Pim75" wrote:
>
>
> - Tekst uit oorspronkelijk bericht weergeven -
|||Pim75 wrote:
> Hello,
> I've configured SQL Server 2005 express to use autogrowth by 5mb.
> After a few weeks the autogrowth option automatically switched to 640
> percent what will lead to performance problems.
> After is set back the autogrowth to 5mb, a few weeks later the same
> problem occurs.
> Does anyone know what can cause this problem?
> Thanks in advance,
> Pim
>
Hi
Not that it helps you a lot, but we see the same thing happening on one
specific database. Occasionally the mdf file for this database is being
set to a growth rate of 12800% and then the file is around 258 GB.
This has started after we moved this database from a SQL2000 server to a
SQL2005 server. The vendor knows about the issue and they has the same
problem with a few other customers. Since it happens quite seldom, they
haven't been able to figure out what it is that causes it to happen. As
a temporary workaround, I'v written a little sql script that runs every
15 minuttes to check the filesize and filegrowth. If one of them has
changed since last run it sends me an email. I can then go in an correct
the values.
Regards
Steen Schlter Persson
Database Administrator / System Administrator
|||Personally I would just set the job to issue the necessary ALTER DATABASE
statement to fix the growth increment when identified (as well as send an
email that it had been done).
Also, I didn't investigate, but it may be possible to use a DDL trigger to
trap ALTER DATABASE calls on this database to 1) prevent the growth factor
change and 2) identify the offending code and get it fixed.
TheSQLGuru
President
Indicium Resources, Inc.
""Steen Schlter Persson (DK)"" <steen@.REMOVE_THIS_asavaenget.dk> wrote in
message news:%23lpkSXbrHHA.1296@.TK2MSFTNGP06.phx.gbl...
> Pim75 wrote:
> Hi
> Not that it helps you a lot, but we see the same thing happening on one
> specific database. Occasionally the mdf file for this database is being
> set to a growth rate of 12800% and then the file is around 258 GB.
> This has started after we moved this database from a SQL2000 server to a
> SQL2005 server. The vendor knows about the issue and they has the same
> problem with a few other customers. Since it happens quite seldom, they
> haven't been able to figure out what it is that causes it to happen. As a
> temporary workaround, I'v written a little sql script that runs every 15
> minuttes to check the filesize and filegrowth. If one of them has changed
> since last run it sends me an email. I can then go in an correct the
> values.
>
> --
> Regards
> Steen Schlter Persson
> Database Administrator / System Administrator
I've configured SQL Server 2005 express to use autogrowth by 5mb.
After a few weeks the autogrowth option automatically switched to 640
percent what will lead to performance problems.
After is set back the autogrowth to 5mb, a few weeks later the same
problem occurs.
Does anyone know what can cause this problem?
Thanks in advance,
Pim
Which servicepack is installed?
You can disable autogrow and set the database size manually as temporarly
workaround.
greetz
"Pim75" wrote:
> Hello,
> I've configured SQL Server 2005 express to use autogrowth by 5mb.
> After a few weeks the autogrowth option automatically switched to 640
> percent what will lead to performance problems.
> After is set back the autogrowth to 5mb, a few weeks later the same
> problem occurs.
> Does anyone know what can cause this problem?
> Thanks in advance,
> Pim
>
|||We use Microsoft SQL Server Express Edition, version 9.00.1399.06
Windows 2003 webserver edition, servicepack 1.
We have some more servers but this is the only one where the problem
occurs.
On 13 jun, 13:37, Hate_orphaned_users
<Hateorphanedus...@.discussions.microsoft.com> wrote:
> Which servicepack is installed?
> You can disable autogrow and set the database size manually as temporarly
> workaround.
> greetz
>
> "Pim75" wrote:
>
>
> - Tekst uit oorspronkelijk bericht weergeven -
|||Pim75 wrote:
> Hello,
> I've configured SQL Server 2005 express to use autogrowth by 5mb.
> After a few weeks the autogrowth option automatically switched to 640
> percent what will lead to performance problems.
> After is set back the autogrowth to 5mb, a few weeks later the same
> problem occurs.
> Does anyone know what can cause this problem?
> Thanks in advance,
> Pim
>
Hi
Not that it helps you a lot, but we see the same thing happening on one
specific database. Occasionally the mdf file for this database is being
set to a growth rate of 12800% and then the file is around 258 GB.
This has started after we moved this database from a SQL2000 server to a
SQL2005 server. The vendor knows about the issue and they has the same
problem with a few other customers. Since it happens quite seldom, they
haven't been able to figure out what it is that causes it to happen. As
a temporary workaround, I'v written a little sql script that runs every
15 minuttes to check the filesize and filegrowth. If one of them has
changed since last run it sends me an email. I can then go in an correct
the values.
Regards
Steen Schlter Persson
Database Administrator / System Administrator
|||Personally I would just set the job to issue the necessary ALTER DATABASE
statement to fix the growth increment when identified (as well as send an
email that it had been done).
Also, I didn't investigate, but it may be possible to use a DDL trigger to
trap ALTER DATABASE calls on this database to 1) prevent the growth factor
change and 2) identify the offending code and get it fixed.
TheSQLGuru
President
Indicium Resources, Inc.
""Steen Schlter Persson (DK)"" <steen@.REMOVE_THIS_asavaenget.dk> wrote in
message news:%23lpkSXbrHHA.1296@.TK2MSFTNGP06.phx.gbl...
> Pim75 wrote:
> Hi
> Not that it helps you a lot, but we see the same thing happening on one
> specific database. Occasionally the mdf file for this database is being
> set to a growth rate of 12800% and then the file is around 258 GB.
> This has started after we moved this database from a SQL2000 server to a
> SQL2005 server. The vendor knows about the issue and they has the same
> problem with a few other customers. Since it happens quite seldom, they
> haven't been able to figure out what it is that causes it to happen. As a
> temporary workaround, I'v written a little sql script that runs every 15
> minuttes to check the filesize and filegrowth. If one of them has changed
> since last run it sends me an email. I can then go in an correct the
> values.
>
> --
> Regards
> Steen Schlter Persson
> Database Administrator / System Administrator
Autogrowth automatically set to 640 percent
Hello,
I've configured SQL Server 2005 express to use autogrowth by 5mb.
After a few weeks the autogrowth option automatically switched to 640
percent what will lead to performance problems.
After is set back the autogrowth to 5mb, a few weeks later the same
problem occurs.
Does anyone know what can cause this problem?
Thanks in advance,
PimWhich servicepack is installed?
You can disable autogrow and set the database size manually as temporarly
workaround.
greetz
"Pim75" wrote:
> Hello,
> I've configured SQL Server 2005 express to use autogrowth by 5mb.
> After a few weeks the autogrowth option automatically switched to 640
> percent what will lead to performance problems.
> After is set back the autogrowth to 5mb, a few weeks later the same
> problem occurs.
> Does anyone know what can cause this problem?
> Thanks in advance,
> Pim
>|||hi
make sure no one else is playing with the server
Regards
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"Pim75" <p.megens@.tiscali.nl> wrote in message
news:1181732495.637264.178440@.d30g2000prg.googlegroups.com...
> Hello,
> I've configured SQL Server 2005 express to use autogrowth by 5mb.
> After a few weeks the autogrowth option automatically switched to 640
> percent what will lead to performance problems.
> After is set back the autogrowth to 5mb, a few weeks later the same
> problem occurs.
> Does anyone know what can cause this problem?
> Thanks in advance,
> Pim
>|||We use Microsoft SQL Server Express Edition, version 9.00.1399.06
Windows 2003 webserver edition, servicepack 1.
We have some more servers but this is the only one where the problem
occurs.
On 13 jun, 13:37, Hate_orphaned_users
<Hateorphanedus...@.discussions.microsoft.com> wrote:
> Which servicepack is installed?
> You can disable autogrow and set the database size manually as temporarly
> workaround.
> greetz
>
> "Pim75" wrote:
>
>
>
> - Tekst uit oorspronkelijk bericht weergeven -|||Pim75 wrote:
> Hello,
> I've configured SQL Server 2005 express to use autogrowth by 5mb.
> After a few weeks the autogrowth option automatically switched to 640
> percent what will lead to performance problems.
> After is set back the autogrowth to 5mb, a few weeks later the same
> problem occurs.
> Does anyone know what can cause this problem?
> Thanks in advance,
> Pim
>
Hi
Not that it helps you a lot, but we see the same thing happening on one
specific database. Occasionally the mdf file for this database is being
set to a growth rate of 12800% and then the file is around 258 GB.
This has started after we moved this database from a SQL2000 server to a
SQL2005 server. The vendor knows about the issue and they has the same
problem with a few other customers. Since it happens quite seldom, they
haven't been able to figure out what it is that causes it to happen. As
a temporary workaround, I'v written a little sql script that runs every
15 minuttes to check the filesize and filegrowth. If one of them has
changed since last run it sends me an email. I can then go in an correct
the values.
Regards
Steen Schlter Persson
Database Administrator / System Administrator|||Personally I would just set the job to issue the necessary ALTER DATABASE
statement to fix the growth increment when identified (as well as send an
email that it had been done).
Also, I didn't investigate, but it may be possible to use a DDL trigger to
trap ALTER DATABASE calls on this database to 1) prevent the growth factor
change and 2) identify the offending code and get it fixed.
TheSQLGuru
President
Indicium Resources, Inc.
""Steen Schlter Persson (DK)"" <steen@.REMOVE_THIS_asavaenget.dk> wrote in
message news:%23lpkSXbrHHA.1296@.TK2MSFTNGP06.phx.gbl...
> Pim75 wrote:
> Hi
> Not that it helps you a lot, but we see the same thing happening on one
> specific database. Occasionally the mdf file for this database is being
> set to a growth rate of 12800% and then the file is around 258 GB.
> This has started after we moved this database from a SQL2000 server to a
> SQL2005 server. The vendor knows about the issue and they has the same
> problem with a few other customers. Since it happens quite seldom, they
> haven't been able to figure out what it is that causes it to happen. As a
> temporary workaround, I'v written a little sql script that runs every 15
> minuttes to check the filesize and filegrowth. If one of them has changed
> since last run it sends me an email. I can then go in an correct the
> values.
>
> --
> Regards
> Steen Schlter Persson
> Database Administrator / System Administrator
I've configured SQL Server 2005 express to use autogrowth by 5mb.
After a few weeks the autogrowth option automatically switched to 640
percent what will lead to performance problems.
After is set back the autogrowth to 5mb, a few weeks later the same
problem occurs.
Does anyone know what can cause this problem?
Thanks in advance,
PimWhich servicepack is installed?
You can disable autogrow and set the database size manually as temporarly
workaround.
greetz
"Pim75" wrote:
> Hello,
> I've configured SQL Server 2005 express to use autogrowth by 5mb.
> After a few weeks the autogrowth option automatically switched to 640
> percent what will lead to performance problems.
> After is set back the autogrowth to 5mb, a few weeks later the same
> problem occurs.
> Does anyone know what can cause this problem?
> Thanks in advance,
> Pim
>|||hi
make sure no one else is playing with the server
Regards
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"Pim75" <p.megens@.tiscali.nl> wrote in message
news:1181732495.637264.178440@.d30g2000prg.googlegroups.com...
> Hello,
> I've configured SQL Server 2005 express to use autogrowth by 5mb.
> After a few weeks the autogrowth option automatically switched to 640
> percent what will lead to performance problems.
> After is set back the autogrowth to 5mb, a few weeks later the same
> problem occurs.
> Does anyone know what can cause this problem?
> Thanks in advance,
> Pim
>|||We use Microsoft SQL Server Express Edition, version 9.00.1399.06
Windows 2003 webserver edition, servicepack 1.
We have some more servers but this is the only one where the problem
occurs.
On 13 jun, 13:37, Hate_orphaned_users
<Hateorphanedus...@.discussions.microsoft.com> wrote:
> Which servicepack is installed?
> You can disable autogrow and set the database size manually as temporarly
> workaround.
> greetz
>
> "Pim75" wrote:
>
>
>
> - Tekst uit oorspronkelijk bericht weergeven -|||Pim75 wrote:
> Hello,
> I've configured SQL Server 2005 express to use autogrowth by 5mb.
> After a few weeks the autogrowth option automatically switched to 640
> percent what will lead to performance problems.
> After is set back the autogrowth to 5mb, a few weeks later the same
> problem occurs.
> Does anyone know what can cause this problem?
> Thanks in advance,
> Pim
>
Hi
Not that it helps you a lot, but we see the same thing happening on one
specific database. Occasionally the mdf file for this database is being
set to a growth rate of 12800% and then the file is around 258 GB.
This has started after we moved this database from a SQL2000 server to a
SQL2005 server. The vendor knows about the issue and they has the same
problem with a few other customers. Since it happens quite seldom, they
haven't been able to figure out what it is that causes it to happen. As
a temporary workaround, I'v written a little sql script that runs every
15 minuttes to check the filesize and filegrowth. If one of them has
changed since last run it sends me an email. I can then go in an correct
the values.
Regards
Steen Schlter Persson
Database Administrator / System Administrator|||Personally I would just set the job to issue the necessary ALTER DATABASE
statement to fix the growth increment when identified (as well as send an
email that it had been done).
Also, I didn't investigate, but it may be possible to use a DDL trigger to
trap ALTER DATABASE calls on this database to 1) prevent the growth factor
change and 2) identify the offending code and get it fixed.
TheSQLGuru
President
Indicium Resources, Inc.
""Steen Schlter Persson (DK)"" <steen@.REMOVE_THIS_asavaenget.dk> wrote in
message news:%23lpkSXbrHHA.1296@.TK2MSFTNGP06.phx.gbl...
> Pim75 wrote:
> Hi
> Not that it helps you a lot, but we see the same thing happening on one
> specific database. Occasionally the mdf file for this database is being
> set to a growth rate of 12800% and then the file is around 258 GB.
> This has started after we moved this database from a SQL2000 server to a
> SQL2005 server. The vendor knows about the issue and they has the same
> problem with a few other customers. Since it happens quite seldom, they
> haven't been able to figure out what it is that causes it to happen. As a
> temporary workaround, I'v written a little sql script that runs every 15
> minuttes to check the filesize and filegrowth. If one of them has changed
> since last run it sends me an email. I can then go in an correct the
> values.
>
> --
> Regards
> Steen Schlter Persson
> Database Administrator / System Administrator
Autogrowth 32000 percent
I have a database with a 3G datafile, and 1G logfile. I have set the
Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
when, the Autogrowth is getting changed to [32000 percent]. So when the
datafile tries to expand it take a considerable amount of disk space (106G),
then my log dumps start failing due to low disk space.
Autogrowth=32000%
Has anyone seen this before?
Thanks in advance,
KenL wrote:
> I have a database with a 3G datafile, and 1G logfile. I have set the
> Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
> when, the Autogrowth is getting changed to [32000 percent]. So when the
> datafile tries to expand it take a considerable amount of disk space (106G),
> then my log dumps start failing due to low disk space.
> Autogrowth=32000%
> Has anyone seen this before?
> Thanks in advance,
You don't say, but I'm assuming this is on SQL 2005? This is a known
bug:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Tracy, thanks very much for the response. The feedback referenced below is
talking about SQL 2000, and says it will be fixed in the next release of SQL
Server. I am using SQL 2005, so isn't that the next release? I do not see a
resolution?
Thanks,
"Tracy McKibben" wrote:
> KenL wrote:
> You don't say, but I'm assuming this is on SQL 2005? This is a known
> bug:
> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
|||KenL wrote:
> Tracy, thanks very much for the response. The feedback referenced below is
> talking about SQL 2000, and says it will be fixed in the next release of SQL
> Server. I am using SQL 2005, so isn't that the next release? I do not see a
> resolution?
No, this is definately a SQL 2005 bug... The article that I linked to
talks about one possible cause of this as being a status bit in a
converted SQL 2000 database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Tracy, again thanks for the response.
The database is in SQL 2005, and was upgraded from a SQL 7 to SQL 2000, and
then SQL 2005. So are your saying this is a known bug that there currently is
no fix or workaround?
Thanks,
Ken
"Tracy McKibben" wrote:
> KenL wrote:
> No, this is definately a SQL 2005 bug... The article that I linked to
> talks about one possible cause of this as being a status bit in a
> converted SQL 2000 database.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
when, the Autogrowth is getting changed to [32000 percent]. So when the
datafile tries to expand it take a considerable amount of disk space (106G),
then my log dumps start failing due to low disk space.
Autogrowth=32000%
Has anyone seen this before?
Thanks in advance,
KenL wrote:
> I have a database with a 3G datafile, and 1G logfile. I have set the
> Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
> when, the Autogrowth is getting changed to [32000 percent]. So when the
> datafile tries to expand it take a considerable amount of disk space (106G),
> then my log dumps start failing due to low disk space.
> Autogrowth=32000%
> Has anyone seen this before?
> Thanks in advance,
You don't say, but I'm assuming this is on SQL 2005? This is a known
bug:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Tracy, thanks very much for the response. The feedback referenced below is
talking about SQL 2000, and says it will be fixed in the next release of SQL
Server. I am using SQL 2005, so isn't that the next release? I do not see a
resolution?
Thanks,
"Tracy McKibben" wrote:
> KenL wrote:
> You don't say, but I'm assuming this is on SQL 2005? This is a known
> bug:
> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
|||KenL wrote:
> Tracy, thanks very much for the response. The feedback referenced below is
> talking about SQL 2000, and says it will be fixed in the next release of SQL
> Server. I am using SQL 2005, so isn't that the next release? I do not see a
> resolution?
No, this is definately a SQL 2005 bug... The article that I linked to
talks about one possible cause of this as being a status bit in a
converted SQL 2000 database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Tracy, again thanks for the response.
The database is in SQL 2005, and was upgraded from a SQL 7 to SQL 2000, and
then SQL 2005. So are your saying this is a known bug that there currently is
no fix or workaround?
Thanks,
Ken
"Tracy McKibben" wrote:
> KenL wrote:
> No, this is definately a SQL 2005 bug... The article that I linked to
> talks about one possible cause of this as being a status bit in a
> converted SQL 2000 database.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
Autogrowth 32000 percent
I have a database with a 3G datafile, and 1G logfile. I have set the
Autogrowth on the datafile to 250M, for the third time. Somehow, I don't kno
w
when, the Autogrowth is getting changed to [32000 percent]. So when the
datafile tries to expand it take a considerable amount of disk space (106G),
then my log dumps start failing due to low disk space.
Autogrowth=32000%
Has anyone seen this before?
Thanks in advance,KenL wrote:
> I have a database with a 3G datafile, and 1G logfile. I have set the
> Autogrowth on the datafile to 250M, for the third time. Somehow, I don't k
now
> when, the Autogrowth is getting changed to [32000 percent]. So when th
e
> datafile tries to expand it take a considerable amount of disk space (106G
),
> then my log dumps start failing due to low disk space.
> Autogrowth=32000%
> Has anyone seen this before?
> Thanks in advance,
You don't say, but I'm assuming this is on SQL 2005? This is a known
bug:
http://connect.microsoft.com/SQLSer...=12717
7
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy, thanks very much for the response. The feedback referenced below is
talking about SQL 2000, and says it will be fixed in the next release of SQL
Server. I am using SQL 2005, so isn't that the next release? I do not see a
resolution?
Thanks,
"Tracy McKibben" wrote:
> KenL wrote:
> You don't say, but I'm assuming this is on SQL 2005? This is a known
> bug:
> http://connect.microsoft.com/SQLSer...=127
177
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||KenL wrote:
> Tracy, thanks very much for the response. The feedback referenced below is
> talking about SQL 2000, and says it will be fixed in the next release of S
QL
> Server. I am using SQL 2005, so isn't that the next release? I do not see
a
> resolution?
No, this is definately a SQL 2005 bug... The article that I linked to
talks about one possible cause of this as being a status bit in a
converted SQL 2000 database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy, again thanks for the response.
The database is in SQL 2005, and was upgraded from a SQL 7 to SQL 2000, and
then SQL 2005. So are your saying this is a known bug that there currently i
s
no fix or workaround?
Thanks,
Ken
"Tracy McKibben" wrote:
> KenL wrote:
> No, this is definately a SQL 2005 bug... The article that I linked to
> talks about one possible cause of this as being a status bit in a
> converted SQL 2000 database.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
Autogrowth on the datafile to 250M, for the third time. Somehow, I don't kno
w
when, the Autogrowth is getting changed to [32000 percent]. So when the
datafile tries to expand it take a considerable amount of disk space (106G),
then my log dumps start failing due to low disk space.
Autogrowth=32000%
Has anyone seen this before?
Thanks in advance,KenL wrote:
> I have a database with a 3G datafile, and 1G logfile. I have set the
> Autogrowth on the datafile to 250M, for the third time. Somehow, I don't k
now
> when, the Autogrowth is getting changed to [32000 percent]. So when th
e
> datafile tries to expand it take a considerable amount of disk space (106G
),
> then my log dumps start failing due to low disk space.
> Autogrowth=32000%
> Has anyone seen this before?
> Thanks in advance,
You don't say, but I'm assuming this is on SQL 2005? This is a known
bug:
http://connect.microsoft.com/SQLSer...=12717
7
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy, thanks very much for the response. The feedback referenced below is
talking about SQL 2000, and says it will be fixed in the next release of SQL
Server. I am using SQL 2005, so isn't that the next release? I do not see a
resolution?
Thanks,
"Tracy McKibben" wrote:
> KenL wrote:
> You don't say, but I'm assuming this is on SQL 2005? This is a known
> bug:
> http://connect.microsoft.com/SQLSer...=127
177
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||KenL wrote:
> Tracy, thanks very much for the response. The feedback referenced below is
> talking about SQL 2000, and says it will be fixed in the next release of S
QL
> Server. I am using SQL 2005, so isn't that the next release? I do not see
a
> resolution?
No, this is definately a SQL 2005 bug... The article that I linked to
talks about one possible cause of this as being a status bit in a
converted SQL 2000 database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy, again thanks for the response.
The database is in SQL 2005, and was upgraded from a SQL 7 to SQL 2000, and
then SQL 2005. So are your saying this is a known bug that there currently i
s
no fix or workaround?
Thanks,
Ken
"Tracy McKibben" wrote:
> KenL wrote:
> No, this is definately a SQL 2005 bug... The article that I linked to
> talks about one possible cause of this as being a status bit in a
> converted SQL 2000 database.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
Autogrowth 32000 percent
I have a database with a 3G datafile, and 1G logfile. I have set the
Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
when, the Autogrowth is getting changed to [32000 percent]. So when the
datafile tries to expand it take a considerable amount of disk space (106G),
then my log dumps start failing due to low disk space.
Autogrowth=32000%
Has anyone seen this before?
Thanks in advance,KenL wrote:
> I have a database with a 3G datafile, and 1G logfile. I have set the
> Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
> when, the Autogrowth is getting changed to [32000 percent]. So when the
> datafile tries to expand it take a considerable amount of disk space (106G),
> then my log dumps start failing due to low disk space.
> Autogrowth=32000%
> Has anyone seen this before?
> Thanks in advance,
You don't say, but I'm assuming this is on SQL 2005? This is a known
bug:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy, thanks very much for the response. The feedback referenced below is
talking about SQL 2000, and says it will be fixed in the next release of SQL
Server. I am using SQL 2005, so isn't that the next release? I do not see a
resolution?
Thanks,
"Tracy McKibben" wrote:
> KenL wrote:
> > I have a database with a 3G datafile, and 1G logfile. I have set the
> > Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
> > when, the Autogrowth is getting changed to [32000 percent]. So when the
> > datafile tries to expand it take a considerable amount of disk space (106G),
> > then my log dumps start failing due to low disk space.
> >
> > Autogrowth=32000%
> > Has anyone seen this before?
> >
> > Thanks in advance,
> You don't say, but I'm assuming this is on SQL 2005? This is a known
> bug:
> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||KenL wrote:
> Tracy, thanks very much for the response. The feedback referenced below is
> talking about SQL 2000, and says it will be fixed in the next release of SQL
> Server. I am using SQL 2005, so isn't that the next release? I do not see a
> resolution?
No, this is definately a SQL 2005 bug... The article that I linked to
talks about one possible cause of this as being a status bit in a
converted SQL 2000 database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy, again thanks for the response.
The database is in SQL 2005, and was upgraded from a SQL 7 to SQL 2000, and
then SQL 2005. So are your saying this is a known bug that there currently is
no fix or workaround?
Thanks,
Ken
"Tracy McKibben" wrote:
> KenL wrote:
> > Tracy, thanks very much for the response. The feedback referenced below is
> > talking about SQL 2000, and says it will be fixed in the next release of SQL
> > Server. I am using SQL 2005, so isn't that the next release? I do not see a
> > resolution?
> No, this is definately a SQL 2005 bug... The article that I linked to
> talks about one possible cause of this as being a status bit in a
> converted SQL 2000 database.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
when, the Autogrowth is getting changed to [32000 percent]. So when the
datafile tries to expand it take a considerable amount of disk space (106G),
then my log dumps start failing due to low disk space.
Autogrowth=32000%
Has anyone seen this before?
Thanks in advance,KenL wrote:
> I have a database with a 3G datafile, and 1G logfile. I have set the
> Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
> when, the Autogrowth is getting changed to [32000 percent]. So when the
> datafile tries to expand it take a considerable amount of disk space (106G),
> then my log dumps start failing due to low disk space.
> Autogrowth=32000%
> Has anyone seen this before?
> Thanks in advance,
You don't say, but I'm assuming this is on SQL 2005? This is a known
bug:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy, thanks very much for the response. The feedback referenced below is
talking about SQL 2000, and says it will be fixed in the next release of SQL
Server. I am using SQL 2005, so isn't that the next release? I do not see a
resolution?
Thanks,
"Tracy McKibben" wrote:
> KenL wrote:
> > I have a database with a 3G datafile, and 1G logfile. I have set the
> > Autogrowth on the datafile to 250M, for the third time. Somehow, I don't know
> > when, the Autogrowth is getting changed to [32000 percent]. So when the
> > datafile tries to expand it take a considerable amount of disk space (106G),
> > then my log dumps start failing due to low disk space.
> >
> > Autogrowth=32000%
> > Has anyone seen this before?
> >
> > Thanks in advance,
> You don't say, but I'm assuming this is on SQL 2005? This is a known
> bug:
> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||KenL wrote:
> Tracy, thanks very much for the response. The feedback referenced below is
> talking about SQL 2000, and says it will be fixed in the next release of SQL
> Server. I am using SQL 2005, so isn't that the next release? I do not see a
> resolution?
No, this is definately a SQL 2005 bug... The article that I linked to
talks about one possible cause of this as being a status bit in a
converted SQL 2000 database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy, again thanks for the response.
The database is in SQL 2005, and was upgraded from a SQL 7 to SQL 2000, and
then SQL 2005. So are your saying this is a known bug that there currently is
no fix or workaround?
Thanks,
Ken
"Tracy McKibben" wrote:
> KenL wrote:
> > Tracy, thanks very much for the response. The feedback referenced below is
> > talking about SQL 2000, and says it will be fixed in the next release of SQL
> > Server. I am using SQL 2005, so isn't that the next release? I do not see a
> > resolution?
> No, this is definately a SQL 2005 bug... The article that I linked to
> talks about one possible cause of this as being a status bit in a
> converted SQL 2000 database.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
Subscribe to:
Posts (Atom)