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:
> > 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

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

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

Auto numbering field similar to

I've been using MS Access 2000 for a while and have recently switched to MS
SQL 2000. When creating a primary key I am used to MS Access ability to auto
matically enter a number in the ID field when I enter data into my tables.
Does MS SQL have a feature similar to this? I checked all the data types and
the only thing that I see that is close to autonumber is uniqueidentifier. Is
that the same thing?
Walker_Michael wrote:
> I've been using MS Access 2000 for a while and have recently switched
> to MS SQL 2000. When creating a primary key I am used to MS Access
> ability to auto matically enter a number in the ID field when I enter
> data into my tables. Does MS SQL have a feature similar to this? I
> checked all the data types and the only thing that I see that is
> close to autonumber is uniqueidentifier. Is that the same thing?
No, not really. What you want is an IDENTITY column (attached to a
numeric data type) as in:
Create Table Customers (
CustID INT IDENTITY NOT NULL )
Unique identifiers can be used as well, but you need to generate the
number manually using the newid() function. They consists of a 16-byte
hexadecimal number (GUID). Some SQL Server users use them as keys. They
are used frequently in replication. The INT IDENTITY can accommodate
more than 2 Billion values and is only 4-bytes as opposed to 16.
The return the last identity value inserted, you should use
scope_identity(). From a stored procedure, you could use:
Create Proc dbo.UpdateCustomer
@.CustID INT OUTPUT,
@.CustName VARCHAR(50
as
Begin
If @.CustID IS NOT NULL
Update dbo.Customers
Set CustName = @.CustName
Where CustID = @.CustID
Else
Begin
Insert dbo.Customers (
CustName)
Values (
@.CustName )
Set @.CustID = SCOPE_IDENTITY()
End
End
To call this procedure:
Declare @.CustID INT
Exec dbo.UpdateCustomer @.CustID OUTPUT, 'David Gugick'
Select @.CustID
David Gugick
Imceda Software
www.imceda.com