Make a same copy of SQL Server to a new machine

Dear all,
Since my old server's harddisk drive nearly used up all the free
space, I need to copy it from new server. Can I simply copy all the dat and
log files to new server without detach it provided that there're no user
using it and after that I attach them back to new sql server? I'm afraid in
case there're something go wrong in my new server and I can still use the
old server. And how can I transfer my logins to new server? I read some
articles that it may has orphan users if without transferring them. Or if
anyone knows the proper procedures on coping data into new server. Please
help. Thanks
Best Rdgs
EllisSee if this helps: http://vyaskn.tripod.com/moving_sql_server.htm
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:ezwt5MlvEHA.3228@.TK2MSFTNGP12.phx.gbl...
> Dear all,
> Since my old server's harddisk drive nearly used up all the free
> space, I need to copy it from new server. Can I simply copy all the dat
and
> log files to new server without detach it provided that there're no user
> using it and after that I attach them back to new sql server? I'm afraid
in
> case there're something go wrong in my new server and I can still use the
> old server. And how can I transfer my logins to new server? I read some
> articles that it may has orphan users if without transferring them. Or if
> anyone knows the proper procedures on coping data into new server. Please
> help. Thanks
> Best Rdgs
> Ellis
>

Make a same copy of SQL Server to a new machine

Dear all,
Since my old server's harddisk drive nearly used up all the free
space, I need to copy it from new server. Can I simply copy all the dat and
log files to new server without detach it provided that there're no user
using it and after that I attach them back to new sql server? I'm afraid in
case there're something go wrong in my new server and I can still use the
old server. And how can I transfer my logins to new server? I read some
articles that it may has orphan users if without transferring them. Or if
anyone knows the proper procedures on coping data into new server. Please
help. Thanks
Best Rdgs
Ellis
See if this helps: http://vyaskn.tripod.com/moving_sql_server.htm
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:ezwt5MlvEHA.3228@.TK2MSFTNGP12.phx.gbl...
> Dear all,
> Since my old server's harddisk drive nearly used up all the free
> space, I need to copy it from new server. Can I simply copy all the dat
and
> log files to new server without detach it provided that there're no user
> using it and after that I attach them back to new sql server? I'm afraid
in
> case there're something go wrong in my new server and I can still use the
> old server. And how can I transfer my logins to new server? I read some
> articles that it may has orphan users if without transferring them. Or if
> anyone knows the proper procedures on coping data into new server. Please
> help. Thanks
> Best Rdgs
> Ellis
>

Make a same copy of SQL Server to a new machine

Dear all,
Since my old server's harddisk drive nearly used up all the free
space, I need to copy it from new server. Can I simply copy all the dat and
log files to new server without detach it provided that there're no user
using it and after that I attach them back to new sql server? I'm afraid in
case there're something go wrong in my new server and I can still use the
old server. And how can I transfer my logins to new server? I read some
articles that it may has orphan users if without transferring them. Or if
anyone knows the proper procedures on coping data into new server. Please
help. Thanks
Best Rdgs
EllisSee if this helps: http://vyaskn.tripod.com/moving_sql_server.htm
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:ezwt5MlvEHA.3228@.TK2MSFTNGP12.phx.gbl...
> Dear all,
> Since my old server's harddisk drive nearly used up all the free
> space, I need to copy it from new server. Can I simply copy all the dat
and
> log files to new server without detach it provided that there're no user
> using it and after that I attach them back to new sql server? I'm afraid
in
> case there're something go wrong in my new server and I can still use the
> old server. And how can I transfer my logins to new server? I read some
> articles that it may has orphan users if without transferring them. Or if
> anyone knows the proper procedures on coping data into new server. Please
> help. Thanks
> Best Rdgs
> Ellis
>

Maintenance plans not deleting old transaction log backups

I'm the dba for a large company and have setup many maintenance plans for our sql servers. One of the options I have set is to delete old backups of databases and transaction logs after 2 days. For some reason, the old database backups are being deleted, but the old transaction logs backups are not. I have them being put in the same directory. Anybody have any ideas why this is happening and what if any fix is available?

Those are separate items that you check off in the options for each step - are you sure you asked the wizard to do that? If possible, drop the old plans and recreate them, checking that section to make sure you select that option.

Other than missing the check box, I don't know what else might cause this. Both delete operations use the same delete stored procedure, so if one works, the other one should.

If you do change your plans and this happens again, check the event logs and the SQL Server error logs.

Maintenance Plans

When you setup a maintenance plan to back up a database and you give it the
option to delete a database older than 1 day. Does it delete the old backup
before it creates the new backup?
After. There's no setting for this, so you cannot change this behavior. Maint plans are totally
reworked in 2005, though.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<Patricia> wrote in message news:OVpW%23yfFGHA.3936@.TK2MSFTNGP12.phx.gbl...
> When you setup a maintenance plan to back up a database and you give it the option to delete a
> database older than 1 day. Does it delete the old backup before it creates the new backup?
>
>
|||The clean up routines will run last unless you have edited the job and
changed the order.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
<Patricia> wrote in message news:OVpW%23yfFGHA.3936@.TK2MSFTNGP12.phx.gbl...
> When you setup a maintenance plan to back up a database and you give it
> the option to delete a database older than 1 day. Does it delete the old
> backup before it creates the new backup?
>
>

Maintenance Plans

When you setup a maintenance plan to back up a database and you give it the
option to delete a database older than 1 day. Does it delete the old backup
before it creates the new backup?After. There's no setting for this, so you cannot change this behavior. Maint plans are totally
reworked in 2005, though.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<Patricia> wrote in message news:OVpW%23yfFGHA.3936@.TK2MSFTNGP12.phx.gbl...
> When you setup a maintenance plan to back up a database and you give it the option to delete a
> database older than 1 day. Does it delete the old backup before it creates the new backup?
>
>|||The clean up routines will run last unless you have edited the job and
changed the order.
--
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
<Patricia> wrote in message news:OVpW%23yfFGHA.3936@.TK2MSFTNGP12.phx.gbl...
> When you setup a maintenance plan to back up a database and you give it
> the option to delete a database older than 1 day. Does it delete the old
> backup before it creates the new backup?
>
>

Maintenance Plans

When you setup a maintenance plan to back up a database and you give it the
option to delete a database older than 1 day. Does it delete the old backup
before it creates the new backup?After. There's no setting for this, so you cannot change this behavior. Main
t plans are totally
reworked in 2005, though.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<Patricia> wrote in message news:OVpW%23yfFGHA.3936@.TK2MSFTNGP12.phx.gbl...
> When you setup a maintenance plan to back up a database and you give it th
e option to delete a
> database older than 1 day. Does it delete the old backup before it create
s the new backup?
>
>|||The clean up routines will run last unless you have edited the job and
changed the order.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
<Patricia> wrote in message news:OVpW%23yfFGHA.3936@.TK2MSFTNGP12.phx.gbl...
> When you setup a maintenance plan to back up a database and you give it
> the option to delete a database older than 1 day. Does it delete the old
> backup before it creates the new backup?
>
>

Maintenance Plan: Delete old files not working right

We do a full backup every night. For some reason the backup files are
staying on the server for 5 full days. Since each backup is 6GB this
is presenting a disk space problem. As far as we can tell, we've
changed all of our SQLServer Maintenance backup jobs to delete any
files older than 23 hours, and even rebooted the server to ensure any
old settings that were set for 5 day file deletion are gone.
Does anyone know why the server is continuing to store files as old as
5 days when we've set our systems up to delete after 23 hours? What
are we missing?
Thanks,
-Rob
Below KB might help:
http://support.microsoft.com/default...&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
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"RW" <rwuhrman@.hotmail.com> wrote in message news:a628b717.0410270951.39dc39f3@.posting.google.c om...
> We do a full backup every night. For some reason the backup files are
> staying on the server for 5 full days. Since each backup is 6GB this
> is presenting a disk space problem. As far as we can tell, we've
> changed all of our SQLServer Maintenance backup jobs to delete any
> files older than 23 hours, and even rebooted the server to ensure any
> old settings that were set for 5 day file deletion are gone.
> Does anyone know why the server is continuing to store files as old as
> 5 days when we've set our systems up to delete after 23 hours? What
> are we missing?
> Thanks,
> -Rob

Maintenance Plan: Delete old files not working right

We do a full backup every night. For some reason the backup files are
staying on the server for 5 full days. Since each backup is 6GB this
is presenting a disk space problem. As far as we can tell, we've
changed all of our SQLServer Maintenance backup jobs to delete any
files older than 23 hours, and even rebooted the server to ensure any
old settings that were set for 5 day file deletion are gone.
Does anyone know why the server is continuing to store files as old as
5 days when we've set our systems up to delete after 23 hours? What
are we missing?
Thanks,
-RobBelow 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
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"RW" <rwuhrman@.hotmail.com> wrote in message news:a628b717.0410270951.39dc39f3@.posting.google.com...
> We do a full backup every night. For some reason the backup files are
> staying on the server for 5 full days. Since each backup is 6GB this
> is presenting a disk space problem. As far as we can tell, we've
> changed all of our SQLServer Maintenance backup jobs to delete any
> files older than 23 hours, and even rebooted the server to ensure any
> old settings that were set for 5 day file deletion are gone.
> Does anyone know why the server is continuing to store files as old as
> 5 days when we've set our systems up to delete after 23 hours? What
> are we missing?
> Thanks,
> -Rob

Maintenance Plan: Delete old files not working right

We do a full backup every night. For some reason the backup files are
staying on the server for 5 full days. Since each backup is 6GB this
is presenting a disk space problem. As far as we can tell, we've
changed all of our SQLServer Maintenance backup jobs to delete any
files older than 23 hours, and even rebooted the server to ensure any
old settings that were set for 5 day file deletion are gone.
Does anyone know why the server is continuing to store files as old as
5 days when we've set our systems up to delete after 23 hours? What
are we missing?
Thanks,
-RobBelow KB might help:
http://support.microsoft.com/defaul...2&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
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"RW" <rwuhrman@.hotmail.com> wrote in message news:a628b717.0410270951.39dc39f3@.posting.googl
e.com...
> We do a full backup every night. For some reason the backup files are
> staying on the server for 5 full days. Since each backup is 6GB this
> is presenting a disk space problem. As far as we can tell, we've
> changed all of our SQLServer Maintenance backup jobs to delete any
> files older than 23 hours, and even rebooted the server to ensure any
> old settings that were set for 5 day file deletion are gone.
> Does anyone know why the server is continuing to store files as old as
> 5 days when we've set our systems up to delete after 23 hours? What
> are we missing?
> Thanks,
> -Rob

maintenance plan reports delete backup file fail but deletes it ok

Hi
I have a sql 2000 sp4 maintenance plan that is set to delete old dbs
over 2 days old. In the maintenance plan history it reports this
activity failing for one db, but the Message section reports 1 file
deleted. The transaction log backup delete works ok and reports
correctly. Any ideas?
Kev
Hey Kev,
(Don'cha hate it when no one replies to your question?) :-)
Even though the History states failure, does the physical file actually get
deleted, though? I've seen several times the "work" gets done even though
sqlmaint (for some reason) has problems and fails. I've never really paid
much attention to the History, myself. Maybe I should. But I always
right-click on the job (if it show failure) and check the jobsteps. Then, I
check the output file created by the Plan's job (backup, optimization, etc.).
Could you send the few lines of output from both the History (may need to
manually type) and the Message section of the output? Manybe I can see
something from them.
Thanks
TJ
"nsiadmin" wrote:

> Hi
> I have a sql 2000 sp4 maintenance plan that is set to delete old dbs
> over 2 days old. In the maintenance plan history it reports this
> activity failing for one db, but the Message section reports 1 file
> deleted. The transaction log backup delete works ok and reports
> correctly. Any ideas?
> Kev
>
|||On 21 Mar, 14:50, ToeJam <Toe...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> Hey Kev,
> (Don'cha hate it when no one replies to your question?) :-)
> Even though the History states failure, does the physical file actually get
> deleted, though? I've seen several times the "work" gets done even though
> sqlmaint (for some reason) has problems and fails. I've never really paid
> much attention to the History, myself. Maybe I should. But I always
> right-click on the job (if it show failure) and check the jobsteps. Then, I
> check the output file created by the Plan's job (backup, optimization, etc.).
> Could you send the few lines of output from both the History (may need to
> manually type) and the Message section of the output? Manybe I can see
> something from them.
> Thanks
> TJ
> "nsiadmin" wrote:
>
Hi TJ
thanks for your reply.
this is the log file from the maint job :
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
Server 'MHA-SQL01\SQL01' as 'MHACAREGROUP\CLU01SQLSVC' (trusted)
Starting maintenance plan 'MHA CareG1_SITE Mtnce plan' on 19/03/2007
20:00:02
[1] Database MHACareG1_SITE: Transaction Log Backup...
Destination: [G:\Program Files\Microsoft SQL Server\MSSQL
$SQL01\BACKUP\MHACareG1_SITE\MHACareG1_SITE_tlog_2 00703192000.TRN]
** Execution Time: 0 hrs, 0 mins, 9 secs **
[2] Database MHACareG1_SITE: Delete Old Backup Files...
2 file(s) deleted.
Deleting old text reports... 1 file(s) deleted.
End of maintenance plan 'MHA CareG1_SITE Mtnce plan' on 19/03/2007
20:00:11
SQLMAINT.EXE Process Exit Code: 0 (Success)
yet the maintenance plan history records :
Db Activity Status
End date Message
MHACareG1_site Delete old db backups X 19/03/07 20:31
2 files deleted
so it appears to do exactly what it says, but still reports it as
failed.
I am going to set up a new maint plan for this db to a different
folder with exactly the same details
Kev
|||That is interesting, not to mention odd.
Question; What else does this Maint. Plan do besides the TLog backup?
The job output states that the job (or step?) begins @. 20:00:02 and finishes
@. 20:00:11 (Execution Time: 9 secs). BUT, the History record shows the End
date (time) as 20:31. What else occurred within those 31 minutes? A
Database Backup, or an Optimization perhaps? Maybe it was one of those that
actually failed. Or are there any other Steps within the same Job?
TJ
"nsiadmin" wrote:

> On 21 Mar, 14:50, ToeJam <Toe...@.discussions.microsoft.com> wrote:
> Hi TJ
> thanks for your reply.
> this is the log file from the maint job :
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
> Server 'MHA-SQL01\SQL01' as 'MHACAREGROUP\CLU01SQLSVC' (trusted)
> Starting maintenance plan 'MHA CareG1_SITE Mtnce plan' on 19/03/2007
> 20:00:02
> [1] Database MHACareG1_SITE: Transaction Log Backup...
> Destination: [G:\Program Files\Microsoft SQL Server\MSSQL
> $SQL01\BACKUP\MHACareG1_SITE\MHACareG1_SITE_tlog_2 00703192000.TRN]
> ** Execution Time: 0 hrs, 0 mins, 9 secs **
> [2] Database MHACareG1_SITE: Delete Old Backup Files...
> 2 file(s) deleted.
> Deleting old text reports... 1 file(s) deleted.
> End of maintenance plan 'MHA CareG1_SITE Mtnce plan' on 19/03/2007
> 20:00:11
> SQLMAINT.EXE Process Exit Code: 0 (Success)
> yet the maintenance plan history records :
> Db Activity Status End date Message
> MHACareG1_site Delete old db backups X 19/03/07 20:31 2 files deleted
> so it appears to do exactly what it says, but still reports it as
> failed.
> I am going to set up a new maint plan for this db to a different
> folder with exactly the same details
> Kev
>
|||Hi Tj,
yes it does a db backup which works ok. The History record refers only
to the delete old files part of the job which ran at 20:31. All the
steps within the maint job are listed in the history as separate
activities, but only delete old files step fails.
Interestingly I set up the new job to run overnight, created 2 old
files in the destination folder, and everything worked ok.
Sometimes I guess its easier to just start again and forget it.
Cheers
Kev
On 21 Mar, 16:18, ToeJam <Toe...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> That is interesting, not to mention odd.
> Question; What else does this Maint. Plan do besides the TLog backup?
> The job output states that the job (or step?) begins @. 20:00:02 and finishes
> @. 20:00:11 (Execution Time: 9 secs). BUT, the History record shows the End
> date (time) as 20:31. What else occurred within those 31 minutes? A
> Database Backup, or an Optimization perhaps? Maybe it was one of those that
> actually failed. Or are there any other Steps within the same Job?
> TJ
> "nsiadmin" wrote:
>
>
>
>
>
>
>
>
>

maintenance plan reports delete backup file fail but deletes it ok

Hi
I have a sql 2000 sp4 maintenance plan that is set to delete old dbs
over 2 days old. In the maintenance plan history it reports this
activity failing for one db, but the Message section reports 1 file
deleted. The transaction log backup delete works ok and reports
correctly. Any ideas?
KevHey Kev,
(Don'cha hate it when no one replies to your question') :-)
Even though the History states failure, does the physical file actually get
deleted, though? I've seen several times the "work" gets done even though
sqlmaint (for some reason) has problems and fails. I've never really paid
much attention to the History, myself. Maybe I should. But I always
right-click on the job (if it show failure) and check the jobsteps. Then, I
check the output file created by the Plan's job (backup, optimization, etc.).
Could you send the few lines of output from both the History (may need to
manually type) and the Message section of the output? Manybe I can see
something from them.
Thanks
TJ
"nsiadmin" wrote:
> Hi
> I have a sql 2000 sp4 maintenance plan that is set to delete old dbs
> over 2 days old. In the maintenance plan history it reports this
> activity failing for one db, but the Message section reports 1 file
> deleted. The transaction log backup delete works ok and reports
> correctly. Any ideas?
> Kev
>|||On 21 Mar, 14:50, ToeJam <Toe...@.discussions.microsoft.com> wrote:
> Hey Kev,
> (Don'cha hate it when no one replies to your question') :-)
> Even though the History states failure, does the physical file actually get
> deleted, though? I've seen several times the "work" gets done even though
> sqlmaint (for some reason) has problems and fails. I've never really paid
> much attention to the History, myself. Maybe I should. But I always
> right-click on the job (if it show failure) and check the jobsteps. Then, I
> check the output file created by the Plan's job (backup, optimization, etc.).
> Could you send the few lines of output from both the History (may need to
> manually type) and the Message section of the output? Manybe I can see
> something from them.
> Thanks
> TJ
> "nsiadmin" wrote:
> > Hi
> > I have a sql 2000 sp4 maintenance plan that is set to delete old dbs
> > over 2 days old. In the maintenance plan history it reports this
> > activity failing for one db, but the Message section reports 1 file
> > deleted. The transaction log backup delete works ok and reports
> > correctly. Any ideas?
> > Kev
Hi TJ
thanks for your reply.
this is the log file from the maint job :
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
Server 'MHA-SQL01\SQL01' as 'MHACAREGROUP\CLU01SQLSVC' (trusted)
Starting maintenance plan 'MHA CareG1_SITE Mtnce plan' on 19/03/2007
20:00:02
[1] Database MHACareG1_SITE: Transaction Log Backup...
Destination: [G:\Program Files\Microsoft SQL Server\MSSQL
$SQL01\BACKUP\MHACareG1_SITE\MHACareG1_SITE_tlog_200703192000.TRN]
** Execution Time: 0 hrs, 0 mins, 9 secs **
[2] Database MHACareG1_SITE: Delete Old Backup Files...
2 file(s) deleted.
Deleting old text reports... 1 file(s) deleted.
End of maintenance plan 'MHA CareG1_SITE Mtnce plan' on 19/03/2007
20:00:11
SQLMAINT.EXE Process Exit Code: 0 (Success)
yet the maintenance plan history records :
Db Activity Status
End date Message
MHACareG1_site Delete old db backups X 19/03/07 20:31
2 files deleted
so it appears to do exactly what it says, but still reports it as
failed.
I am going to set up a new maint plan for this db to a different
folder with exactly the same details
Kev|||That is interesting, not to mention odd.
Question; What else does this Maint. Plan do besides the TLog backup?
The job output states that the job (or step?) begins @. 20:00:02 and finishes
@. 20:00:11 (Execution Time: 9 secs). BUT, the History record shows the End
date (time) as 20:31. What else occurred within those 31 minutes? A
Database Backup, or an Optimization perhaps? Maybe it was one of those that
actually failed. Or are there any other Steps within the same Job?
TJ
"nsiadmin" wrote:
> On 21 Mar, 14:50, ToeJam <Toe...@.discussions.microsoft.com> wrote:
> > Hey Kev,
> >
> > (Don'cha hate it when no one replies to your question') :-)
> >
> > Even though the History states failure, does the physical file actually get
> > deleted, though? I've seen several times the "work" gets done even though
> > sqlmaint (for some reason) has problems and fails. I've never really paid
> > much attention to the History, myself. Maybe I should. But I always
> > right-click on the job (if it show failure) and check the jobsteps. Then, I
> > check the output file created by the Plan's job (backup, optimization, etc.).
> >
> > Could you send the few lines of output from both the History (may need to
> > manually type) and the Message section of the output? Manybe I can see
> > something from them.
> > Thanks
> > TJ
> >
> > "nsiadmin" wrote:
> > > Hi
> >
> > > I have a sql 2000 sp4 maintenance plan that is set to delete old dbs
> > > over 2 days old. In the maintenance plan history it reports this
> > > activity failing for one db, but the Message section reports 1 file
> > > deleted. The transaction log backup delete works ok and reports
> > > correctly. Any ideas?
> >
> > > Kev
> Hi TJ
> thanks for your reply.
> this is the log file from the maint job :
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
> Server 'MHA-SQL01\SQL01' as 'MHACAREGROUP\CLU01SQLSVC' (trusted)
> Starting maintenance plan 'MHA CareG1_SITE Mtnce plan' on 19/03/2007
> 20:00:02
> [1] Database MHACareG1_SITE: Transaction Log Backup...
> Destination: [G:\Program Files\Microsoft SQL Server\MSSQL
> $SQL01\BACKUP\MHACareG1_SITE\MHACareG1_SITE_tlog_200703192000.TRN]
> ** Execution Time: 0 hrs, 0 mins, 9 secs **
> [2] Database MHACareG1_SITE: Delete Old Backup Files...
> 2 file(s) deleted.
> Deleting old text reports... 1 file(s) deleted.
> End of maintenance plan 'MHA CareG1_SITE Mtnce plan' on 19/03/2007
> 20:00:11
> SQLMAINT.EXE Process Exit Code: 0 (Success)
> yet the maintenance plan history records :
> Db Activity Status End date Message
> MHACareG1_site Delete old db backups X 19/03/07 20:31 2 files deleted
> so it appears to do exactly what it says, but still reports it as
> failed.
> I am going to set up a new maint plan for this db to a different
> folder with exactly the same details
> Kev
>|||Hi Tj,
yes it does a db backup which works ok. The History record refers only
to the delete old files part of the job which ran at 20:31. All the
steps within the maint job are listed in the history as separate
activities, but only delete old files step fails.
Interestingly I set up the new job to run overnight, created 2 old
files in the destination folder, and everything worked ok.
Sometimes I guess its easier to just start again and forget it.
Cheers
Kev
On 21 Mar, 16:18, ToeJam <Toe...@.discussions.microsoft.com> wrote:
> That is interesting, not to mention odd.
> Question; What else does this Maint. Plan do besides the TLog backup?
> The job output states that the job (or step?) begins @. 20:00:02 and finishes
> @. 20:00:11 (Execution Time: 9 secs). BUT, the History record shows the End
> date (time) as 20:31. What else occurred within those 31 minutes? A
> Database Backup, or an Optimization perhaps? Maybe it was one of those that
> actually failed. Or are there any other Steps within the same Job?
> TJ
> "nsiadmin" wrote:
> > On 21 Mar, 14:50, ToeJam <Toe...@.discussions.microsoft.com> wrote:
> > > Hey Kev,
> > > (Don'cha hate it when no one replies to your question') :-)
> > > Even though the History states failure, does the physical file actually get
> > > deleted, though? I've seen several times the "work" gets done even though
> > > sqlmaint (for some reason) has problems and fails. I've never really paid
> > > much attention to the History, myself. Maybe I should. But I always
> > > right-click on the job (if it show failure) and check the jobsteps. Then, I
> > > check the output file created by the Plan's job (backup, optimization, etc.).
> > > Could you send the few lines of output from both the History (may need to
> > > manually type) and the Message section of the output? Manybe I can see
> > > something from them.
> > > Thanks
> > > TJ
> > > "nsiadmin" wrote:
> > > > Hi
> > > > I have a sql 2000 sp4 maintenance plan that is set to delete old dbs
> > > > over 2 days old. In the maintenance plan history it reports this
> > > > activity failing for one db, but the Message section reports 1 file
> > > > deleted. The transaction log backup delete works ok and reports
> > > > correctly. Any ideas?
> > > > Kev
> > Hi TJ
> > thanks for your reply.
> > this is the log file from the maint job :
> > Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
> > Server 'MHA-SQL01\SQL01' as 'MHACAREGROUP\CLU01SQLSVC' (trusted)
> > Starting maintenance plan 'MHA CareG1_SITE Mtnce plan' on 19/03/2007
> > 20:00:02
> > [1] Database MHACareG1_SITE: Transaction Log Backup...
> > Destination: [G:\Program Files\Microsoft SQL Server\MSSQL
> > $SQL01\BACKUP\MHACareG1_SITE\MHACareG1_SITE_tlog_200703192000.TRN]
> > ** Execution Time: 0 hrs, 0 mins, 9 secs **
> > [2] Database MHACareG1_SITE: Delete Old Backup Files...
> > 2 file(s) deleted.
> > Deleting old text reports... 1 file(s) deleted.
> > End of maintenance plan 'MHA CareG1_SITE Mtnce plan' on 19/03/2007
> > 20:00:11
> > SQLMAINT.EXE Process Exit Code: 0 (Success)
> > yet the maintenance plan history records :
> > Db Activity Status End date Message
> > MHACareG1_site Delete old db backups X 19/03/07 20:31 2 files deleted
> > so it appears to do exactly what it says, but still reports it as
> > failed.
> > I am going to set up a new maint plan for this db to a different
> > folder with exactly the same details
> > Kev

maintenance plan reports delete backup file fail but deletes it ok

Hi
I have a sql 2000 sp4 maintenance plan that is set to delete old dbs
over 2 days old. In the maintenance plan history it reports this
activity failing for one db, but the Message section reports 1 file
deleted. The transaction log backup delete works ok and reports
correctly. Any ideas?
KevHey Kev,
(Don'cha hate it when no one replies to your question') :-)
Even though the History states failure, does the physical file actually get
deleted, though? I've seen several times the "work" gets done even though
sqlmaint (for some reason) has problems and fails. I've never really paid
much attention to the History, myself. Maybe I should. But I always
right-click on the job (if it show failure) and check the jobsteps. Then, I
check the output file created by the Plan's job (backup, optimization, etc.)
.
Could you send the few lines of output from both the History (may need to
manually type) and the Message section of the output? Manybe I can see
something from them.
Thanks
TJ
"nsiadmin" wrote:

> Hi
> I have a sql 2000 sp4 maintenance plan that is set to delete old dbs
> over 2 days old. In the maintenance plan history it reports this
> activity failing for one db, but the Message section reports 1 file
> deleted. The transaction log backup delete works ok and reports
> correctly. Any ideas?
> Kev
>|||On 21 Mar, 14:50, ToeJam <Toe...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> Hey Kev,
> (Don'cha hate it when no one replies to your question') :-)
> Even though the History states failure, does the physical file actually ge
t
> deleted, though? I've seen several times the "work" gets done even though
> sqlmaint (for some reason) has problems and fails. I've never really paid
> much attention to the History, myself. Maybe I should. But I always
> right-click on the job (if it show failure) and check the jobsteps. Then,
I
> check the output file created by the Plan's job (backup, optimization, etc
.).
> Could you send the few lines of output from both the History (may need to
> manually type) and the Message section of the output? Manybe I can see
> something from them.
> Thanks
> TJ
> "nsiadmin" wrote:
>
>
Hi TJ
thanks for your reply.
this is the log file from the maint job :
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
Server 'MHA-SQL01\SQL01' as 'MHACAREGROUP\CLU01SQLSVC' (trusted)
Starting maintenance plan 'MHA CareG1_SITE Mtnce plan' on 19/03/2007
20:00:02
[1] Database MHACareG1_SITE: Transaction Log Backup...
Destination: [G:\Program Files\Microsoft SQL Server\MSSQL
$SQL01\BACKUP\MHACareG1_SITE\MHACareG1_S
ITE_tlog_200703192000.TRN]
** Execution Time: 0 hrs, 0 mins, 9 secs **
[2] Database MHACareG1_SITE: Delete Old Backup Files...
2 file(s) deleted.
Deleting old text reports... 1 file(s) deleted.
End of maintenance plan 'MHA CareG1_SITE Mtnce plan' on 19/03/2007
20:00:11
SQLMAINT.EXE Process Exit Code: 0 (Success)
yet the maintenance plan history records :
Db Activity Status
End date Message
MHACareG1_site Delete old db backups X 19/03/07 20:31
2 files deleted
so it appears to do exactly what it says, but still reports it as
failed.
I am going to set up a new maint plan for this db to a different
folder with exactly the same details
Kev