InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 05:54:24 GMT20http://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspx[quote][b]MyDoggieJessie (11/29/2012)[/b][hr]If you create a custom alert for SQL Error # 1101 or 1105 (not sure exactly which is which, you can Google that) it will send you an alert should your data file become full and it is unable to grow [/quote] in this case DBA will reactively respond there (DIsk is full now what to do :w00t:) , but here person should be informed proactively.Sun, 02 Dec 2012 23:51:59 GMTBhuvneshhttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspxIf you create a custom alert for SQL Error # 1101 or 1105 (not sure exactly which is which, you can Google that) it will send you an alert should your data file become full and it is unable to grow Thu, 29 Nov 2012 11:29:36 GMTMyDoggieJessiehttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspxThanks, we do have sql agent alerts setup, I wonder if it is the Severity 17- insufficient resources that does the work?I never got the alert because we have a diskspace check job so I can take care of the space proactively.But just wonder it is the above insufficient resources alert will be triggered if there is no enough file space for mdf file and ldf file.Thanks,Thu, 29 Nov 2012 11:13:39 GMTsqlfriendshttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspxThere are many SQL Server Events, SQL Performance Condition Alerts, as well as WMI Events that can be set up rather easily under SQL Server Agent >> Alerts. Settings up these alerts gives you the option to specify a response i.e. (notify a particular operator), and additionally specify if you want to Email, Page, or netsend the event should one occur.These are free :-PThu, 29 Nov 2012 11:08:28 GMTMyDoggieJessiehttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspx[quote][b]sqlfriends (11/29/2012)[/b][hr]So, it doesnot send any kind of alerts to DBA proactively?[/quote]If you've configured alerts, you get alerts. If not, you don't (how would SQL intuit who to send alerts to?)Thu, 29 Nov 2012 10:53:40 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspxI wasn't aware that SQL Server on it's own EVER sent anything to the DBA proactively. All monitoring has to be built or bought.Thu, 29 Nov 2012 10:50:31 GMTGrant Fritcheyhttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspxSo, it doesnot send any kind of alerts to DBA proactively?Thu, 29 Nov 2012 10:46:43 GMTsqlfriendshttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspxYes & no. It just stops allowing writes. You get errors. Reads work fine. All writes stop because there's nowhere for them to go.Thu, 29 Nov 2012 10:02:19 GMTGrant Fritcheyhttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspxThanks, currently we do have own DiskspaceCheck sql job to monitor the disk space.So we set it to unrestricted.But I see some people are using restricted method.I am curious if it is set to restricted size and if it is full, what will happen, does it generate any errors or an alert and notifiy DBA, how is this alert set up?You said the database will become to readonly, is it automatically change it readonly mode?ThanksThu, 29 Nov 2012 09:51:00 GMTsqlfriendshttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspxPersonally, unrestricted with lots and lots and lots of monitoring and alerts in place so that I can try to prevent the disks from filling up. Either approach has downsides. If you restrict the growth, you avoid filling the drive, but, you put a database into read only mode. Depending on the database in your system, that could be a resume generating event.Thu, 29 Nov 2012 05:46:32 GMTGrant Fritcheyhttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspxI found this interesting KB article [url=http://support.microsoft.com/kb/315512]Considerations for the "autogrow" and "autoshrink" settings in SQL Server[/url]..Wed, 28 Nov 2012 21:22:58 GMTprettsonshttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspxReasoning for wanted to limit frequent file growth is because of the contention created by having to grow the data/log files on the disk(s). It's often best to choose an appropriate size in advance to minimize this growth, if the file does have to grown, consider choosing a large enough size in MB's so that it won't have to do it again.Wed, 28 Nov 2012 20:13:51 GMTMyDoggieJessiehttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspxIf you have the ability to receive alerts when disk space is getting low, then unrestricted growth makes sense.On the other hand, you don't want one out-of-control database to create problems for other databases on a shared server, so for some environments it makes sense to set a restricted size and monitor file usage carefully.Personally I receive alerts when a filegroup is getting full, and also when an autogrowth has occurred, so I get plenty of advance warning of potential space problems.Wed, 28 Nov 2012 12:24:09 GMTRichard Fryarhttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspxPersonally, unrestricted with warnings that watch the drive(s) itself for space issues.Wed, 28 Nov 2012 12:17:07 GMTEvil Kraig Fhttp://www.sqlservercentral.com/Forums/Topic1390047-1550-1.aspxI would like to know as a dba practice, do you setup the autogrow for file size to a restricted file growth or unrestricted file growth.ThanksWed, 28 Nov 2012 12:09:59 GMTsqlfriends