Windows Server

Todd Ouimet · Guest

I'm getting the following error. I do have the OnePoint db set to autogrow.
Why is that an issue? Thanks Todd

Severity: Warning
Maintenance Mode: False
Domain:
Computer: MOM2005
Time Last Modified: 10/20/2005 11:15:00 AM
Resolution State: New
Time in State: 10/13/2005 9:15:00 PM
Problem State: 3
Repeat Count: 324
Name: MOM Database is set to Autogrow
Source: Microsoft Operations Manager
Ticket Id:
Owner:
Description: The following filegroup:file combinations in the MOM Database
in the SQL Server instance MOM2005 are set to autogrow:

PRIMARY:EEA_DATA

The MOM Database should not have any files set to autogrow.

Microsoft MVP ¾¤¹ÅÀs for · Guest

Hello,

Thank you for your posting!

Causes

The specified filegroup has run out of free space.

Resolutions

To gain more space, you can free disk space on any disk drive

containing a file in the full filegroup, allowing files in the group to

grow. Or you can gain space using a data file with the specified database.

Freeing disk space

You can free disk space on your local drive or on another disk drive.

To free disk space on another drive:

1.. Move the data files in the filegroup with an insufficient amount

of free disk space to a different disk drive.

2.. Detach the database by executing sp_detach_db.

3.. Attach the database by executing sp_attach_db, pointing to the

moved files.

Using a data file

Another solution is to add a data file to the specified database using

the ADD FILE clause of the ALTER DATABASE statement. Or you can enlarge the

data file by using the MODIFY FILE clause of the ALTER DATABASE statement,

specifying the SIZE and MAXSIZE syntax.

If you have any questions, please feel to let me know. I am glad to be of
assistance.

--
Daniel Lai
Microsoft MVP Program Top Contributor
Windows Server-Management Infrastructure
Microsoft Management Solution Consultant

"Todd Ouimet" <touimet@[NO-SPAM]kishmish.com> wrote in message
news:%23H4b$lY1FHA.1256@TK2MSFTNGP09.phx.gbl...

Todd Ouimet · Guest

Okay so the concern is only that the OnePoint Db will overgrow the size of
the disk, correct?

Thanks!!!

"Microsoft MVP ¾¤¹ÅÀs for Windows Server" <laigarry@hotmail.com> wrote in
message news:eaDPDtY1FHA.1252@TK2MSFTNGP09.phx.gbl...

davidtyra@hotmail.com · Guest

Todd,

The Onepoint database should not be set to autogrow because database
operations are suspended while automatic growing is taking place. This
would cause database updates to fail. Since the Onepoint database is
being written to almost continuously, it would be very sensitive to any
suspension of database operations. The Reporting database, on the other
hand, is only written to by the DTS job so it is a better candidate for
automatic growth.

Regards,

David Tyra

Justin Gould · Guest

Autogrow on SystemCenterReporting is also a bad idea. If autogrow initiates
in the middle of a DTS job (which it always will), DTS may hold onto table
locks in OnePoint until it can complete the transaction that triggered the
expansion operation. This could cause insert failures in OnePoint.

Autogrowth is generally a bad practice on any MOM DB. The sizes of OnePoint
and SystemCenterReporting both need regular monitoring to ensure that the
system is operating properly, for capacity planning, etc.

Justin

"davidtyra@hotmail.com" wrote:

The Reporting database, on the other

Justin Gould · Guest

In additon to the DB locking issues David mentions, there is also a concern
that OnePoint will overgrow its supported size (30GB). The actual size you
need will depend on the MPs you have loaded, but our DB is at about 10GB with
650 servers and 20 management packs.

A ballooning OnePoint can also be a sign of trouble. For instance, our
OnePoint grew to 30GB because a single server was generating 60 WINS
events/second (30,000,000 events/week!), dragging the DB down. If your
OnePoint size does not level off well under 30GB, make sure that you have MOM
Reporting installed and configured, and that the reporting DTS transfer and
MOM grooming (MOMX Partitioning and Grooming SQL job) are running properly.
If this is all working, run a Most Common Events by Computer report to see if
you have any big talkers.

Justin

"Todd Ouimet" wrote:

davidtyra@hotmail.com · Guest

Very good points. We don't use autogrow on any of our MOM databases. I
have just seen customers do that in the past. It would certainly not be
a best practice for the reasons that you mention.

David

Todd Ouimet · Guest

Okay, great points!! So now what shoudl I do. I created the database as
only a 1GB database. I've already outgrown it. It is as simple as going
into the SQL Ent Manager and changing the Space allocated on both databases?

Thanks,
Todd

<davidtyra@hotmail.com> wrote in message
news:1129915342.996554.245520@g44g2000cwa.googlegroups.com...

Arie de Haan · Guest

Todd,

Daniel Lai was not correct, see the post from David Tyra, that is the
correct reason.
So.. no the concern isn't that the OnePoint DB will overgrow.

In article <eR5LI5Y1FHA.3892@TK2MSFTNGP12.phx.gbl>, touimet@[NO-SPAM]
kishmish.com says...

waasvlk · Guest

Since Autogrow should not be enabled on MOM databases, there should be a way
to notify in advance, before Onepoint DB or SystemCenterReporting DB run out
of space completely.

I cannot find any rule to be used for notifying MOM administrators in
advance, if Onepoint and SystemCenterReporting databases have less than a
specified threshold of space available (as displayed in SQL Enterprise
Manager). Am I missing something ?

We are using MOM2005 SP1 with latest versions of MOM MP (version
05.0.3100.0000) and SQL MP (version 05.0.3100.0000)

Thanks & regards
Volker

"davidtyra@hotmail.com" wrote:

waasvlk · Guest

o.k., I found the rule that does what I want:

Microsoft SQL Server\SQL Server 2000\State Monitoring and Service
Discovery\SQL Server Space Analysis

However, this rule seems to raise false alert notifications like this,
although our SystemCenterReporting database has more than 28000 MB of free
space available:

"Database space for "SystemCenterReporting" in instance "MSSQLSERVER" has
less than the Error threshold of 100MB free space. The database currently has
-681.18MB free space. It is recommended database files for a database have
more than 100MB of free space, taking into account growth potential."

Volker

"waasvlk" wrote:

	Windows Server Forum Index -> MOM	All times are GMT
Page 1 of 1