Autogrow question

Hello Folks,

Last evening, as a result of our autogrow settings, our production
database grew from 102 GB to 107 GB. What puzzled me is that, prior to
the growth, we still had a good 10% free space left in the data file.
My understanding is that SQL Server will automatically grow a database
when worker thread decides that more space is necessary to fulfill a
request. We don't suspect the app of sending over a request which
would require that much more space.

Any ideas on why the file grew unexpectedly?

Thanks,
Joe

.

Relevant Pages

  • Re: Issues with CHANGE_TRACKING AUTO after initial index population
    ... There's a problem with 64 bit SQL 2005 server. ... Director of Text Mining and Database Strategy ... started the FT initial index population when our site activity is low. ... High activity on the data file. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Using SQl to store aspx pages and memory problems
    ... I've seen classic ASP applications design this way that work ... database isn't some sort of magic pixie dust that solves all problems. ... > the memory increases - the slowness of the request could be dealt with by ... >> takes to get the page from SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: URGENT: Application_Start - doesnt fire
    ... Your application start is firing correctly because you can request a page. ... I have>> stopped and started the Web site via IIS Manager. ... This particular Web application connects to a>> database. ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: Need Help To Create a Function For Parameter Query
    ... >> function up with prompts ... > adds your question and the answers to the database of answers. ... >> I have a query named Status. ... >> Request Date. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Access database stability problems
    ... The backend data files are even located on the same network drive on the server. ... I found out today that people running that database are NOT having crashes like we are. ... What I wanted to strongly recommend is moving your database to an SQL server of some kind, SQL Server 2005 Express if nothing else. ... You haven't said whether 'crashing the database' is just a matter of Access losing its network connection and screaming blue murder, or whether it's actually breaking the backend data file. ...
    (microsoft.public.windows.server.sbs)