Mantanace Plan not deleting old files

I have a maintanace Plan establishe that is working excep
for on nagging item. The plan does both full backups and
transaction log backups each day. It is supposed to
delete files older than 3 days old but does not. I have
to manually go and clear the old files on a regular basis
to keep from filling up the disk. I have not seen any
error or know what to look for to see if something is
wrong. I thought that if a full backup was done that it
emptyed the transaction logs but that dies not appear to
be the case either and is why I have the transition logs
in the mainance plan. Any information on how to get the
old fikes to delete?
Here is a good summary of the normal issues related to this by Bill from MS:
http://support.microsoft.com/default...;en-us;Q303292
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
Andrew J. Kelly SQL MVP
"Jim Abel" <jim.abel@.lmco.com> wrote in message
news:177f01c49cbe$504699e0$a301280a@.phx.gbl...
> I have a maintanace Plan establishe that is working excep
> for on nagging item. The plan does both full backups and
> transaction log backups each day. It is supposed to
> delete files older than 3 days old but does not. I have
> to manually go and clear the old files on a regular basis
> to keep from filling up the disk. I have not seen any
> error or know what to look for to see if something is
> wrong. I thought that if a full backup was done that it
> emptyed the transaction logs but that dies not appear to
> be the case either and is why I have the transition logs
> in the mainance plan. Any information on how to get the
> old fikes to delete?
|||i had the same problem. RIght-click on the maintenance plan and look at the
job history for any errors.
The problem I had was someone set up a maintenance plan to backup ALL
databases and to do transaction lo backups periodically. The trouble with
that is the system DBs (and any user DBs that are not set to FULL recovery
mode) cannot have Transaction log backups performed on them. So the Backups
were running, but the delete step was not running because the transaction log
backup step failed for some of the DBs.
hope that helps
"Andrew J. Kelly" wrote:

> Here is a good summary of the normal issues related to this by Bill from MS:
>
> http://support.microsoft.com/default...;en-us;Q303292
> 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
>
> --
> Andrew J. Kelly SQL MVP
>
> "Jim Abel" <jim.abel@.lmco.com> wrote in message
> news:177f01c49cbe$504699e0$a301280a@.phx.gbl...
>
>

Mantanace Plan not deleting old files

I have a maintanace Plan establishe that is working excep
for on nagging item. The plan does both full backups and
transaction log backups each day. It is supposed to
delete files older than 3 days old but does not. I have
to manually go and clear the old files on a regular basis
to keep from filling up the disk. I have not seen any
error or know what to look for to see if something is
wrong. I thought that if a full backup was done that it
emptyed the transaction logs but that dies not appear to
be the case either and is why I have the transition logs
in the mainance plan. Any information on how to get the
old fikes to delete?Here is a good summary of the normal issues related to this by Bill from MS:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q303292
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
Andrew J. Kelly SQL MVP
"Jim Abel" <jim.abel@.lmco.com> wrote in message
news:177f01c49cbe$504699e0$a301280a@.phx.gbl...
> I have a maintanace Plan establishe that is working excep
> for on nagging item. The plan does both full backups and
> transaction log backups each day. It is supposed to
> delete files older than 3 days old but does not. I have
> to manually go and clear the old files on a regular basis
> to keep from filling up the disk. I have not seen any
> error or know what to look for to see if something is
> wrong. I thought that if a full backup was done that it
> emptyed the transaction logs but that dies not appear to
> be the case either and is why I have the transition logs
> in the mainance plan. Any information on how to get the
> old fikes to delete?|||i had the same problem. RIght-click on the maintenance plan and look at the
job history for any errors.
The problem I had was someone set up a maintenance plan to backup ALL
databases and to do transaction lo backups periodically. The trouble with
that is the system DBs (and any user DBs that are not set to FULL recovery
mode) cannot have Transaction log backups performed on them. So the Backups
were running, but the delete step was not running because the transaction log
backup step failed for some of the DBs.
hope that helps
"Andrew J. Kelly" wrote:
> Here is a good summary of the normal issues related to this by Bill from MS:
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q303292
> 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
>
> --
> Andrew J. Kelly SQL MVP
>
> "Jim Abel" <jim.abel@.lmco.com> wrote in message
> news:177f01c49cbe$504699e0$a301280a@.phx.gbl...
> > I have a maintanace Plan establishe that is working excep
> > for on nagging item. The plan does both full backups and
> > transaction log backups each day. It is supposed to
> > delete files older than 3 days old but does not. I have
> > to manually go and clear the old files on a regular basis
> > to keep from filling up the disk. I have not seen any
> > error or know what to look for to see if something is
> > wrong. I thought that if a full backup was done that it
> > emptyed the transaction logs but that dies not appear to
> > be the case either and is why I have the transition logs
> > in the mainance plan. Any information on how to get the
> > old fikes to delete?
>
>

Managing 2000 and 2005

Dear all
I have now a default instance of SQL Server 2005 running on one PC and an
old default instance of SQL Server 2000 running on another PC.
I would like to administer both SQL Servers with the new SQL Server 2005
Management Studio. However, I am unable to register the SQL Server 2000 in
the SQL Server 2005 Management Studio.
Any help is appreciated.
Best regards
AdrianYou should be able to.
What problems are you seeing?
"Adrian" <adrian@.iai.uni-bonn.de> wrote in message
news:Ofpo5yH6GHA.4620@.TK2MSFTNGP02.phx.gbl...
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>|||Adrian wrote:
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>
"Unable to register" means what exactly? Are you getting an error
message? Management Studio is perfectly capable of working with a 2000
server, I do it all day long every day...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525017F.8020007@.realsqlguy.com...
> Adrian wrote:
>> Dear all
>> I have now a default instance of SQL Server 2005 running on one PC and an
>> old default instance of SQL Server 2000 running on another PC.
>> I would like to administer both SQL Servers with the new SQL Server 2005
>> Management Studio. However, I am unable to register the SQL Server 2000
>> in the SQL Server 2005 Management Studio.
>> Any help is appreciated.
>> Best regards
>> Adrian
> "Unable to register" means what exactly? Are you getting an error
> message? Management Studio is perfectly capable of working with a 2000
> server, I do it all day long every day...
Well, it is great to hear it. So I just need to figure out how.
I can connect to the SQL Server 2000 with the sqlcmd program within an eye's
blink. However, when I enter precisely the same connect data to the
register-dialog of the Management Studio it returns after quite a long time
a message with the error 10061.
So what am I doing wrong?
Adrian
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||You should be able to connect to a SQL Server 2000 box from the SQL Server
2005 tools (including SSMS, Profiler, and the Replication Monitor
(sqlmonitor).
--
Keith Kratochvil
"Adrian" <adrian@.iai.uni-bonn.de> wrote in message
news:Ofpo5yH6GHA.4620@.TK2MSFTNGP02.phx.gbl...
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>|||Adrian wrote:
> Well, it is great to hear it. So I just need to figure out how.
> I can connect to the SQL Server 2000 with the sqlcmd program within an eye's
> blink. However, when I enter precisely the same connect data to the
> register-dialog of the Management Studio it returns after quite a long time
> a message with the error 10061.
> So what am I doing wrong?
That error indicates that the connection was refused by the server. Is
SQL Server using TCP/IP? Listening on what port?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45250DE5.8030609@.realsqlguy.com...
> Adrian wrote:
>> Well, it is great to hear it. So I just need to figure out how.
>> I can connect to the SQL Server 2000 with the sqlcmd program within an
>> eye's blink. However, when I enter precisely the same connect data to the
>> register-dialog of the Management Studio it returns after quite a long
>> time a message with the error 10061.
>> So what am I doing wrong?
> That error indicates that the connection was refused by the server. Is
> SQL Server using TCP/IP? Listening on what port?
Yes, it listens on TCP/IP 2433 and requires encryption. The client libraries
on the SQL Server 2005 PC are set appriopriately, so sqlcmd has no problems
connecting to it. It is only the Management Studio that makes me ...
aaarrrgh.
Any ideas?
Adrian
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Adrian wrote:
> Yes, it listens on TCP/IP 2433 and requires encryption. The client libraries
> on the SQL Server 2005 PC are set appriopriately, so sqlcmd has no problems
> connecting to it. It is only the Management Studio that makes me ...
> aaarrrgh.
> Any ideas?
>
In the connection dialog in Management Studio, try specifying the server
name like this:
serverDNSname,2433
And in the Options of that connection dialog, make sure the "Encrypt
Connection" checkbox is marked...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Firewalls?
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525139C.1010502@.realsqlguy.com...
> Adrian wrote:
>> Yes, it listens on TCP/IP 2433 and requires encryption. The client
>> libraries on the SQL Server 2005 PC are set appriopriately, so sqlcmd has
>> no problems connecting to it. It is only the Management Studio that makes
>> me ... aaarrrgh.
>> Any ideas?
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Deal all
Thank you very much for the excellent and very quick help.
Yes, the connection is established.
The trick is:
i) to follow this advice:
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
but
ii) not to follow this one:
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
Now my sleep will be peaceful.
Best regards
Adrian
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525139C.1010502@.realsqlguy.com...
> Adrian wrote:
>> Yes, it listens on TCP/IP 2433 and requires encryption. The client
>> libraries on the SQL Server 2005 PC are set appriopriately, so sqlcmd has
>> no problems connecting to it. It is only the Management Studio that makes
>> me ... aaarrrgh.
>> Any ideas?
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com