Dear all,
I get the following error when restore database :
Modify File encountered operating system error 112(There is not enough space
on the disk) while attempting to expand the physical file.
Can anyone tell me how I can overcome this problem ?
Thx.The error is very spcific - you don't have enough space on the disk.
You can delete some files in order to make more space on the disk or
restore the database to a different disk.
Adi
Vensia wrote:
> Dear all,
> I get the following error when restore database :
> Modify File encountered operating system error 112(There is not enough space
> on the disk) while attempting to expand the physical file.
> Can anyone tell me how I can overcome this problem ?
> Thx.|||Hello,
The Restore Database command will create a identical MDF and LDF which is
same as source database. So ensure that
you have enough space in physical hard drives you are going to restore.
Otherwise identify the right drives with space and
restore in that location.
Thanks
Hari
"Vensia" <vensia2000_nospam@.yahoo.com> wrote in message
news:%23XphYUhPHHA.1248@.TK2MSFTNGP02.phx.gbl...
> Dear all,
> I get the following error when restore database :
> Modify File encountered operating system error 112(There is not enough
> space
> on the disk) while attempting to expand the physical file.
> Can anyone tell me how I can overcome this problem ?
> Thx.
>|||Vensia wrote:
> Dear all,
> I get the following error when restore database :
> Modify File encountered operating system error 112(There is not enough space
> on the disk) while attempting to expand the physical file.
> Can anyone tell me how I can overcome this problem ?
> Thx.
>
Which part of "There is not enough space on the disk) while attempting
to expand the physical file" is unclear?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
Showing posts with label space. Show all posts
Showing posts with label space. Show all posts
Monday, March 19, 2012
Sunday, March 11, 2012
Error In Replace With Spaces
Hi !
I'm trying to put a space after . and , in varchar fields.
I've tried
UPDATE Resultados
SET RespuestaAbierta = REPLACE(RespuestaAbierta, ',', ', ')
but nothing happened
What's wrong ??
Thanks and sorry if my english isnt so good.
Eduardo (from Argentina)This works fine for me:
drop table test2
create table test2(f1 varchar(1000))
insert test2 select '1,2,3,4,5,6,7'
select REPLACE(f1, ',', ', ') from test2
update test2 set f1=REPLACE(f1, ',', ', ')
select * from test2|||It seems to work fine for me, using:SELECT Replace('1,2,3,4,5,6,7,8,9', ',', ', ')Maybe the character you are looking for only looks like it is a comma.
-PatP|||Trabajos para m
DECLARE @.RespuestaAbierta varchar(50)
SELECT @.RespuestaAbierta = 'Brett,Kaiser'
SELECT REPLACE(@.RespuestaAbierta, ',', ', ')|||I can't understand,
this works fine ...
drop table test2
create table test2(f1 varchar(4000))
insert test2 select '1,2,3,4,5,6,7'
insert test2 select 'ninguna en especial,me la recomendo mi hermano.'
select REPLACE(f1, ',', ', ') from test2
update test2 set f1=REPLACE(f1, ',', ', ')
select * from test2
1, 2, 3, 4, 5, 6, 7
ninguna en especial, me la recomendo mi hermano.
but this one doesn't
select respuestaabierta,
REPLACE(respuestaabierta, ',', ', ')
from resultados
where idresultado = 1244591
ninguna en especial,me la recomendo mi hermano. ninguna en especial,me la recomendo mi hermano.
The field respuestaabierta is varchar(4000) null
Thanks for your answers !|||I remeber...the answer is that the comma in your column is not a comma!
That bugged us for a while once...
select char(130), ascii(',')
Do This
DECLARE @.x varchar(80)
SELECT @.x = 'This is not a comma' + CHAR(130) + ' even though it looks like one'
SELECT @.x
-- Then do
select CHARINDEX(CHAR(130),respuestaabierta)
from resultados
where idresultado = 1244591
-- If it's not 0, then that's what it is...
And let us know...|||Thanks, Brett
but that's not the problem :
select CHARINDEX(CHAR(130),respuestaabierta) , CHARINDEX(CHAR(44),respuestaabierta)
from resultados
where idresultado = 1244591
Output:
0 20
I've noticed that the table has
Collation = SQL_Latin1_General_CP1_CI_AS
and, with Collation = databasedefault works fine
what does it mean ?
Thanks|||Damn...I thought that might have been it...
Can you post the DDL of your table?
Do you know how to do that in Enterprise manager?|||Bred,
thanks for everything, I gave up
I did a stored procedure wich updates row by row (instead a single update command).
Thanks again. Eduardo (from Argentina)|||Too bad...I was gonna suggest that you find the position and say
SELECT ASCII(SUBSTRING(col1,n,1))
to see what the damn thing was...
what code did you use?
I'm trying to put a space after . and , in varchar fields.
I've tried
UPDATE Resultados
SET RespuestaAbierta = REPLACE(RespuestaAbierta, ',', ', ')
but nothing happened
What's wrong ??
Thanks and sorry if my english isnt so good.
Eduardo (from Argentina)This works fine for me:
drop table test2
create table test2(f1 varchar(1000))
insert test2 select '1,2,3,4,5,6,7'
select REPLACE(f1, ',', ', ') from test2
update test2 set f1=REPLACE(f1, ',', ', ')
select * from test2|||It seems to work fine for me, using:SELECT Replace('1,2,3,4,5,6,7,8,9', ',', ', ')Maybe the character you are looking for only looks like it is a comma.
-PatP|||Trabajos para m
DECLARE @.RespuestaAbierta varchar(50)
SELECT @.RespuestaAbierta = 'Brett,Kaiser'
SELECT REPLACE(@.RespuestaAbierta, ',', ', ')|||I can't understand,
this works fine ...
drop table test2
create table test2(f1 varchar(4000))
insert test2 select '1,2,3,4,5,6,7'
insert test2 select 'ninguna en especial,me la recomendo mi hermano.'
select REPLACE(f1, ',', ', ') from test2
update test2 set f1=REPLACE(f1, ',', ', ')
select * from test2
1, 2, 3, 4, 5, 6, 7
ninguna en especial, me la recomendo mi hermano.
but this one doesn't
select respuestaabierta,
REPLACE(respuestaabierta, ',', ', ')
from resultados
where idresultado = 1244591
ninguna en especial,me la recomendo mi hermano. ninguna en especial,me la recomendo mi hermano.
The field respuestaabierta is varchar(4000) null
Thanks for your answers !|||I remeber...the answer is that the comma in your column is not a comma!
That bugged us for a while once...
select char(130), ascii(',')
Do This
DECLARE @.x varchar(80)
SELECT @.x = 'This is not a comma' + CHAR(130) + ' even though it looks like one'
SELECT @.x
-- Then do
select CHARINDEX(CHAR(130),respuestaabierta)
from resultados
where idresultado = 1244591
-- If it's not 0, then that's what it is...
And let us know...|||Thanks, Brett
but that's not the problem :
select CHARINDEX(CHAR(130),respuestaabierta) , CHARINDEX(CHAR(44),respuestaabierta)
from resultados
where idresultado = 1244591
Output:
0 20
I've noticed that the table has
Collation = SQL_Latin1_General_CP1_CI_AS
and, with Collation = databasedefault works fine
what does it mean ?
Thanks|||Damn...I thought that might have been it...
Can you post the DDL of your table?
Do you know how to do that in Enterprise manager?|||Bred,
thanks for everything, I gave up
I did a stored procedure wich updates row by row (instead a single update command).
Thanks again. Eduardo (from Argentina)|||Too bad...I was gonna suggest that you find the position and say
SELECT ASCII(SUBSTRING(col1,n,1))
to see what the damn thing was...
what code did you use?
Friday, March 9, 2012
Error in Maintenance Plan (tempdb)
Hello
Give this error in Maintenance Plan:
8] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002:
[Microsoft][ODBC SQL Server Driver][SQL Server]The log file for
database
'tempdb' is full. Back up the transaction log for the database to free up
some log space.
End of maintenance plan 'DB Maintenance Plan openview' on 13-07-2006 0:00:22
SQLMAINT.EXE Process Exit Code: 1 (Failed)
What should I do?
Regards
José Júlio DuarteYou need to clear the tempdb, There are few methods by which you can do
this
http://support.microsoft.com/defaul...kb;en-us;307487
"Jos Jlio Duarte" <JosJlioDuarte@.discussions.microsoft.com> wrote in
message news:59EC2548-AAB9-4456-9001-B326BC9756D4@.microsoft.com...
> Hello
> Give this error in Maintenance Plan:
> 8] Database openview: Removing unused space from the database files (if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002:
> [Microsoft][ODBC SQL Server Driver][SQL Server]The log file fo
r database
> 'tempdb' is full. Back up the transaction log for the database to free up
> some log space.
> End of maintenance plan 'DB Maintenance Plan openview' on 13-07-2006
0:00:22
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>
> What should I do?
> Regards
> Jos Jlio Duarte
Give this error in Maintenance Plan:
8] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002:
[Microsoft][ODBC SQL Server Driver][SQL Server]The log file for
database
'tempdb' is full. Back up the transaction log for the database to free up
some log space.
End of maintenance plan 'DB Maintenance Plan openview' on 13-07-2006 0:00:22
SQLMAINT.EXE Process Exit Code: 1 (Failed)
What should I do?
Regards
José Júlio DuarteYou need to clear the tempdb, There are few methods by which you can do
this
http://support.microsoft.com/defaul...kb;en-us;307487
"Jos Jlio Duarte" <JosJlioDuarte@.discussions.microsoft.com> wrote in
message news:59EC2548-AAB9-4456-9001-B326BC9756D4@.microsoft.com...
> Hello
> Give this error in Maintenance Plan:
> 8] Database openview: Removing unused space from the database files (if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002:
> [Microsoft][ODBC SQL Server Driver][SQL Server]The log file fo
r database
> 'tempdb' is full. Back up the transaction log for the database to free up
> some log space.
> End of maintenance plan 'DB Maintenance Plan openview' on 13-07-2006
0:00:22
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>
> What should I do?
> Regards
> Jos Jlio Duarte
Error in Maintenance Plan (tempdb)
Hello
Give this error in Maintenance Plan:
8] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002:
[Microsoft][ODBC SQL Server Driver][SQL Server]The log file for database
'tempdb' is full. Back up the transaction log for the database to free up
some log space.
End of maintenance plan 'DB Maintenance Plan openview' on 13-07-2006 0:00:22
SQLMAINT.EXE Process Exit Code: 1 (Failed)
What should I do?
Regards
José Júlio DuarteYou need to clear the tempdb, There are few methods by which you can do
this
http://support.microsoft.com/default.aspx?scid=kb;en-us;307487
"José Júlio Duarte" <JosJlioDuarte@.discussions.microsoft.com> wrote in
message news:59EC2548-AAB9-4456-9001-B326BC9756D4@.microsoft.com...
> Hello
> Give this error in Maintenance Plan:
> 8] Database openview: Removing unused space from the database files (if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002:
> [Microsoft][ODBC SQL Server Driver][SQL Server]The log file for database
> 'tempdb' is full. Back up the transaction log for the database to free up
> some log space.
> End of maintenance plan 'DB Maintenance Plan openview' on 13-07-2006
0:00:22
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>
> What should I do?
> Regards
> José Júlio Duarte
Give this error in Maintenance Plan:
8] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002:
[Microsoft][ODBC SQL Server Driver][SQL Server]The log file for database
'tempdb' is full. Back up the transaction log for the database to free up
some log space.
End of maintenance plan 'DB Maintenance Plan openview' on 13-07-2006 0:00:22
SQLMAINT.EXE Process Exit Code: 1 (Failed)
What should I do?
Regards
José Júlio DuarteYou need to clear the tempdb, There are few methods by which you can do
this
http://support.microsoft.com/default.aspx?scid=kb;en-us;307487
"José Júlio Duarte" <JosJlioDuarte@.discussions.microsoft.com> wrote in
message news:59EC2548-AAB9-4456-9001-B326BC9756D4@.microsoft.com...
> Hello
> Give this error in Maintenance Plan:
> 8] Database openview: Removing unused space from the database files (if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002:
> [Microsoft][ODBC SQL Server Driver][SQL Server]The log file for database
> 'tempdb' is full. Back up the transaction log for the database to free up
> some log space.
> End of maintenance plan 'DB Maintenance Plan openview' on 13-07-2006
0:00:22
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>
> What should I do?
> Regards
> José Júlio Duarte
Error in Maintenance Plan (one of database)
Hello
When i execute the Maintenance Plan,
Database Maintenance Plan (Optimization):
(Check) Remove unused space from database files
Shrink database when it grows beyonds: 50 MB
Amount of free space to remain after shrink: 10 % of data space
Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
Sucess
[1] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan openview Optimization' on
13-07-2006 15:04:00
SQLMAINT.EXE Process Exit Code: 0 (Success)
************************************************************
but when i add this,
Database Maintenance Plan (Optimization):
(Check) Reorganize data and index pages
with
Reorganize pages with the original amount of free space
or
Change free space per page percentage to 10 %
(Check) Remove unused space from database files
Shrink database when it grows beyonds: 50 MB
Amount of free space to remain after shrink: 10 % of data space
Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
Failed - error
[1] Database openview: Index Rebuild (leaving 100%% free space)...
Rebuilding indexes for table 'OV_MS_Annotation'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002: [Microsoft][ODBC SQL
Server Driver][SQL Server]The log file for database 'openview' is full. Back
up the transaction log for the database to free up some log space.
[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
terminated.
** Execution Time: 0 hrs, 0 mins, 2 secs **
[2] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan openview Optimization' on
13-07-2006 15:03:02
SQLMAINT.EXE Process Exit Code: 1 (Failed)
Will it be that it doesn't let to execute everything in the same maintenance
Plan?
Regards,
José Júlio DuarteJosé Júlio Duarte wrote:
> Hello
> When i execute the Maintenance Plan,
> Database Maintenance Plan (Optimization):
> (Check) Remove unused space from database files
> Shrink database when it grows beyonds: 50 MB
> Amount of free space to remain after shrink: 10 % of data space
> Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> Sucess
> [1] Database openview: Removing unused space from the database files (if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Deleting old text reports... 0 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> 13-07-2006 15:04:00
> SQLMAINT.EXE Process Exit Code: 0 (Success)
> ************************************************************
> but when i add this,
> Database Maintenance Plan (Optimization):
> (Check) Reorganize data and index pages
> with
> Reorganize pages with the original amount of free space
> or
> Change free space per page percentage to 10 %
>
> (Check) Remove unused space from database files
> Shrink database when it grows beyonds: 50 MB
> Amount of free space to remain after shrink: 10 % of data space
> Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> Failed - error
> [1] Database openview: Index Rebuild (leaving 100%% free space)...
> Rebuilding indexes for table 'OV_MS_Annotation'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002: [Microsoft][ODBC SQL
> Server Driver][SQL Server]The log file for database 'openview' is full. Back
> up the transaction log for the database to free up some log space.
> [Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
> terminated.
> ** Execution Time: 0 hrs, 0 mins, 2 secs **
> [2] Database openview: Removing unused space from the database files (if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Deleting old text reports... 0 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> 13-07-2006 15:03:02
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> Will it be that it doesn't let to execute everything in the same maintenance
> Plan?
>
> Regards,
> José Júlio Duarte
>
Reindexing generates a log of transaction log activity, and your
transaction log isn't big enough to handle the volume. Exactly what the
error message says.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hello Tracy
Where can i change to resolve this? and how?
Regards
"Tracy McKibben" wrote:
> José Júlio Duarte wrote:
> > Hello
> >
> > When i execute the Maintenance Plan,
> >
> > Database Maintenance Plan (Optimization):
> >
> > (Check) Remove unused space from database files
> > Shrink database when it grows beyonds: 50 MB
> > Amount of free space to remain after shrink: 10 % of data space
> > Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> >
> > Sucess
> >
> > [1] Database openview: Removing unused space from the database files (if
> > database size is more than 50 MB). Reducing free space to 10 percent of
> > data...
> > ** Execution Time: 0 hrs, 0 mins, 1 secs **
> >
> > Deleting old text reports... 0 file(s) deleted.
> >
> > End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> > 13-07-2006 15:04:00
> > SQLMAINT.EXE Process Exit Code: 0 (Success)
> >
> > ************************************************************
> > but when i add this,
> >
> > Database Maintenance Plan (Optimization):
> >
> > (Check) Reorganize data and index pages
> > with
> > Reorganize pages with the original amount of free space
> > or
> > Change free space per page percentage to 10 %
> >
> >
> >
> > (Check) Remove unused space from database files
> > Shrink database when it grows beyonds: 50 MB
> > Amount of free space to remain after shrink: 10 % of data space
> > Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> >
> > Failed - error
> >
> > [1] Database openview: Index Rebuild (leaving 100%% free space)...
> >
> > Rebuilding indexes for table 'OV_MS_Annotation'
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002: [Microsoft][ODBC SQL
> > Server Driver][SQL Server]The log file for database 'openview' is full. Back
> > up the transaction log for the database to free up some log space.
> > [Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
> > terminated.
> >
> > ** Execution Time: 0 hrs, 0 mins, 2 secs **
> >
> > [2] Database openview: Removing unused space from the database files (if
> > database size is more than 50 MB). Reducing free space to 10 percent of
> > data...
> > ** Execution Time: 0 hrs, 0 mins, 1 secs **
> >
> > Deleting old text reports... 0 file(s) deleted.
> >
> > End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> > 13-07-2006 15:03:02
> > SQLMAINT.EXE Process Exit Code: 1 (Failed)
> >
> > Will it be that it doesn't let to execute everything in the same maintenance
> > Plan?
> >
> >
> > Regards,
> >
> > José Júlio Duarte
> >
> Reindexing generates a log of transaction log activity, and your
> transaction log isn't big enough to handle the volume. Exactly what the
> error message says.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||José Júlio Duarte wrote:
> Hello Tracy
> Where can i change to resolve this? and how?
>
Hmmmm... This is precisely why I DESPISE that maintenance plan wizard.
You should not be creating processes like this without understanding
their impact. The fact that you have to ask how to expand (or
auto-grow) a transaction log file tells me that you are in over your head.
Read about "Creating and Maintaining Databases" in Books Online to learn
how to configure automatic file growth.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> José Júlio Duarte wrote:
>> Hello Tracy
>> Where can i change to resolve this? and how?
> Hmmmm... This is precisely why I DESPISE that maintenance plan wizard.
> You should not be creating processes like this without understanding
> their impact. The fact that you have to ask how to expand (or
> auto-grow) a transaction log file tells me that you are in over your head.
> Read about "Creating and Maintaining Databases" in Books Online to learn
> how to configure automatic file growth.
>
After re-reading this, I should clarify. I wasn't attacking you, my
apologies if it looks that way. Those maintenance plan wizards
frustrate me greatly, because they attempt to gloss over what are some
very critical and potentially dangerous processes. Reindexing is an
intensive process, and shouldn't be possible using a wizard, the
administrator should fully understand what's going on throughout the
process. Transaction log backups, if not done properly, can result in
unusable backups, full log files, all sorts of things.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||This is a multi-part message in MIME format.
--090306080204040602090200
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Tracy McKibben wrote:
> Tracy McKibben wrote:
>> José Júlio Duarte wrote:
>> Hello Tracy
>> Where can i change to resolve this? and how?
>>
>> Hmmmm... This is precisely why I DESPISE that maintenance plan
>> wizard. You should not be creating processes like this without
>> understanding their impact. The fact that you have to ask how to
>> expand (or auto-grow) a transaction log file tells me that you are in
>> over your head.
>> Read about "Creating and Maintaining Databases" in Books Online to
>> learn how to configure automatic file growth.
>>
> After re-reading this, I should clarify. I wasn't attacking you, my
> apologies if it looks that way. Those maintenance plan wizards
> frustrate me greatly, because they attempt to gloss over what are some
> very critical and potentially dangerous processes. Reindexing is an
> intensive process, and shouldn't be possible using a wizard, the
> administrator should fully understand what's going on throughout the
> process. Transaction log backups, if not done properly, can result in
> unusable backups, full log files, all sorts of things.
>
Just to add to Tracy's comments. Why do you run this shrink job every
week? In my opinion it won't give you anything but trouble and poor
performance. Especially when you have a limit of 50 Mb which is next to
nothing for a database file it's really waste of time to shrink it.
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
--090306080204040602090200
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Tracy McKibben wrote:
<blockquote cite="midOTbkp%23ppGHA.1140@.TK2MSFTNGP05.phx.gbl"
type="cite">Tracy McKibben wrote:
<br>
<blockquote type="cite">José Júlio Duarte wrote:
<br>
<blockquote type="cite">Hello Tracy
<br>
Where can i change to resolve this? and how?
<br>
<br>
</blockquote>
<br>
Hmmmm... This is precisely why I DESPISE that maintenance plan wizard.
 You should not be creating processes like this without understanding
their impact. The fact that you have to ask how to expand (or
auto-grow) a transaction log file tells me that you are in over your
head.
<br>
<br>
Read about "Creating and Maintaining Databases" in Books Online to
learn how to configure automatic file growth.
<br>
<br>
<br>
</blockquote>
<br>
After re-reading this, I should clarify. I wasn't attacking you, my
apologies if it looks that way. Those maintenance plan wizards
frustrate me greatly, because they attempt to gloss over what are some
very critical and potentially dangerous processes. Reindexing is an
intensive process, and shouldn't be possible using a wizard, the
administrator should fully understand what's going on throughout the
process. Transaction log backups, if not done properly, can result in
unusable backups, full log files, all sorts of things.
<br>
<br>
</blockquote>
<font size="-1"><font face="Arial"><br>
Just to add to Tracy's comments. Why do you run this shrink job every
week? In my opinion it won't give you anything but trouble and poor
performance. Especially when you have a limit of 50 Mb which is next to
nothing for a database file it's really waste of time to shrink it. <br>
<br>
<br>
-- <br>
Regards<br>
Steen Schlüter Persson<br>
Databaseadministrator / Systemadministrator<br>
</font></font>
</body>
</html>
--090306080204040602090200--
When i execute the Maintenance Plan,
Database Maintenance Plan (Optimization):
(Check) Remove unused space from database files
Shrink database when it grows beyonds: 50 MB
Amount of free space to remain after shrink: 10 % of data space
Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
Sucess
[1] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan openview Optimization' on
13-07-2006 15:04:00
SQLMAINT.EXE Process Exit Code: 0 (Success)
************************************************************
but when i add this,
Database Maintenance Plan (Optimization):
(Check) Reorganize data and index pages
with
Reorganize pages with the original amount of free space
or
Change free space per page percentage to 10 %
(Check) Remove unused space from database files
Shrink database when it grows beyonds: 50 MB
Amount of free space to remain after shrink: 10 % of data space
Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
Failed - error
[1] Database openview: Index Rebuild (leaving 100%% free space)...
Rebuilding indexes for table 'OV_MS_Annotation'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002: [Microsoft][ODBC SQL
Server Driver][SQL Server]The log file for database 'openview' is full. Back
up the transaction log for the database to free up some log space.
[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
terminated.
** Execution Time: 0 hrs, 0 mins, 2 secs **
[2] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan openview Optimization' on
13-07-2006 15:03:02
SQLMAINT.EXE Process Exit Code: 1 (Failed)
Will it be that it doesn't let to execute everything in the same maintenance
Plan?
Regards,
José Júlio DuarteJosé Júlio Duarte wrote:
> Hello
> When i execute the Maintenance Plan,
> Database Maintenance Plan (Optimization):
> (Check) Remove unused space from database files
> Shrink database when it grows beyonds: 50 MB
> Amount of free space to remain after shrink: 10 % of data space
> Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> Sucess
> [1] Database openview: Removing unused space from the database files (if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Deleting old text reports... 0 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> 13-07-2006 15:04:00
> SQLMAINT.EXE Process Exit Code: 0 (Success)
> ************************************************************
> but when i add this,
> Database Maintenance Plan (Optimization):
> (Check) Reorganize data and index pages
> with
> Reorganize pages with the original amount of free space
> or
> Change free space per page percentage to 10 %
>
> (Check) Remove unused space from database files
> Shrink database when it grows beyonds: 50 MB
> Amount of free space to remain after shrink: 10 % of data space
> Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> Failed - error
> [1] Database openview: Index Rebuild (leaving 100%% free space)...
> Rebuilding indexes for table 'OV_MS_Annotation'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002: [Microsoft][ODBC SQL
> Server Driver][SQL Server]The log file for database 'openview' is full. Back
> up the transaction log for the database to free up some log space.
> [Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
> terminated.
> ** Execution Time: 0 hrs, 0 mins, 2 secs **
> [2] Database openview: Removing unused space from the database files (if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Deleting old text reports... 0 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> 13-07-2006 15:03:02
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> Will it be that it doesn't let to execute everything in the same maintenance
> Plan?
>
> Regards,
> José Júlio Duarte
>
Reindexing generates a log of transaction log activity, and your
transaction log isn't big enough to handle the volume. Exactly what the
error message says.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hello Tracy
Where can i change to resolve this? and how?
Regards
"Tracy McKibben" wrote:
> José Júlio Duarte wrote:
> > Hello
> >
> > When i execute the Maintenance Plan,
> >
> > Database Maintenance Plan (Optimization):
> >
> > (Check) Remove unused space from database files
> > Shrink database when it grows beyonds: 50 MB
> > Amount of free space to remain after shrink: 10 % of data space
> > Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> >
> > Sucess
> >
> > [1] Database openview: Removing unused space from the database files (if
> > database size is more than 50 MB). Reducing free space to 10 percent of
> > data...
> > ** Execution Time: 0 hrs, 0 mins, 1 secs **
> >
> > Deleting old text reports... 0 file(s) deleted.
> >
> > End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> > 13-07-2006 15:04:00
> > SQLMAINT.EXE Process Exit Code: 0 (Success)
> >
> > ************************************************************
> > but when i add this,
> >
> > Database Maintenance Plan (Optimization):
> >
> > (Check) Reorganize data and index pages
> > with
> > Reorganize pages with the original amount of free space
> > or
> > Change free space per page percentage to 10 %
> >
> >
> >
> > (Check) Remove unused space from database files
> > Shrink database when it grows beyonds: 50 MB
> > Amount of free space to remain after shrink: 10 % of data space
> > Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> >
> > Failed - error
> >
> > [1] Database openview: Index Rebuild (leaving 100%% free space)...
> >
> > Rebuilding indexes for table 'OV_MS_Annotation'
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002: [Microsoft][ODBC SQL
> > Server Driver][SQL Server]The log file for database 'openview' is full. Back
> > up the transaction log for the database to free up some log space.
> > [Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been
> > terminated.
> >
> > ** Execution Time: 0 hrs, 0 mins, 2 secs **
> >
> > [2] Database openview: Removing unused space from the database files (if
> > database size is more than 50 MB). Reducing free space to 10 percent of
> > data...
> > ** Execution Time: 0 hrs, 0 mins, 1 secs **
> >
> > Deleting old text reports... 0 file(s) deleted.
> >
> > End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> > 13-07-2006 15:03:02
> > SQLMAINT.EXE Process Exit Code: 1 (Failed)
> >
> > Will it be that it doesn't let to execute everything in the same maintenance
> > Plan?
> >
> >
> > Regards,
> >
> > José Júlio Duarte
> >
> Reindexing generates a log of transaction log activity, and your
> transaction log isn't big enough to handle the volume. Exactly what the
> error message says.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||José Júlio Duarte wrote:
> Hello Tracy
> Where can i change to resolve this? and how?
>
Hmmmm... This is precisely why I DESPISE that maintenance plan wizard.
You should not be creating processes like this without understanding
their impact. The fact that you have to ask how to expand (or
auto-grow) a transaction log file tells me that you are in over your head.
Read about "Creating and Maintaining Databases" in Books Online to learn
how to configure automatic file growth.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> José Júlio Duarte wrote:
>> Hello Tracy
>> Where can i change to resolve this? and how?
> Hmmmm... This is precisely why I DESPISE that maintenance plan wizard.
> You should not be creating processes like this without understanding
> their impact. The fact that you have to ask how to expand (or
> auto-grow) a transaction log file tells me that you are in over your head.
> Read about "Creating and Maintaining Databases" in Books Online to learn
> how to configure automatic file growth.
>
After re-reading this, I should clarify. I wasn't attacking you, my
apologies if it looks that way. Those maintenance plan wizards
frustrate me greatly, because they attempt to gloss over what are some
very critical and potentially dangerous processes. Reindexing is an
intensive process, and shouldn't be possible using a wizard, the
administrator should fully understand what's going on throughout the
process. Transaction log backups, if not done properly, can result in
unusable backups, full log files, all sorts of things.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||This is a multi-part message in MIME format.
--090306080204040602090200
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Tracy McKibben wrote:
> Tracy McKibben wrote:
>> José Júlio Duarte wrote:
>> Hello Tracy
>> Where can i change to resolve this? and how?
>>
>> Hmmmm... This is precisely why I DESPISE that maintenance plan
>> wizard. You should not be creating processes like this without
>> understanding their impact. The fact that you have to ask how to
>> expand (or auto-grow) a transaction log file tells me that you are in
>> over your head.
>> Read about "Creating and Maintaining Databases" in Books Online to
>> learn how to configure automatic file growth.
>>
> After re-reading this, I should clarify. I wasn't attacking you, my
> apologies if it looks that way. Those maintenance plan wizards
> frustrate me greatly, because they attempt to gloss over what are some
> very critical and potentially dangerous processes. Reindexing is an
> intensive process, and shouldn't be possible using a wizard, the
> administrator should fully understand what's going on throughout the
> process. Transaction log backups, if not done properly, can result in
> unusable backups, full log files, all sorts of things.
>
Just to add to Tracy's comments. Why do you run this shrink job every
week? In my opinion it won't give you anything but trouble and poor
performance. Especially when you have a limit of 50 Mb which is next to
nothing for a database file it's really waste of time to shrink it.
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
--090306080204040602090200
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Tracy McKibben wrote:
<blockquote cite="midOTbkp%23ppGHA.1140@.TK2MSFTNGP05.phx.gbl"
type="cite">Tracy McKibben wrote:
<br>
<blockquote type="cite">José Júlio Duarte wrote:
<br>
<blockquote type="cite">Hello Tracy
<br>
Where can i change to resolve this? and how?
<br>
<br>
</blockquote>
<br>
Hmmmm... This is precisely why I DESPISE that maintenance plan wizard.
 You should not be creating processes like this without understanding
their impact. The fact that you have to ask how to expand (or
auto-grow) a transaction log file tells me that you are in over your
head.
<br>
<br>
Read about "Creating and Maintaining Databases" in Books Online to
learn how to configure automatic file growth.
<br>
<br>
<br>
</blockquote>
<br>
After re-reading this, I should clarify. I wasn't attacking you, my
apologies if it looks that way. Those maintenance plan wizards
frustrate me greatly, because they attempt to gloss over what are some
very critical and potentially dangerous processes. Reindexing is an
intensive process, and shouldn't be possible using a wizard, the
administrator should fully understand what's going on throughout the
process. Transaction log backups, if not done properly, can result in
unusable backups, full log files, all sorts of things.
<br>
<br>
</blockquote>
<font size="-1"><font face="Arial"><br>
Just to add to Tracy's comments. Why do you run this shrink job every
week? In my opinion it won't give you anything but trouble and poor
performance. Especially when you have a limit of 50 Mb which is next to
nothing for a database file it's really waste of time to shrink it. <br>
<br>
<br>
-- <br>
Regards<br>
Steen Schlüter Persson<br>
Databaseadministrator / Systemadministrator<br>
</font></font>
</body>
</html>
--090306080204040602090200--
Error in Maintenance Plan (one of database)
Hello
When i execute the Maintenance Plan,
Database Maintenance Plan (Optimization):
(Check) Remove unused space from database files
Shrink database when it grows beyonds: 50 MB
Amount of free space to remain after shrink: 10 % of data space
Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
Sucess
[1] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan openview Optimization' on
13-07-2006 15:04:00
SQLMAINT.EXE Process Exit Code: 0 (Success)
****************************************
********************
but when i add this,
Database Maintenance Plan (Optimization):
(Check) Reorganize data and index pages
with
Reorganize pages with the original amount of free space
or
Change free space per page percentage to 10 %
(Check) Remove unused space from database files
Shrink database when it grows beyonds: 50 MB
Amount of free space to remain after shrink: 10 % of data space
Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
Failed - error
[1] Database openview: Index Rebuild (leaving 100%% free space)...
Rebuilding indexes for table 'OV_MS_Annotation'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server]The log file for database 'openview' is full.
Back
up the transaction log for the database to free up some log space.
[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has
been
terminated.
** Execution Time: 0 hrs, 0 mins, 2 secs **
[2] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan openview Optimization' on
13-07-2006 15:03:02
SQLMAINT.EXE Process Exit Code: 1 (Failed)
Will it be that it doesn't let to execute everything in the same maintenance
Plan?
Regards,
José Júlio DuarteJosé Júlio Duarte wrote:
> Hello
> When i execute the Maintenance Plan,
> Database Maintenance Plan (Optimization):
> (Check) Remove unused space from database files
> Shrink database when it grows beyonds: 50 MB
> Amount of free space to remain after shrink: 10 % of data space
> Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> Sucess
> [1] Database openview: Removing unused space from the database files (
if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Deleting old text reports... 0 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> 13-07-2006 15:04:00
> SQLMAINT.EXE Process Exit Code: 0 (Success)
> ****************************************
********************
> but when i add this,
> Database Maintenance Plan (Optimization):
> (Check) Reorganize data and index pages
> with
> Reorganize pages with the original amount of free space
> or
> Change free space per page percentage to 10 %
>
> (Check) Remove unused space from database files
> Shrink database when it grows beyonds: 50 MB
> Amount of free space to remain after shrink: 10 % of data space
> Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> Failed - error
> [1] Database openview: Index Rebuild (leaving 100%% free space)...
> Rebuilding indexes for table 'OV_MS_Annotation'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002: [Microsoft]
[ODBC SQL
> Server Driver][SQL Server]The log file for database 'openview' is full
. Back
> up the transaction log for the database to free up some log space.
> [Microsoft][ODBC SQL Server Driver][SQL Server]The statement h
as been
> terminated.
> ** Execution Time: 0 hrs, 0 mins, 2 secs **
> [2] Database openview: Removing unused space from the database files (
if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Deleting old text reports... 0 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> 13-07-2006 15:03:02
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> Will it be that it doesn't let to execute everything in the same maintenan
ce
> Plan?
>
> Regards,
> José Júlio Duarte
>
Reindexing generates a log of transaction log activity, and your
transaction log isn't big enough to handle the volume. Exactly what the
error message says.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hello Tracy
Where can i change to resolve this? and how?
Regards
"Tracy McKibben" wrote:
> José Júlio Duarte wrote:
> Reindexing generates a log of transaction log activity, and your
> transaction log isn't big enough to handle the volume. Exactly what the
> error message says.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||José Júlio Duarte wrote:
> Hello Tracy
> Where can i change to resolve this? and how?
>
Hmmmm... This is precisely why I DESPISE that maintenance plan wizard.
You should not be creating processes like this without understanding
their impact. The fact that you have to ask how to expand (or
auto-grow) a transaction log file tells me that you are in over your head.
Read about "Creating and Maintaining Databases" in Books Online to learn
how to configure automatic file growth.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> José Júlio Duarte wrote:
> Hmmmm... This is precisely why I DESPISE that maintenance plan wizard.
> You should not be creating processes like this without understanding
> their impact. The fact that you have to ask how to expand (or
> auto-grow) a transaction log file tells me that you are in over your head.
> Read about "Creating and Maintaining Databases" in Books Online to learn
> how to configure automatic file growth.
>
After re-reading this, I should clarify. I wasn't attacking you, my
apologies if it looks that way. Those maintenance plan wizards
frustrate me greatly, because they attempt to gloss over what are some
very critical and potentially dangerous processes. Reindexing is an
intensive process, and shouldn't be possible using a wizard, the
administrator should fully understand what's going on throughout the
process. Transaction log backups, if not done properly, can result in
unusable backups, full log files, all sorts of things.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> Tracy McKibben wrote:
> After re-reading this, I should clarify. I wasn't attacking you, my
> apologies if it looks that way. Those maintenance plan wizards
> frustrate me greatly, because they attempt to gloss over what are some
> very critical and potentially dangerous processes. Reindexing is an
> intensive process, and shouldn't be possible using a wizard, the
> administrator should fully understand what's going on throughout the
> process. Transaction log backups, if not done properly, can result in
> unusable backups, full log files, all sorts of things.
>
Just to add to Tracy's comments. Why do you run this shrink job every
week? In my opinion it won't give you anything but trouble and poor
performance. Especially when you have a limit of 50 Mb which is next to
nothing for a database file it's really waste of time to shrink it.
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
When i execute the Maintenance Plan,
Database Maintenance Plan (Optimization):
(Check) Remove unused space from database files
Shrink database when it grows beyonds: 50 MB
Amount of free space to remain after shrink: 10 % of data space
Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
Sucess
[1] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan openview Optimization' on
13-07-2006 15:04:00
SQLMAINT.EXE Process Exit Code: 0 (Success)
****************************************
********************
but when i add this,
Database Maintenance Plan (Optimization):
(Check) Reorganize data and index pages
with
Reorganize pages with the original amount of free space
or
Change free space per page percentage to 10 %
(Check) Remove unused space from database files
Shrink database when it grows beyonds: 50 MB
Amount of free space to remain after shrink: 10 % of data space
Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
Failed - error
[1] Database openview: Index Rebuild (leaving 100%% free space)...
Rebuilding indexes for table 'OV_MS_Annotation'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server]The log file for database 'openview' is full.
Back
up the transaction log for the database to free up some log space.
[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has
been
terminated.
** Execution Time: 0 hrs, 0 mins, 2 secs **
[2] Database openview: Removing unused space from the database files (if
database size is more than 50 MB). Reducing free space to 10 percent of
data...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan openview Optimization' on
13-07-2006 15:03:02
SQLMAINT.EXE Process Exit Code: 1 (Failed)
Will it be that it doesn't let to execute everything in the same maintenance
Plan?
Regards,
José Júlio DuarteJosé Júlio Duarte wrote:
> Hello
> When i execute the Maintenance Plan,
> Database Maintenance Plan (Optimization):
> (Check) Remove unused space from database files
> Shrink database when it grows beyonds: 50 MB
> Amount of free space to remain after shrink: 10 % of data space
> Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> Sucess
> [1] Database openview: Removing unused space from the database files (
if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Deleting old text reports... 0 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> 13-07-2006 15:04:00
> SQLMAINT.EXE Process Exit Code: 0 (Success)
> ****************************************
********************
> but when i add this,
> Database Maintenance Plan (Optimization):
> (Check) Reorganize data and index pages
> with
> Reorganize pages with the original amount of free space
> or
> Change free space per page percentage to 10 %
>
> (Check) Remove unused space from database files
> Shrink database when it grows beyonds: 50 MB
> Amount of free space to remain after shrink: 10 % of data space
> Schedude : Occurs every 1 week(s) on Thurday, at 15:04:00
> Failed - error
> [1] Database openview: Index Rebuild (leaving 100%% free space)...
> Rebuilding indexes for table 'OV_MS_Annotation'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 9002: [Microsoft]
[ODBC SQL
> Server Driver][SQL Server]The log file for database 'openview' is full
. Back
> up the transaction log for the database to free up some log space.
> [Microsoft][ODBC SQL Server Driver][SQL Server]The statement h
as been
> terminated.
> ** Execution Time: 0 hrs, 0 mins, 2 secs **
> [2] Database openview: Removing unused space from the database files (
if
> database size is more than 50 MB). Reducing free space to 10 percent of
> data...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Deleting old text reports... 0 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan openview Optimization' on
> 13-07-2006 15:03:02
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> Will it be that it doesn't let to execute everything in the same maintenan
ce
> Plan?
>
> Regards,
> José Júlio Duarte
>
Reindexing generates a log of transaction log activity, and your
transaction log isn't big enough to handle the volume. Exactly what the
error message says.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hello Tracy
Where can i change to resolve this? and how?
Regards
"Tracy McKibben" wrote:
> José Júlio Duarte wrote:
> Reindexing generates a log of transaction log activity, and your
> transaction log isn't big enough to handle the volume. Exactly what the
> error message says.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||José Júlio Duarte wrote:
> Hello Tracy
> Where can i change to resolve this? and how?
>
Hmmmm... This is precisely why I DESPISE that maintenance plan wizard.
You should not be creating processes like this without understanding
their impact. The fact that you have to ask how to expand (or
auto-grow) a transaction log file tells me that you are in over your head.
Read about "Creating and Maintaining Databases" in Books Online to learn
how to configure automatic file growth.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> José Júlio Duarte wrote:
> Hmmmm... This is precisely why I DESPISE that maintenance plan wizard.
> You should not be creating processes like this without understanding
> their impact. The fact that you have to ask how to expand (or
> auto-grow) a transaction log file tells me that you are in over your head.
> Read about "Creating and Maintaining Databases" in Books Online to learn
> how to configure automatic file growth.
>
After re-reading this, I should clarify. I wasn't attacking you, my
apologies if it looks that way. Those maintenance plan wizards
frustrate me greatly, because they attempt to gloss over what are some
very critical and potentially dangerous processes. Reindexing is an
intensive process, and shouldn't be possible using a wizard, the
administrator should fully understand what's going on throughout the
process. Transaction log backups, if not done properly, can result in
unusable backups, full log files, all sorts of things.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> Tracy McKibben wrote:
> After re-reading this, I should clarify. I wasn't attacking you, my
> apologies if it looks that way. Those maintenance plan wizards
> frustrate me greatly, because they attempt to gloss over what are some
> very critical and potentially dangerous processes. Reindexing is an
> intensive process, and shouldn't be possible using a wizard, the
> administrator should fully understand what's going on throughout the
> process. Transaction log backups, if not done properly, can result in
> unusable backups, full log files, all sorts of things.
>
Just to add to Tracy's comments. Why do you run this shrink job every
week? In my opinion it won't give you anything but trouble and poor
performance. Especially when you have a limit of 50 Mb which is next to
nothing for a database file it's really waste of time to shrink it.
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
Sunday, February 26, 2012
Error in DB
I have the next problem:
when i try to insert a row inside a table there ir the
next error message:
Could not allocate space for object '<Table Name>' in
database '<DB Name>' because the 'PRIMARY' filegroup is
full.
How can i solve this problem ?
Thanks in advanceTHe problem could either be.
1. lack of disk space on the drive where the primary filegroup resides. (As
another poster suggests ) or
2. The filegroup may have a max size set... In SQL Enterprise Manager, right
click your database ->Properties, and check the data and log tab...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Enrico" <ezerilli@.csc.com> wrote in message
news:0da001c3db7c$e64030e0$a301280a@.phx.gbl...
filegroup resides. (As
Enterprise Manager, right
log tab...
Charlotte, NC
(PASS) and it's
I have solve the problem check the option Unrestricted
file Growth under DB properties/Transaction Log.
So i dont have any error about PRIMARY Filegroup.
Thanks a lot to every body.
Bye
when i try to insert a row inside a table there ir the
next error message:
Could not allocate space for object '<Table Name>' in
database '<DB Name>' because the 'PRIMARY' filegroup is
full.
How can i solve this problem ?
Thanks in advanceTHe problem could either be.
1. lack of disk space on the drive where the primary filegroup resides. (As
another poster suggests ) or
2. The filegroup may have a max size set... In SQL Enterprise Manager, right
click your database ->Properties, and check the data and log tab...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Enrico" <ezerilli@.csc.com> wrote in message
news:0da001c3db7c$e64030e0$a301280a@.phx.gbl...
quote:|||
> I have the next problem:
> when i try to insert a row inside a table there ir the
> next error message:
> Could not allocate space for object '<Table Name>' in
> database '<DB Name>' because the 'PRIMARY' filegroup is
> full.
> How can i solve this problem ?
> Thanks in advance
quote:
>--Original Message--
>THe problem could either be.
>1. lack of disk space on the drive where the primary
filegroup resides. (As
quote:
>another poster suggests ) or
>2. The filegroup may have a max size set... In SQL
Enterprise Manager, right
quote:
>click your database ->Properties, and check the data and
log tab...
quote:
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Computer Education Services Corporation (CESC),
Charlotte, NC
quote:
>www.computeredservices.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
quote:
>community of SQL Server professionals.
>www.sqlpass.org
>"Enrico" <ezerilli@.csc.com> wrote in message
>news:0da001c3db7c$e64030e0$a301280a@.phx.gbl...
>
>.
>
I have solve the problem check the option Unrestricted
file Growth under DB properties/Transaction Log.
So i dont have any error about PRIMARY Filegroup.
Thanks a lot to every body.
Bye
Error in DB
I have the next problem:
when i try to insert a row inside a table there ir the
next error message:
Could not allocate space for object '<Table Name>' in
database '<DB Name>' because the 'PRIMARY' filegroup is
full.
How can i solve this problem ?
Thanks in advanceCheck the disk (drive) where your primary filegroup is
located and see how much space is left... try to free up
space (clean up files you dont need) if not create a
second filegroup...
>--Original Message--
>I have the next problem:
>when i try to insert a row inside a table there ir the
>next error message:
>Could not allocate space for object '<Table Name>' in
>database '<DB Name>' because the 'PRIMARY' filegroup is
>full.
>How can i solve this problem ?
>Thanks in advance
>.
>|||THe problem could either be.
1. lack of disk space on the drive where the primary filegroup resides. (As
another poster suggests ) or
2. The filegroup may have a max size set... In SQL Enterprise Manager, right
click your database ->Properties, and check the data and log tab...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Enrico" <ezerilli@.csc.com> wrote in message
news:0da001c3db7c$e64030e0$a301280a@.phx.gbl...
> I have the next problem:
> when i try to insert a row inside a table there ir the
> next error message:
> Could not allocate space for object '<Table Name>' in
> database '<DB Name>' because the 'PRIMARY' filegroup is
> full.
> How can i solve this problem ?
> Thanks in advance|||>--Original Message--
>THe problem could either be.
>1. lack of disk space on the drive where the primary
filegroup resides. (As
>another poster suggests ) or
>2. The filegroup may have a max size set... In SQL
Enterprise Manager, right
>click your database ->Properties, and check the data and
log tab...
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Computer Education Services Corporation (CESC),
Charlotte, NC
>www.computeredservices.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"Enrico" <ezerilli@.csc.com> wrote in message
>news:0da001c3db7c$e64030e0$a301280a@.phx.gbl...
>> I have the next problem:
>> when i try to insert a row inside a table there ir the
>> next error message:
>> Could not allocate space for object '<Table Name>' in
>> database '<DB Name>' because the 'PRIMARY' filegroup is
>> full.
>> How can i solve this problem ?
>> Thanks in advance
>
>.
>
I have solve the problem check the option Unrestricted
file Growth under DB properties/Transaction Log.
So i dont have any error about PRIMARY Filegroup.
Thanks a lot to every body.
Bye
when i try to insert a row inside a table there ir the
next error message:
Could not allocate space for object '<Table Name>' in
database '<DB Name>' because the 'PRIMARY' filegroup is
full.
How can i solve this problem ?
Thanks in advanceCheck the disk (drive) where your primary filegroup is
located and see how much space is left... try to free up
space (clean up files you dont need) if not create a
second filegroup...
>--Original Message--
>I have the next problem:
>when i try to insert a row inside a table there ir the
>next error message:
>Could not allocate space for object '<Table Name>' in
>database '<DB Name>' because the 'PRIMARY' filegroup is
>full.
>How can i solve this problem ?
>Thanks in advance
>.
>|||THe problem could either be.
1. lack of disk space on the drive where the primary filegroup resides. (As
another poster suggests ) or
2. The filegroup may have a max size set... In SQL Enterprise Manager, right
click your database ->Properties, and check the data and log tab...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Enrico" <ezerilli@.csc.com> wrote in message
news:0da001c3db7c$e64030e0$a301280a@.phx.gbl...
> I have the next problem:
> when i try to insert a row inside a table there ir the
> next error message:
> Could not allocate space for object '<Table Name>' in
> database '<DB Name>' because the 'PRIMARY' filegroup is
> full.
> How can i solve this problem ?
> Thanks in advance|||>--Original Message--
>THe problem could either be.
>1. lack of disk space on the drive where the primary
filegroup resides. (As
>another poster suggests ) or
>2. The filegroup may have a max size set... In SQL
Enterprise Manager, right
>click your database ->Properties, and check the data and
log tab...
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Computer Education Services Corporation (CESC),
Charlotte, NC
>www.computeredservices.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"Enrico" <ezerilli@.csc.com> wrote in message
>news:0da001c3db7c$e64030e0$a301280a@.phx.gbl...
>> I have the next problem:
>> when i try to insert a row inside a table there ir the
>> next error message:
>> Could not allocate space for object '<Table Name>' in
>> database '<DB Name>' because the 'PRIMARY' filegroup is
>> full.
>> How can i solve this problem ?
>> Thanks in advance
>
>.
>
I have solve the problem check the option Unrestricted
file Growth under DB properties/Transaction Log.
So i dont have any error about PRIMARY Filegroup.
Thanks a lot to every body.
Bye
Subscribe to:
Posts (Atom)