Is the database offline as it grows data files ?

Just curious to know if the database does take some hit by going offline
when the data files grow ?Hassan
No, a database is not OFF at this time, the users will be waiting till the
growth will be completed. We should prevent from such situations
"Hassan" <Hassan@.hotmail.com> wrote in message
news:eBJAVEZyGHA.4024@.TK2MSFTNGP02.phx.gbl...
> Just curious to know if the database does take some hit by going offline
> when the data files grow ?
>
>|||I didnt know..
So if i have a 10GB database and if i have to grow it to say 100GB and it
takes 10 mins , are you saying that no users will be able to connect or
perform any work during this 10 mins ?
Will connections be timed out or will queries take longer to execute ? Can
you please comment ?
Thanks
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23kEZrJayGHA.4232@.TK2MSFTNGP04.phx.gbl...
> Hassan
> No, a database is not OFF at this time, the users will be waiting till the
> growth will be completed. We should prevent from such situations
>
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:eBJAVEZyGHA.4024@.TK2MSFTNGP02.phx.gbl...
>> Just curious to know if the database does take some hit by going offline
>> when the data files grow ?
>>
>|||Hi
If autogrow kicks in due to DB or Log space being unavailable:
Users will still be able the query the DB, assuming they are not blocked
by normal locking.
Transactions can NOT continue. Everyone doing Data modifications will be
blocked until space is available again. If the querytimeout occurs, the
specific transactions will be aborted. If the transaction that caused the
autogrow operation to occur rolls back, the autogrow rolls back.
Checkpoints will not occur until space is available again.
IO performance will be severely impacted.
Microsoft's recommendation is not to use Autogrow in a production
environment. Rather manage the space properly by pre-growing the DB and Log
in good sized chunks and only rely on autogrow as last-resort if the DBA did
not manage the space well.
If the DB or Log are grown manually, and if space is available for the
current transactions:
Users will still be able the query the DB, assuming they are not blocked
by normal locking.
Transactions can continue.
Checkpoints continues to occur.
IO performance will be severely impacted.
The severely reduced IO throughput will affect performance and may cause
queries to time-out. Growing DB's is recommended when the load is least and
in a controlled manner.
Regards
--
Mike
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hassan" <Hassan@.hotmail.com> wrote in message
news:OD70MXhyGHA.4576@.TK2MSFTNGP06.phx.gbl...
>I didnt know..
> So if i have a 10GB database and if i have to grow it to say 100GB and it
> takes 10 mins , are you saying that no users will be able to connect or
> perform any work during this 10 mins ?
> Will connections be timed out or will queries take longer to execute ? Can
> you please comment ?
> Thanks
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:%23kEZrJayGHA.4232@.TK2MSFTNGP04.phx.gbl...
>> Hassan
>> No, a database is not OFF at this time, the users will be waiting till
>> the growth will be completed. We should prevent from such situations
>>
>>
>> "Hassan" <Hassan@.hotmail.com> wrote in message
>> news:eBJAVEZyGHA.4024@.TK2MSFTNGP02.phx.gbl...
>> Just curious to know if the database does take some hit by going offline
>> when the data files grow ?
>>
>>
>sql