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,
JoeHi

Although everywhere I have found regarding filegrowth indicates it is done
when the file is full, it would make sense that it is grown before it is
actually totally full otherwise you will have problems on a highly active
system!!!

You can still have problems if the file growth is set to very large values
even if the disc space is available as the time to fill up the remainder of
the file may be less than the time taken to grow it.

John

"ceadtinneh" <sulla33@.yahoo.com> wrote in message
news:1128023665.503904.262830@.z14g2000cwz.googlegr oups.com...
> 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

Auto-Generate MDX Query from Cube OWC Settings?

Can I somehow auto-generate an MDX query based on current settings in the AS OWC cube browser? Why? If so, I will want to use the AS OWC cube browser to filter the data down to < 66K rows, then auto-generate an MDX query from the current browsed settings, copy and paste the MDX script into MS Excel's OLAP query, and use it. I'm trying to avoid the 66K row limitation in Excel 2002.

If this is innappropriate, is there another way, besides raw MDX hand-coding, to accomplish the same thing?

You can start a trace using the SQL Server Profiler, and see the MDX query created by OWC. Then use that query in Excel?

Chris.