hotfix for: KB816939 (PRB: File Growth Value for TempDB is Not Per

Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent When
Changed From Fixed Increments to Percentage):
Does anyone know if microsoft has included a fix for this in sp4, or has a
hotfix for this bug?
We tried the workaround listed in the KB, but it did not work...
Link:
http://support.microsoft.com/defaul...n-us;816939#kb4Can you give more info regarding how the work around did not work?
As far as I know the fix did not make it into SP4...
It is fixed in SQL 2005 though.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:FF219273-52D1-42C0-8CE5-35CDF27E01BD@.microsoft.com...
> Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent
When
> Changed From Fixed Increments to Percentage):
> Does anyone know if microsoft has included a fix for this in sp4, or has a
> hotfix for this bug?
> We tried the workaround listed in the KB, but it did not work...
> Link:
> http://support.microsoft.com/defaul...n-us;816939#kb4

hotfix for: KB816939 (PRB: File Growth Value for TempDB is Not Per

Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent When
Changed From Fixed Increments to Percentage):
Does anyone know if microsoft has included a fix for this in sp4, or has a
hotfix for this bug?
We tried the workaround listed in the KB, but it did not work...
Link:
http://support.microsoft.com/default...-us;816939#kb4
Can you give more info regarding how the work around did not work?
As far as I know the fix did not make it into SP4...
It is fixed in SQL 2005 though.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:FF219273-52D1-42C0-8CE5-35CDF27E01BD@.microsoft.com...
> Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent
When
> Changed From Fixed Increments to Percentage):
> Does anyone know if microsoft has included a fix for this in sp4, or has a
> hotfix for this bug?
> We tried the workaround listed in the KB, but it did not work...
> Link:
> http://support.microsoft.com/default...-us;816939#kb4

hotfix for: KB816939 (PRB: File Growth Value for TempDB is Not Per

Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent When
Changed From Fixed Increments to Percentage):
Does anyone know if microsoft has included a fix for this in sp4, or has a
hotfix for this bug?
We tried the workaround listed in the KB, but it did not work...
Link:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816939#kb4Can you give more info regarding how the work around did not work?
As far as I know the fix did not make it into SP4...
It is fixed in SQL 2005 though.
--
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:FF219273-52D1-42C0-8CE5-35CDF27E01BD@.microsoft.com...
> Regarding KB816939 (PRB: File Growth Value for TempDB is Not Persistent
When
> Changed From Fixed Increments to Percentage):
> Does anyone know if microsoft has included a fix for this in sp4, or has a
> hotfix for this bug?
> We tried the workaround listed in the KB, but it did not work...
> Link:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;816939#kb4

hosted sql 2005 databases

We are hosting multiple sql server 2005 databases on a windows 2003 server.
I've setup restricted growth on the databases to 50 mb. What would be a good
setting for the log files? I have all of the databases setup in Simple
recovery mode. Is Auto Shrink = True a good idea?
Please advise.
Thanks!
Hi
The best way to get these values is to monitor it during you normal working
period (e.g. a week and take the values from that). If the files are often
growing then you may want to increase the size they grow by, or put in a
system when the files are increased at a time when it will not impact users.
For log file sizes hopefully you can set a maximum ceiling that will rarely
be expanded.
Growing the files frequently may lead to disc fragmentation and decreases in
performance, therefore auto shrink is not a good idea.
You should monitor the space available on your disc so that you can prevent
the sort of situation where there is not enough room to expand the database.
MOM is a very useful to monitor your SQL Server in this respect.
John
"mp3nomad" wrote:

> We are hosting multiple sql server 2005 databases on a windows 2003 server.
> I've setup restricted growth on the databases to 50 mb. What would be a good
> setting for the log files? I have all of the databases setup in Simple
> recovery mode. Is Auto Shrink = True a good idea?
> Please advise.
> Thanks!

hosted sql 2005 databases

We are hosting multiple sql server 2005 databases on a windows 2003 server.
I've setup restricted growth on the databases to 50 mb. What would be a good
setting for the log files? I have all of the databases setup in Simple
recovery mode. Is Auto Shrink = True a good idea?
Please advise.
Thanks!Hi
The best way to get these values is to monitor it during you normal working
period (e.g. a week and take the values from that). If the files are often
growing then you may want to increase the size they grow by, or put in a
system when the files are increased at a time when it will not impact users.
For log file sizes hopefully you can set a maximum ceiling that will rarely
be expanded.
Growing the files frequently may lead to disc fragmentation and decreases in
performance, therefore auto shrink is not a good idea.
You should monitor the space available on your disc so that you can prevent
the sort of situation where there is not enough room to expand the database.
MOM is a very useful to monitor your SQL Server in this respect.
John
"mp3nomad" wrote:
> We are hosting multiple sql server 2005 databases on a windows 2003 server.
> I've setup restricted growth on the databases to 50 mb. What would be a good
> setting for the log files? I have all of the databases setup in Simple
> recovery mode. Is Auto Shrink = True a good idea?
> Please advise.
> Thanks!