I'm running SQL 2000 on W2K on two servers. The DB maintenance is set to
automatically remove old transaction log backups. A couple of months ago,
the transaction log backups stop getting tossed. I don't think it has
anything to do with whether or not the db is set to do a simple backup.
I've split the dbs between different maintenance plans and have had no luck.
I'm thinking it has something to do with a hotfix because both SQL servers
had issues about the same time.
I didn't make any changes to any of the Dbs or the SQL server that I can
remember.
Do I need to register the SQL server with Active Directory? I upgraded the
network from NT4 to W2003 and AD.
Registering with AD should have no effect... Does the DBMaint Plan log show
any information?
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"Chris Geiser" <glg.dell@.worldnet.att.net> wrote in message
news:%23CAcS9JaEHA.2792@.TK2MSFTNGP09.phx.gbl...
> I'm running SQL 2000 on W2K on two servers. The DB maintenance is set to
> automatically remove old transaction log backups. A couple of months ago,
> the transaction log backups stop getting tossed. I don't think it has
> anything to do with whether or not the db is set to do a simple backup.
> I've split the dbs between different maintenance plans and have had no
luck.
> I'm thinking it has something to do with a hotfix because both SQL servers
> had issues about the same time.
> I didn't make any changes to any of the Dbs or the SQL server that I can
> remember.
> Do I need to register the SQL server with Active Directory? I upgraded
the
> network from NT4 to W2003 and AD.
>
Showing posts with label old. Show all posts
Showing posts with label old. Show all posts
Sunday, March 11, 2012
database maintenance plan...
I'm running SQL 2000 on W2K on two servers. The DB maintenance is set to
automatically remove old transaction log backups. A couple of months ago,
the transaction log backups stop getting tossed. I don't think it has
anything to do with whether or not the db is set to do a simple backup.
I've split the dbs between different maintenance plans and have had no luck.
I'm thinking it has something to do with a hotfix because both SQL servers
had issues about the same time.
I didn't make any changes to any of the Dbs or the SQL server that I can
remember.
Do I need to register the SQL server with Active Directory? I upgraded the
network from NT4 to W2003 and AD.Registering with AD should have no effect... Does the DBMaint Plan log show
any information?
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"Chris Geiser" <glg.dell@.worldnet.att.net> wrote in message
news:%23CAcS9JaEHA.2792@.TK2MSFTNGP09.phx.gbl...
> I'm running SQL 2000 on W2K on two servers. The DB maintenance is set to
> automatically remove old transaction log backups. A couple of months ago,
> the transaction log backups stop getting tossed. I don't think it has
> anything to do with whether or not the db is set to do a simple backup.
> I've split the dbs between different maintenance plans and have had no
luck.
> I'm thinking it has something to do with a hotfix because both SQL servers
> had issues about the same time.
> I didn't make any changes to any of the Dbs or the SQL server that I can
> remember.
> Do I need to register the SQL server with Active Directory? I upgraded
the
> network from NT4 to W2003 and AD.
>
automatically remove old transaction log backups. A couple of months ago,
the transaction log backups stop getting tossed. I don't think it has
anything to do with whether or not the db is set to do a simple backup.
I've split the dbs between different maintenance plans and have had no luck.
I'm thinking it has something to do with a hotfix because both SQL servers
had issues about the same time.
I didn't make any changes to any of the Dbs or the SQL server that I can
remember.
Do I need to register the SQL server with Active Directory? I upgraded the
network from NT4 to W2003 and AD.Registering with AD should have no effect... Does the DBMaint Plan log show
any information?
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"Chris Geiser" <glg.dell@.worldnet.att.net> wrote in message
news:%23CAcS9JaEHA.2792@.TK2MSFTNGP09.phx.gbl...
> I'm running SQL 2000 on W2K on two servers. The DB maintenance is set to
> automatically remove old transaction log backups. A couple of months ago,
> the transaction log backups stop getting tossed. I don't think it has
> anything to do with whether or not the db is set to do a simple backup.
> I've split the dbs between different maintenance plans and have had no
luck.
> I'm thinking it has something to do with a hotfix because both SQL servers
> had issues about the same time.
> I didn't make any changes to any of the Dbs or the SQL server that I can
> remember.
> Do I need to register the SQL server with Active Directory? I upgraded
the
> network from NT4 to W2003 and AD.
>
database maintenance plan...
I'm running SQL 2000 on W2K on two servers. The DB maintenance is set to
automatically remove old transaction log backups. A couple of months ago,
the transaction log backups stop getting tossed. I don't think it has
anything to do with whether or not the db is set to do a simple backup.
I've split the dbs between different maintenance plans and have had no luck.
I'm thinking it has something to do with a hotfix because both SQL servers
had issues about the same time.
I didn't make any changes to any of the Dbs or the SQL server that I can
remember.
Do I need to register the SQL server with Active Directory? I upgraded the
network from NT4 to W2003 and AD.Registering with AD should have no effect... Does the DBMaint Plan log show
any information?
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"Chris Geiser" <glg.dell@.worldnet.att.net> wrote in message
news:%23CAcS9JaEHA.2792@.TK2MSFTNGP09.phx.gbl...
> I'm running SQL 2000 on W2K on two servers. The DB maintenance is set to
> automatically remove old transaction log backups. A couple of months ago,
> the transaction log backups stop getting tossed. I don't think it has
> anything to do with whether or not the db is set to do a simple backup.
> I've split the dbs between different maintenance plans and have had no
luck.
> I'm thinking it has something to do with a hotfix because both SQL servers
> had issues about the same time.
> I didn't make any changes to any of the Dbs or the SQL server that I can
> remember.
> Do I need to register the SQL server with Active Directory? I upgraded
the
> network from NT4 to W2003 and AD.
>
automatically remove old transaction log backups. A couple of months ago,
the transaction log backups stop getting tossed. I don't think it has
anything to do with whether or not the db is set to do a simple backup.
I've split the dbs between different maintenance plans and have had no luck.
I'm thinking it has something to do with a hotfix because both SQL servers
had issues about the same time.
I didn't make any changes to any of the Dbs or the SQL server that I can
remember.
Do I need to register the SQL server with Active Directory? I upgraded the
network from NT4 to W2003 and AD.Registering with AD should have no effect... Does the DBMaint Plan log show
any information?
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"Chris Geiser" <glg.dell@.worldnet.att.net> wrote in message
news:%23CAcS9JaEHA.2792@.TK2MSFTNGP09.phx.gbl...
> I'm running SQL 2000 on W2K on two servers. The DB maintenance is set to
> automatically remove old transaction log backups. A couple of months ago,
> the transaction log backups stop getting tossed. I don't think it has
> anything to do with whether or not the db is set to do a simple backup.
> I've split the dbs between different maintenance plans and have had no
luck.
> I'm thinking it has something to do with a hotfix because both SQL servers
> had issues about the same time.
> I didn't make any changes to any of the Dbs or the SQL server that I can
> remember.
> Do I need to register the SQL server with Active Directory? I upgraded
the
> network from NT4 to W2003 and AD.
>
Thursday, March 8, 2012
Database Maintenance Plan no longer deleting old files
My maintenance plan is set up to delete the old database dump files and transaction logs. After months of this working, the dump files are no longer being deleted. This has happened before. I recreated the plan and it worked for a while, then stopped again. The old transaction logs are being deleted as scheduled. Please help.Below KB might help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;303292&Product=sql2k
Also, check out below great troubleshooting suggestions from Bill H at MS:
-- Log files don't delete --
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Smith" <anonymous@.discussions.microsoft.com> wrote in message
news:B0355203-D93B-44F1-AD39-9EEE5194DEE3@.microsoft.com...
> My maintenance plan is set up to delete the old database dump files and transaction logs. After
months of this working, the dump files are no longer being deleted. This has happened before. I
recreated the plan and it worked for a while, then stopped again. The old transaction logs are
being deleted as scheduled. Please help.|||"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in message news:<O7uyC2XxDHA.3224@.tk2msftngp13.phx.gbl>...
> Below KB might help:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;303292&Product=sql2k
>
> Also, check out below great troubleshooting suggestions from Bill H at MS:
>
> -- Log files don't delete --
> This is likely to be either a permissions problem or a sharing violation
> problem. The maintenance plan is run as a job, and jobs are run by the
> SQLServerAgent service.
> Permissions:
> 1. Determine the startup account for the SQLServerAgent service
> (Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
> account is the security context for jobs, and thus the maintenance plan.
> 2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
> account) then skip step 3.
> 3. On that box, log onto NT as that account. Using Explorer, attempt to
> delete an expired backup. If that succeeds then go to Sharing Violation
> section.
> 4. Log onto NT with an account that is an administrator and use Explorer to
> look at the Properties|Security of the folder (where the backups reside)
> and ensure the SQLServerAgent startup account has Full Control. If the
> SQLServerAgent startup account is LocalSystem, then the account to consider
> is SYSTEM.
> 5. In NT, if an account is a member of an NT group, and if that group has
> Access is Denied, then that account will have Access is Denied, even if
> that account is also a member of the Administrators group. Thus you may
> need to check group permissions (if the Startup Account is a member of a
> group).
> 6. Keep in mind that permissions (by default) are inherited from a parent
> folder. Thus, if the backups are stored in C:\bak, and if someone had
> denied permission to the SQLServerAgent startup account for C:\, then
> C:\bak will inherit access is denied.
> Sharing violation:
> This is likely to be rooted in a timing issue, with the most likely cause
> being another scheduled process (such as NT Backup or Anti-Virus software)
> having the backup file open at the time when the SQLServerAgent (i.e., the
> maintenance plan job) tried to delete it.
> 1. Download filemon and handle from www.sysinternals.com.
> 2. I am not sure whether filemon can be scheduled, or you might be able to
> use NT scheduling services to start filemon just before the maintenance
> plan job is started, but the filemon log can become very large, so it would
> be best to start it some short time before the maintenance plan starts.
> 3. Inspect the filemon log for another process that has that backup file
> open (if your lucky enough to have started filemon before this other
> process grabs the backup folder), and inspect the log for the results when
> the SQLServerAgent agent attempts to open that same file.
> 4. Schedule the job or that other process to do their work at different
> times.
> 5. You can use the handle utility if you are around at the time when the
> job is scheduled to run.
> If the backup files are going to a \\share or a mapped drive (as opposed to
> local drive), then you will need to modify the above (with respect to where
> the tests and utilities are run).
> Finally, inspection of the maintenance plan's history report might be
> useful.
> Thanks,
> Bill Hollinshead
> Microsoft, SQL Server
>
>
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Smith" <anonymous@.discussions.microsoft.com> wrote in message
> news:B0355203-D93B-44F1-AD39-9EEE5194DEE3@.microsoft.com...
> > My maintenance plan is set up to delete the old database dump files and transaction logs. After
> months of this working, the dump files are no longer being deleted. This has happened before. I
> recreated the plan and it worked for a while, then stopped again. The old transaction logs are
> being deleted as scheduled. Please help.
You may also want to check what the 'effective' date is on your job -
see if your date range is out of whack, or else, if the process that
is supposed to be deleting the files is running into a 'file lock'. I
have had problems before like this, where a process that copies my old
backup files to a new directory was not actually terminating all the
time, and so then whenever the other process tried to delete them, it
couldn't. If you can look at that - it may help - or else, try
rebooting the server (if you can) and waiting to see if it behaves
normally again.
When in doubt, reboot *grin*
Sonya
http://support.microsoft.com/default.aspx?scid=kb;en-us;303292&Product=sql2k
Also, check out below great troubleshooting suggestions from Bill H at MS:
-- Log files don't delete --
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Smith" <anonymous@.discussions.microsoft.com> wrote in message
news:B0355203-D93B-44F1-AD39-9EEE5194DEE3@.microsoft.com...
> My maintenance plan is set up to delete the old database dump files and transaction logs. After
months of this working, the dump files are no longer being deleted. This has happened before. I
recreated the plan and it worked for a while, then stopped again. The old transaction logs are
being deleted as scheduled. Please help.|||"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in message news:<O7uyC2XxDHA.3224@.tk2msftngp13.phx.gbl>...
> Below KB might help:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;303292&Product=sql2k
>
> Also, check out below great troubleshooting suggestions from Bill H at MS:
>
> -- Log files don't delete --
> This is likely to be either a permissions problem or a sharing violation
> problem. The maintenance plan is run as a job, and jobs are run by the
> SQLServerAgent service.
> Permissions:
> 1. Determine the startup account for the SQLServerAgent service
> (Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
> account is the security context for jobs, and thus the maintenance plan.
> 2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
> account) then skip step 3.
> 3. On that box, log onto NT as that account. Using Explorer, attempt to
> delete an expired backup. If that succeeds then go to Sharing Violation
> section.
> 4. Log onto NT with an account that is an administrator and use Explorer to
> look at the Properties|Security of the folder (where the backups reside)
> and ensure the SQLServerAgent startup account has Full Control. If the
> SQLServerAgent startup account is LocalSystem, then the account to consider
> is SYSTEM.
> 5. In NT, if an account is a member of an NT group, and if that group has
> Access is Denied, then that account will have Access is Denied, even if
> that account is also a member of the Administrators group. Thus you may
> need to check group permissions (if the Startup Account is a member of a
> group).
> 6. Keep in mind that permissions (by default) are inherited from a parent
> folder. Thus, if the backups are stored in C:\bak, and if someone had
> denied permission to the SQLServerAgent startup account for C:\, then
> C:\bak will inherit access is denied.
> Sharing violation:
> This is likely to be rooted in a timing issue, with the most likely cause
> being another scheduled process (such as NT Backup or Anti-Virus software)
> having the backup file open at the time when the SQLServerAgent (i.e., the
> maintenance plan job) tried to delete it.
> 1. Download filemon and handle from www.sysinternals.com.
> 2. I am not sure whether filemon can be scheduled, or you might be able to
> use NT scheduling services to start filemon just before the maintenance
> plan job is started, but the filemon log can become very large, so it would
> be best to start it some short time before the maintenance plan starts.
> 3. Inspect the filemon log for another process that has that backup file
> open (if your lucky enough to have started filemon before this other
> process grabs the backup folder), and inspect the log for the results when
> the SQLServerAgent agent attempts to open that same file.
> 4. Schedule the job or that other process to do their work at different
> times.
> 5. You can use the handle utility if you are around at the time when the
> job is scheduled to run.
> If the backup files are going to a \\share or a mapped drive (as opposed to
> local drive), then you will need to modify the above (with respect to where
> the tests and utilities are run).
> Finally, inspection of the maintenance plan's history report might be
> useful.
> Thanks,
> Bill Hollinshead
> Microsoft, SQL Server
>
>
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Smith" <anonymous@.discussions.microsoft.com> wrote in message
> news:B0355203-D93B-44F1-AD39-9EEE5194DEE3@.microsoft.com...
> > My maintenance plan is set up to delete the old database dump files and transaction logs. After
> months of this working, the dump files are no longer being deleted. This has happened before. I
> recreated the plan and it worked for a while, then stopped again. The old transaction logs are
> being deleted as scheduled. Please help.
You may also want to check what the 'effective' date is on your job -
see if your date range is out of whack, or else, if the process that
is supposed to be deleting the files is running into a 'file lock'. I
have had problems before like this, where a process that copies my old
backup files to a new directory was not actually terminating all the
time, and so then whenever the other process tried to delete them, it
couldn't. If you can look at that - it may help - or else, try
rebooting the server (if you can) and waiting to see if it behaves
normally again.
When in doubt, reboot *grin*
Sonya
Database Maintenance Plan
Hello, everyone:
I have a Database Maintenance Plan that back up some databases and delete old backup files that more than two day. Can any one have idea which action is first, backup or delete old files?
Thanks
ZYTIt backs up first then deletes.
I have a Database Maintenance Plan that back up some databases and delete old backup files that more than two day. Can any one have idea which action is first, backup or delete old files?
Thanks
ZYTIt backs up first then deletes.
Wednesday, March 7, 2012
Database Maintanence not deleting old backups
I have a database maintanence plan set up to backup all my SQL 2000
databases and to delete the backups older than 3 days. It doesn't delete the
old ones. Is this a bug or am I just missing something?You may be missing something.
Check the extention that you defined to delete. Check the folder that you
chose to delete the backup files.
Also, check the maintanence plan history for more info.
--
Ekrem Önsoy
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:uO3WSRoNIHA.5360@.TK2MSFTNGP03.phx.gbl...
>I have a database maintanence plan set up to backup all my SQL 2000
>databases and to delete the backups older than 3 days. It doesn't delete
>the old ones. Is this a bug or am I just missing something?
>
databases and to delete the backups older than 3 days. It doesn't delete the
old ones. Is this a bug or am I just missing something?You may be missing something.
Check the extention that you defined to delete. Check the folder that you
chose to delete the backup files.
Also, check the maintanence plan history for more info.
--
Ekrem Önsoy
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:uO3WSRoNIHA.5360@.TK2MSFTNGP03.phx.gbl...
>I have a database maintanence plan set up to backup all my SQL 2000
>databases and to delete the backups older than 3 days. It doesn't delete
>the old ones. Is this a bug or am I just missing something?
>
Database Maintanence not deleting old backups
I have a database maintanence plan set up to backup all my SQL 2000
databases and to delete the backups older than 3 days. It doesn't delete the
old ones. Is this a bug or am I just missing something?
You may be missing something.
Check the extention that you defined to delete. Check the folder that you
chose to delete the backup files.
Also, check the maintanence plan history for more info.
Ekrem nsoy
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:uO3WSRoNIHA.5360@.TK2MSFTNGP03.phx.gbl...
>I have a database maintanence plan set up to backup all my SQL 2000
>databases and to delete the backups older than 3 days. It doesn't delete
>the old ones. Is this a bug or am I just missing something?
>
databases and to delete the backups older than 3 days. It doesn't delete the
old ones. Is this a bug or am I just missing something?
You may be missing something.
Check the extention that you defined to delete. Check the folder that you
chose to delete the backup files.
Also, check the maintanence plan history for more info.
Ekrem nsoy
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:uO3WSRoNIHA.5360@.TK2MSFTNGP03.phx.gbl...
>I have a database maintanence plan set up to backup all my SQL 2000
>databases and to delete the backups older than 3 days. It doesn't delete
>the old ones. Is this a bug or am I just missing something?
>
Database Maintanence not deleting old backups
I have a database maintanence plan set up to backup all my SQL 2000
databases and to delete the backups older than 3 days. It doesn't delete the
old ones. Is this a bug or am I just missing something?You may be missing something.
Check the extention that you defined to delete. Check the folder that you
chose to delete the backup files.
Also, check the maintanence plan history for more info.
Ekrem nsoy
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:uO3WSRoNIHA.5360@.TK2MSFTNGP03.phx.gbl...
>I have a database maintanence plan set up to backup all my SQL 2000
>databases and to delete the backups older than 3 days. It doesn't delete
>the old ones. Is this a bug or am I just missing something?
>
databases and to delete the backups older than 3 days. It doesn't delete the
old ones. Is this a bug or am I just missing something?You may be missing something.
Check the extention that you defined to delete. Check the folder that you
chose to delete the backup files.
Also, check the maintanence plan history for more info.
Ekrem nsoy
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:uO3WSRoNIHA.5360@.TK2MSFTNGP03.phx.gbl...
>I have a database maintanence plan set up to backup all my SQL 2000
>databases and to delete the backups older than 3 days. It doesn't delete
>the old ones. Is this a bug or am I just missing something?
>
Friday, February 17, 2012
database log file size
I want to ask what are the impacts if I limit the file size to certain MBs and will it report (File is full) or overwrite old data when the file reachs the assigned size?
you have to configure an alert (several MB) before log gets full.
when the log gets full no change in the database shall be committed.
|||
but is it true that SQL Server will be faster if the allocated size for the log file was larger?
|||
Jassim,
Perhaps you are referring to an auto grow capability of data and log files. By default database files are created with auto grow option. Each time a file reaches it's full capacity it gets resized, by the specified amount (either fixed size or percentage). This operation has some negative impact on the database performance, so in general it should be avoided. The autogrow functionality is primarly useful in systems that are not closely monitored by an adminstrator, for example embedded applications.
So if you set the initial log size to be bigger, you avoid growing the log file on demand. You can monitor for the auto grow of log and data files using SQL Profiler by selecting Log File Auto Grow and Data File Auto Grow events.
Hope that helps.
Regards,
database log file size
I want to ask what are the impacts if I limit the file size to certain MBs and will it report (File is full) or overwrite old data when the file reachs the assigned size?
you have to configure an alert (several MB) before log gets full.
when the log gets full no change in the database shall be committed.
|||
but is it true that SQL Server will be faster if the allocated size for the log file was larger?
|||
Jassim,
Perhaps you are referring to an auto grow capability of data and log files. By default database files are created with auto grow option. Each time a file reaches it's full capacity it gets resized, by the specified amount (either fixed size or percentage). This operation has some negative impact on the database performance, so in general it should be avoided. The autogrow functionality is primarly useful in systems that are not closely monitored by an adminstrator, for example embedded applications.
So if you set the initial log size to be bigger, you avoid growing the log file on demand. You can monitor for the auto grow of log and data files using SQL Profiler by selecting Log File Auto Grow and Data File Auto Grow events.
Hope that helps.
Regards,
Subscribe to:
Posts (Atom)