Fixed datafile suddenly change to max "automaticgrow"

Hi to all,
If I give in a fixed datafile size ( say 80000 Mb ) for a couple of
datafiles SQL server is capturing the size on the filesystem and after
finishing I asume this size is dedicated to this particular file(s) and
checking this it seems to be OK....
however. . .
Checking this same fixed filesize the next moring the original size ( before
yesterdays action ) has returned and the 80000 Mb has been MOVED to the
"automatic grow file" part as max extented restriction. ( this part was
grayed out and is still grayed out ).
it seems that I have a problem when SQL server needs to expand . . . . .
( the application running this database has a mechanism to stop when 80pct
has been reached of just one datafile ( of many ) - no alternative on the
application part !! )
Is this a known issue or is this a SQL server BUG and how to fixe this '
Please help me out.
GKramer
The NetherlandsHi
I think you are using SQL Server 2005 , right? I have seen this behaviour
when you detach/attach the database and it should be fixed in SP1 , however
someone else can provide more info.
"Guus Kramer" <GuusKramer@.discussions.microsoft.com> wrote in message
news:1B126CF6-8A66-429A-8D2E-82D730C9502F@.microsoft.com...
> Hi to all,
> If I give in a fixed datafile size ( say 80000 Mb ) for a couple of
> datafiles SQL server is capturing the size on the filesystem and after
> finishing I asume this size is dedicated to this particular file(s) and
> checking this it seems to be OK....
> however. . .
> Checking this same fixed filesize the next moring the original size (
> before
> yesterdays action ) has returned and the 80000 Mb has been MOVED to the
> "automatic grow file" part as max extented restriction. ( this part was
> grayed out and is still grayed out ).
> it seems that I have a problem when SQL server needs to expand . . . . .
> ( the application running this database has a mechanism to stop when 80pct
> has been reached of just one datafile ( of many ) - no alternative on the
> application part !! )
> Is this a known issue or is this a SQL server BUG and how to fixe this '
> Please help me out.
> GKramer
> The Netherlands
>|||Uri,
Thanks for the quick reply.
Unfortionately we still use SQL serve 2000 ( 2005 is still being tested ).
No attach or detach has been made. . . .it just happened overnight !!!!!
Guus
"Uri Dimant" wrote:

> Hi
> I think you are using SQL Server 2005 , right? I have seen this behaviour
> when you detach/attach the database and it should be fixed in SP1 , howeve
r
> someone else can provide more info.
>
>
> "Guus Kramer" <GuusKramer@.discussions.microsoft.com> wrote in message
> news:1B126CF6-8A66-429A-8D2E-82D730C9502F@.microsoft.com...
>
>|||Hi
Well, so perhaps someone has changed this feature and you did not know , did
you?
"Guus Kramer" <GuusKramer@.discussions.microsoft.com> wrote in message
news:83ECCAAA-3E98-4F88-AC2E-99AD3F9E93DB@.microsoft.com...[vbcol=seagreen]
> Uri,
> Thanks for the quick reply.
> Unfortionately we still use SQL serve 2000 ( 2005 is still being tested ).
> No attach or detach has been made. . . .it just happened overnight !!!!!
> Guus
> "Uri Dimant" wrote:
>|||Uri,
I was the only DBA for Europe last week and no-one other than me ( and our
DBA team ) has access !!!! ( or even has the knowledge on this )
Guus
"Uri Dimant" wrote:

> Hi
> Well, so perhaps someone has changed this feature and you did not know , d
id
> you?
>
>
> "Guus Kramer" <GuusKramer@.discussions.microsoft.com> wrote in message
> news:83ECCAAA-3E98-4F88-AC2E-99AD3F9E93DB@.microsoft.com...
>
>|||Hi
Then I have no idea. It could be that a script will be ran to change the
settings , you know, there is no magic here :-))))
"Guus Kramer" <GuusKramer@.discussions.microsoft.com> wrote in message
news:70F7163C-82F1-4625-955E-C15FEBDB1D51@.microsoft.com...[vbcol=seagreen]
> Uri,
> I was the only DBA for Europe last week and no-one other than me ( and our
> DBA team ) has access !!!! ( or even has the knowledge on this )
> Guus
> "Uri Dimant" wrote:
>