Hi I'm getting the following error on an maintanence plan that Optimizes the
database.
Error 1105:[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1105:
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocat
e
space for object '(SYSTEM table id: -21614735)' in database 'itiserver'
because the
'ITEMDATAI' filegroup is full.
I have "Reorganize data and index pages", "Change free space percentage per
page to 10 percent" checked off.
"Remove unused space is not checked"
I have plenty of room to grow on this file, can anyone give me some pointers
to get pass this issue.The first thing would be to ensure this particle file is on the drive you
believe it to be. But I would manually grow the file instead of letting
autogrow kick in and that should take care of it. You should always have
plenty of free space int he DB files anyway so you may want to address all
of them. Never rely on Autogrow.
Andrew J. Kelly SQL MVP
"robert_at_cbb" <robertatcbb@.discussions.microsoft.com> wrote in message
news:382B64D2-6150-4572-A99E-6BB47B3ECF9C@.microsoft.com...
> Hi I'm getting the following error on an maintanence plan that Optimizes
the
> database.
> Error 1105:[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1105:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not alloc
ate
> space for object '(SYSTEM table id: -21614735)' in database 'itiserver'
> because the
> 'ITEMDATAI' filegroup is full.
> I have "Reorganize data and index pages", "Change free space percentage
per
> page to 10 percent" checked off.
> "Remove unused space is not checked"
> I have plenty of room to grow on this file, can anyone give me some
pointers
> to get pass this issue.
>|||Thanks, when you say manually grow the file are you refering to the database
properties, auto grow, max file size? I have the auto grow set to grow by
600mb and the max size restricted to 26000gb, its at 21000 right now. So how
do I manually grow the file, do I increase the restricted max?
"Andrew J. Kelly" wrote:
> The first thing would be to ensure this particle file is on the drive you
> believe it to be. But I would manually grow the file instead of letting
> autogrow kick in and that should take care of it. You should always have
> plenty of free space int he DB files anyway so you may want to address all
> of them. Never rely on Autogrow.
> --
> Andrew J. Kelly SQL MVP
>
> "robert_at_cbb" <robertatcbb@.discussions.microsoft.com> wrote in message
> news:382B64D2-6150-4572-A99E-6BB47B3ECF9C@.microsoft.com...
> the
> per
> pointers
>
>|||By manually grow I mean either use the command ALTER DATABASE like:
ALTER DATABASE Test1
MODIFY FILE
(NAME = test1dat3,
SIZE = 20MB)
or use EM and change the size of the file in the properties dialog where it
shows the actual file size. The Max file size is how large it can grow
before it stops growing. This way you can control when and how the file
grows. But ideally you want to make it as large as you will need for quite
some time and then you won't have to worry about it growing<g>.
Andrew J. Kelly SQL MVP
"robert_at_cbb" <robertatcbb@.discussions.microsoft.com> wrote in message
news:C3F2DC9E-B1B6-43EC-A2A1-08D114B13CEF@.microsoft.com...
> Thanks, when you say manually grow the file are you refering to the
database
> properties, auto grow, max file size? I have the auto grow set to grow by
> 600mb and the max size restricted to 26000gb, its at 21000 right now. So
how[vbcol=seagreen]
> do I manually grow the file, do I increase the restricted max?
> "Andrew J. Kelly" wrote:
>
you[vbcol=seagreen]
have[vbcol=seagreen]
all[vbcol=seagreen]
Optimizes[vbcol=seagreen]
'itiserver'[vbcol=seagreen]
percentage[vbcol=seagreen]
Saturday, February 25, 2012
Maintenance Plans
Labels:
110591microsoft,
database,
error,
following,
maintanence,
maintenance,
microsoft,
mysql,
odbc,
optimizes,
oracle,
plan,
plans,
server,
sql,
sql-dmo,
sqlstate,
thedatabase
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment