I have read these two sites:
http://blogs.msdn.com/bryanke/articles/71491.aspx
http://scruffylookingcatherder.com/archive/2007/12/07/printing-reporting-services-2005-reports.aspx
But I'm new to Reporting Services and these methods aren't well documented
(that I can find). I have a report that has four parameters -- the second
parameter is queried off the value of the first, and could potentially have
up to five unique values for each unique first value. I need to generate a
report for each unique device listed in the second parameter, spit it out to
PDF for us to review and email to the clients.
Is there a command that can be used to do this? Or do I need to do a SQL
query or two myself to pull those values, and using a foreach statement
generate a report for each?
Any suggestions would be fantastic.
--Nathan Loding
Systems Associate, Special Projects
WESCO NetI doubt that RS has the capabilities you're looking for as that kind of
round-tripping would be frought with really complicated issues (mainly
maintaining state management). I did a cursory look at the client proxy
objects and nothing lept out at me that seems like it'd do what you're
looking for. I can't claim this to be an authoritative answer, but
personally, I'm betting you'll have to redo the queries client-side if you're
going to mimic the Report Manager functionality.
Jacob
"Nathan Loding" wrote:
> I have read these two sites:
> http://blogs.msdn.com/bryanke/articles/71491.aspx
> http://scruffylookingcatherder.com/archive/2007/12/07/printing-reporting-services-2005-reports.aspx
> But I'm new to Reporting Services and these methods aren't well documented
> (that I can find). I have a report that has four parameters -- the second
> parameter is queried off the value of the first, and could potentially have
> up to five unique values for each unique first value. I need to generate a
> report for each unique device listed in the second parameter, spit it out to
> PDF for us to review and email to the clients.
> Is there a command that can be used to do this? Or do I need to do a SQL
> query or two myself to pull those values, and using a foreach statement
> generate a report for each?
> Any suggestions would be fantastic.
> --Nathan Loding
> Systems Associate, Special Projects
> WESCO Net
Showing posts with label articles. Show all posts
Showing posts with label articles. Show all posts
Wednesday, March 7, 2012
Friday, February 24, 2012
Autogrow Timeouts
Hello - Can anyone direct me to good articles on Alter database and Autogrow?
We have a shared server where users in one database got timeouts. Looking
back at the logs, the database was trying to grow during that time frame, but
it timed out. Please see part of log:
2006-10-17 15:00:32.97 spid622 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 15922 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:00:44.41 spid168 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 11390 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:00:46.14 spid460 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 1672 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:05.19 spid745 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 18968 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:05.62 spid478 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 406 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:10.03 spid213 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 4390 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:09.95 spid175 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 59906 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:23.48 spid478 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 13515 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:47.55 spid69 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 24047 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:49.81 spid875 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 2265 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:03:12.64 spid168 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 22829 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
The database is about 2.7 gb, and the autogrow is set for 10%. So it was
trying to add maybe 300 mb, but it kept timing out. I could understand it
being an issue for a larger number, but 300 mb is not very much.
When the alter database add filespace happens, is the entire database
inaccessible during that time? Or is it just the space it is adding that is
inaccessible?
I am wondering if the autogrow timeouts and the user timeouts had the same
thing happening to make them timeout. Or if the autogrow attempts were
causing the user timeouts. Seems that cpu on the server were normal, and no
other databases had complaints of slows. The autogrow attempts kept
happening for about an hour and a half before it was succesful. Please help!
Below are two KB about the issue:
http://support.microsoft.com/kb/315512/
INF: Considerations for Autogrow and Autoshrink configuration in SQL
Server
http://support.microsoft.com/kb/305635/
PRB: A Timeout Occurs When a Database Is Automatically Expanding
Mitch wrote:
> Hello - Can anyone direct me to good articles on Alter database and Autogrow?
> We have a shared server where users in one database got timeouts. Looking
> back at the logs, the database was trying to grow during that time frame, but
> it timed out. Please see part of log:
> 2006-10-17 15:00:32.97 spid622 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 15922 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:00:44.41 spid168 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 11390 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:00:46.14 spid460 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 1672 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:05.19 spid745 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 18968 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:05.62 spid478 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 406 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:10.03 spid213 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 4390 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:09.95 spid175 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 59906 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:23.48 spid478 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 13515 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:47.55 spid69 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 24047 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:49.81 spid875 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 2265 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:03:12.64 spid168 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 22829 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> The database is about 2.7 gb, and the autogrow is set for 10%. So it was
> trying to add maybe 300 mb, but it kept timing out. I could understand it
> being an issue for a larger number, but 300 mb is not very much.
> When the alter database add filespace happens, is the entire database
> inaccessible during that time? Or is it just the space it is adding that is
> inaccessible?
> I am wondering if the autogrow timeouts and the user timeouts had the same
> thing happening to make them timeout. Or if the autogrow attempts were
> causing the user timeouts. Seems that cpu on the server were normal, and no
> other databases had complaints of slows. The autogrow attempts kept
> happening for about an hour and a half before it was succesful. Please help!
We have a shared server where users in one database got timeouts. Looking
back at the logs, the database was trying to grow during that time frame, but
it timed out. Please see part of log:
2006-10-17 15:00:32.97 spid622 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 15922 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:00:44.41 spid168 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 11390 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:00:46.14 spid460 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 1672 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:05.19 spid745 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 18968 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:05.62 spid478 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 406 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:10.03 spid213 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 4390 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:09.95 spid175 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 59906 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:23.48 spid478 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 13515 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:47.55 spid69 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 24047 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:49.81 spid875 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 2265 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:03:12.64 spid168 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 22829 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
The database is about 2.7 gb, and the autogrow is set for 10%. So it was
trying to add maybe 300 mb, but it kept timing out. I could understand it
being an issue for a larger number, but 300 mb is not very much.
When the alter database add filespace happens, is the entire database
inaccessible during that time? Or is it just the space it is adding that is
inaccessible?
I am wondering if the autogrow timeouts and the user timeouts had the same
thing happening to make them timeout. Or if the autogrow attempts were
causing the user timeouts. Seems that cpu on the server were normal, and no
other databases had complaints of slows. The autogrow attempts kept
happening for about an hour and a half before it was succesful. Please help!
Below are two KB about the issue:
http://support.microsoft.com/kb/315512/
INF: Considerations for Autogrow and Autoshrink configuration in SQL
Server
http://support.microsoft.com/kb/305635/
PRB: A Timeout Occurs When a Database Is Automatically Expanding
Mitch wrote:
> Hello - Can anyone direct me to good articles on Alter database and Autogrow?
> We have a shared server where users in one database got timeouts. Looking
> back at the logs, the database was trying to grow during that time frame, but
> it timed out. Please see part of log:
> 2006-10-17 15:00:32.97 spid622 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 15922 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:00:44.41 spid168 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 11390 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:00:46.14 spid460 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 1672 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:05.19 spid745 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 18968 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:05.62 spid478 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 406 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:10.03 spid213 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 4390 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:09.95 spid175 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 59906 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:23.48 spid478 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 13515 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:47.55 spid69 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 24047 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:49.81 spid875 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 2265 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:03:12.64 spid168 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 22829 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> The database is about 2.7 gb, and the autogrow is set for 10%. So it was
> trying to add maybe 300 mb, but it kept timing out. I could understand it
> being an issue for a larger number, but 300 mb is not very much.
> When the alter database add filespace happens, is the entire database
> inaccessible during that time? Or is it just the space it is adding that is
> inaccessible?
> I am wondering if the autogrow timeouts and the user timeouts had the same
> thing happening to make them timeout. Or if the autogrow attempts were
> causing the user timeouts. Seems that cpu on the server were normal, and no
> other databases had complaints of slows. The autogrow attempts kept
> happening for about an hour and a half before it was succesful. Please help!
Autogrow Timeouts
Hello - Can anyone direct me to good articles on Alter database and Autogrow
?
We have a shared server where users in one database got timeouts. Looking
back at the logs, the database was trying to grow during that time frame, bu
t
it timed out. Please see part of log:
2006-10-17 15:00:32.97 spid622 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 15922 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:00:44.41 spid168 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 11390 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:00:46.14 spid460 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 1672 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:05.19 spid745 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 18968 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:05.62 spid478 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 406 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:10.03 spid213 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 4390 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:09.95 spid175 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 59906 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:23.48 spid478 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 13515 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:47.55 spid69 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 24047 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:49.81 spid875 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 2265 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:03:12.64 spid168 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 22829 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
The database is about 2.7 gb, and the autogrow is set for 10%. So it was
trying to add maybe 300 mb, but it kept timing out. I could understand it
being an issue for a larger number, but 300 mb is not very much.
When the alter database add filespace happens, is the entire database
inaccessible during that time? Or is it just the space it is adding that is
inaccessible?
I am wondering if the autogrow timeouts and the user timeouts had the same
thing happening to make them timeout. Or if the autogrow attempts were
causing the user timeouts. Seems that cpu on the server were normal, and no
other databases had complaints of slows. The autogrow attempts kept
happening for about an hour and a half before it was succesful. Please help
!Below are two KB about the issue:
http://support.microsoft.com/kb/315512/
INF: Considerations for Autogrow and Autoshrink configuration in SQL
Server
http://support.microsoft.com/kb/305635/
PRB: A Timeout Occurs When a Database Is Automatically Expanding
Mitch wrote:[vbcol=seagreen]
> Hello - Can anyone direct me to good articles on Alter database and Autogr
ow?
> We have a shared server where users in one database got timeouts. Lookin
g
> back at the logs, the database was trying to grow during that time frame,
but
> it timed out. Please see part of log:
> 2006-10-17 15:00:32.97 spid622 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 15922 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:00:44.41 spid168 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 11390 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:00:46.14 spid460 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 1672 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:05.19 spid745 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 18968 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:05.62 spid478 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 406 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:10.03 spid213 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 4390 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:09.95 spid175 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 59906 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:23.48 spid478 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 13515 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:47.55 spid69 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 24047 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:49.81 spid875 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 2265 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:03:12.64 spid168 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 22829 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> The database is about 2.7 gb, and the autogrow is set for 10%. So it was
> trying to add maybe 300 mb, but it kept timing out. I could understand it
> being an issue for a larger number, but 300 mb is not very much.
> When the alter database add filespace happens, is the entire database
> inaccessible during that time? Or is it just the space it is adding that
is
> inaccessible?
> I am wondering if the autogrow timeouts and the user timeouts had the same
> thing happening to make them timeout. Or if the autogrow attempts were
> causing the user timeouts. Seems that cpu on the server were normal, and
no
> other databases had complaints of slows. The autogrow attempts kept
> happening for about an hour and a half before it was succesful. Please help![/vbc
ol]
?
We have a shared server where users in one database got timeouts. Looking
back at the logs, the database was trying to grow during that time frame, bu
t
it timed out. Please see part of log:
2006-10-17 15:00:32.97 spid622 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 15922 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:00:44.41 spid168 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 11390 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:00:46.14 spid460 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 1672 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:05.19 spid745 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 18968 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:05.62 spid478 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 406 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:10.03 spid213 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 4390 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:09.95 spid175 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 59906 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:23.48 spid478 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 13515 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:47.55 spid69 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 24047 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:49.81 spid875 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 2265 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:03:12.64 spid168 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 22829 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
The database is about 2.7 gb, and the autogrow is set for 10%. So it was
trying to add maybe 300 mb, but it kept timing out. I could understand it
being an issue for a larger number, but 300 mb is not very much.
When the alter database add filespace happens, is the entire database
inaccessible during that time? Or is it just the space it is adding that is
inaccessible?
I am wondering if the autogrow timeouts and the user timeouts had the same
thing happening to make them timeout. Or if the autogrow attempts were
causing the user timeouts. Seems that cpu on the server were normal, and no
other databases had complaints of slows. The autogrow attempts kept
happening for about an hour and a half before it was succesful. Please help
!Below are two KB about the issue:
http://support.microsoft.com/kb/315512/
INF: Considerations for Autogrow and Autoshrink configuration in SQL
Server
http://support.microsoft.com/kb/305635/
PRB: A Timeout Occurs When a Database Is Automatically Expanding
Mitch wrote:[vbcol=seagreen]
> Hello - Can anyone direct me to good articles on Alter database and Autogr
ow?
> We have a shared server where users in one database got timeouts. Lookin
g
> back at the logs, the database was trying to grow during that time frame,
but
> it timed out. Please see part of log:
> 2006-10-17 15:00:32.97 spid622 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 15922 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:00:44.41 spid168 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 11390 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:00:46.14 spid460 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 1672 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:05.19 spid745 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 18968 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:05.62 spid478 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 406 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:10.03 spid213 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 4390 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:09.95 spid175 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 59906 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:23.48 spid478 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 13515 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:47.55 spid69 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 24047 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:49.81 spid875 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 2265 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:03:12.64 spid168 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 22829 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> The database is about 2.7 gb, and the autogrow is set for 10%. So it was
> trying to add maybe 300 mb, but it kept timing out. I could understand it
> being an issue for a larger number, but 300 mb is not very much.
> When the alter database add filespace happens, is the entire database
> inaccessible during that time? Or is it just the space it is adding that
is
> inaccessible?
> I am wondering if the autogrow timeouts and the user timeouts had the same
> thing happening to make them timeout. Or if the autogrow attempts were
> causing the user timeouts. Seems that cpu on the server were normal, and
no
> other databases had complaints of slows. The autogrow attempts kept
> happening for about an hour and a half before it was succesful. Please help![/vbc
ol]
Autogrow Timeouts
Hello - Can anyone direct me to good articles on Alter database and Autogrow?
We have a shared server where users in one database got timeouts. Looking
back at the logs, the database was trying to grow during that time frame, but
it timed out. Please see part of log:
2006-10-17 15:00:32.97 spid622 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 15922 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:00:44.41 spid168 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 11390 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:00:46.14 spid460 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 1672 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:05.19 spid745 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 18968 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:05.62 spid478 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 406 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:10.03 spid213 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 4390 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:09.95 spid175 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 59906 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:23.48 spid478 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 13515 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:47.55 spid69 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 24047 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:49.81 spid875 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 2265 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:03:12.64 spid168 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 22829 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
The database is about 2.7 gb, and the autogrow is set for 10%. So it was
trying to add maybe 300 mb, but it kept timing out. I could understand it
being an issue for a larger number, but 300 mb is not very much.
When the alter database add filespace happens, is the entire database
inaccessible during that time? Or is it just the space it is adding that is
inaccessible?
I am wondering if the autogrow timeouts and the user timeouts had the same
thing happening to make them timeout. Or if the autogrow attempts were
causing the user timeouts. Seems that cpu on the server were normal, and no
other databases had complaints of slows. The autogrow attempts kept
happening for about an hour and a half before it was succesful. Please help!Below are two KB about the issue:
http://support.microsoft.com/kb/315512/
INF: Considerations for Autogrow and Autoshrink configuration in SQL
Server
http://support.microsoft.com/kb/305635/
PRB: A Timeout Occurs When a Database Is Automatically Expanding
Mitch wrote:
> Hello - Can anyone direct me to good articles on Alter database and Autogrow?
> We have a shared server where users in one database got timeouts. Looking
> back at the logs, the database was trying to grow during that time frame, but
> it timed out. Please see part of log:
> 2006-10-17 15:00:32.97 spid622 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 15922 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:00:44.41 spid168 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 11390 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:00:46.14 spid460 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 1672 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:05.19 spid745 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 18968 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:05.62 spid478 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 406 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:10.03 spid213 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 4390 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:09.95 spid175 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 59906 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:23.48 spid478 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 13515 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:47.55 spid69 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 24047 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:49.81 spid875 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 2265 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:03:12.64 spid168 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 22829 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> The database is about 2.7 gb, and the autogrow is set for 10%. So it was
> trying to add maybe 300 mb, but it kept timing out. I could understand it
> being an issue for a larger number, but 300 mb is not very much.
> When the alter database add filespace happens, is the entire database
> inaccessible during that time? Or is it just the space it is adding that is
> inaccessible?
> I am wondering if the autogrow timeouts and the user timeouts had the same
> thing happening to make them timeout. Or if the autogrow attempts were
> causing the user timeouts. Seems that cpu on the server were normal, and no
> other databases had complaints of slows. The autogrow attempts kept
> happening for about an hour and a half before it was succesful. Please help!
We have a shared server where users in one database got timeouts. Looking
back at the logs, the database was trying to grow during that time frame, but
it timed out. Please see part of log:
2006-10-17 15:00:32.97 spid622 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 15922 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:00:44.41 spid168 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 11390 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:00:46.14 spid460 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 1672 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:05.19 spid745 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 18968 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:05.62 spid478 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 406 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:01:10.03 spid213 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 4390 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:09.95 spid175 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 59906 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:23.48 spid478 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 13515 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:47.55 spid69 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 24047 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:02:49.81 spid875 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 2265 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
2006-10-17 15:03:12.64 spid168 Autogrow of file 'SCHR_Data' in database
'SCHR' cancelled or timed out after 22829 ms. Use ALTER DATABASE to set a
smaller FILEGROWTH or to set a new size.
The database is about 2.7 gb, and the autogrow is set for 10%. So it was
trying to add maybe 300 mb, but it kept timing out. I could understand it
being an issue for a larger number, but 300 mb is not very much.
When the alter database add filespace happens, is the entire database
inaccessible during that time? Or is it just the space it is adding that is
inaccessible?
I am wondering if the autogrow timeouts and the user timeouts had the same
thing happening to make them timeout. Or if the autogrow attempts were
causing the user timeouts. Seems that cpu on the server were normal, and no
other databases had complaints of slows. The autogrow attempts kept
happening for about an hour and a half before it was succesful. Please help!Below are two KB about the issue:
http://support.microsoft.com/kb/315512/
INF: Considerations for Autogrow and Autoshrink configuration in SQL
Server
http://support.microsoft.com/kb/305635/
PRB: A Timeout Occurs When a Database Is Automatically Expanding
Mitch wrote:
> Hello - Can anyone direct me to good articles on Alter database and Autogrow?
> We have a shared server where users in one database got timeouts. Looking
> back at the logs, the database was trying to grow during that time frame, but
> it timed out. Please see part of log:
> 2006-10-17 15:00:32.97 spid622 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 15922 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:00:44.41 spid168 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 11390 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:00:46.14 spid460 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 1672 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:05.19 spid745 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 18968 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:05.62 spid478 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 406 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:01:10.03 spid213 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 4390 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:09.95 spid175 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 59906 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:23.48 spid478 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 13515 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:47.55 spid69 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 24047 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:02:49.81 spid875 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 2265 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> 2006-10-17 15:03:12.64 spid168 Autogrow of file 'SCHR_Data' in database
> 'SCHR' cancelled or timed out after 22829 ms. Use ALTER DATABASE to set a
> smaller FILEGROWTH or to set a new size.
> The database is about 2.7 gb, and the autogrow is set for 10%. So it was
> trying to add maybe 300 mb, but it kept timing out. I could understand it
> being an issue for a larger number, but 300 mb is not very much.
> When the alter database add filespace happens, is the entire database
> inaccessible during that time? Or is it just the space it is adding that is
> inaccessible?
> I am wondering if the autogrow timeouts and the user timeouts had the same
> thing happening to make them timeout. Or if the autogrow attempts were
> causing the user timeouts. Seems that cpu on the server were normal, and no
> other databases had complaints of slows. The autogrow attempts kept
> happening for about an hour and a half before it was succesful. Please help!
Subscribe to:
Comments (Atom)