Hello:
A client of mine is using SQL Server 2000 and has constructed a database
maintenance job to do "Complete Backup" and "Transaction Log Backup".
In another thread, I had asked why the job was not deleting its own backups
files as the job is configured to delete backups after one day.
Someone had replied and said that the deletions will not take effect until
the backup job completes successfully.
Since the backup files are not deleting, does that mean that the backup job
is not being successful?
If that's the case, then, I don't know what the client is doing wrong. It's
not hard to set up a backup job in the database maintenance plan.
I mean, does the SQL Server Service need to be stopped in order for these
backups to take place successfully?
Thanks!
childofthe1980s
Hi,
Before i suggest u any thing just check the maintinance plan log file.
It is not true that backup will not delete till the next backup is
successful.
Check maintinance plan again and make sure that u had selected one
day(delete old files)
check the path on the backup.
hope this helps
from
Killer
Showing posts with label backup. Show all posts
Showing posts with label backup. Show all posts
Tuesday, March 27, 2012
are backups not successful?
Hello:
A client of mine is using SQL Server 2000 and has constructed a database
maintenance job to do "Complete Backup" and "Transaction Log Backup".
In another thread, I had asked why the job was not deleting its own backups
files as the job is configured to delete backups after one day.
Someone had replied and said that the deletions will not take effect until
the backup job completes successfully.
Since the backup files are not deleting, does that mean that the backup job
is not being successful?
If that's the case, then, I don't know what the client is doing wrong. It's
not hard to set up a backup job in the database maintenance plan.
I mean, does the SQL Server Service need to be stopped in order for these
backups to take place successfully?
Thanks!
childofthe1980sHi,
Before i suggest u any thing just check the maintinance plan log file.
It is not true that backup will not delete till the next backup is
successful.
Check maintinance plan again and make sure that u had selected one
day(delete old files)
check the path on the backup.
hope this helps
from
Killersql
A client of mine is using SQL Server 2000 and has constructed a database
maintenance job to do "Complete Backup" and "Transaction Log Backup".
In another thread, I had asked why the job was not deleting its own backups
files as the job is configured to delete backups after one day.
Someone had replied and said that the deletions will not take effect until
the backup job completes successfully.
Since the backup files are not deleting, does that mean that the backup job
is not being successful?
If that's the case, then, I don't know what the client is doing wrong. It's
not hard to set up a backup job in the database maintenance plan.
I mean, does the SQL Server Service need to be stopped in order for these
backups to take place successfully?
Thanks!
childofthe1980sHi,
Before i suggest u any thing just check the maintinance plan log file.
It is not true that backup will not delete till the next backup is
successful.
Check maintinance plan again and make sure that u had selected one
day(delete old files)
check the path on the backup.
hope this helps
from
Killersql
are backups not successful?
Hello:
A client of mine is using SQL Server 2000 and has constructed a database
maintenance job to do "Complete Backup" and "Transaction Log Backup".
In another thread, I had asked why the job was not deleting its own backups
files as the job is configured to delete backups after one day.
Someone had replied and said that the deletions will not take effect until
the backup job completes successfully.
Since the backup files are not deleting, does that mean that the backup job
is not being successful?
If that's the case, then, I don't know what the client is doing wrong. It's
not hard to set up a backup job in the database maintenance plan.
I mean, does the SQL Server Service need to be stopped in order for these
backups to take place successfully?
Thanks!
childofthe1980sHi,
Before i suggest u any thing just check the maintinance plan log file.
--
It is not true that backup will not delete till the next backup is
successful.
Check maintinance plan again and make sure that u had selected one
day(delete old files)
check the path on the backup.
hope this helps
from
Killer
A client of mine is using SQL Server 2000 and has constructed a database
maintenance job to do "Complete Backup" and "Transaction Log Backup".
In another thread, I had asked why the job was not deleting its own backups
files as the job is configured to delete backups after one day.
Someone had replied and said that the deletions will not take effect until
the backup job completes successfully.
Since the backup files are not deleting, does that mean that the backup job
is not being successful?
If that's the case, then, I don't know what the client is doing wrong. It's
not hard to set up a backup job in the database maintenance plan.
I mean, does the SQL Server Service need to be stopped in order for these
backups to take place successfully?
Thanks!
childofthe1980sHi,
Before i suggest u any thing just check the maintinance plan log file.
--
It is not true that backup will not delete till the next backup is
successful.
Check maintinance plan again and make sure that u had selected one
day(delete old files)
check the path on the backup.
hope this helps
from
Killer
ArcServ and SQl Server 2000
Hi,
I am trying to create a backup agent for a SQl Server. I have given the information for the following: instance, AUTHENTICATION, USERNAME, PASSWORD, CONFIRM PASSWORD.
I keep getting the error message, enter valid instance, even though i am entering in the instance.
any ideas?
Is this a named instance? Do you have any special characters like dashes in the server name?
-Sue
|||Problem solved ? If yes, post how you solved it, or if the hint from Sue helped you′.
Jens K. Suessmeyer
http://www.sqlserver2005.de
Archiving AS 2000 Database to a network backup server
WE are currently using the following to archive our AS 2000 OLAP cubes to the local directory on the server:
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\DataMart" "DataMart" "c:\BackupFiles\DataMart.cab" It runs inside an agent job. It works fine.
I wanted to change it to archive to our standard backup server location. So I changed it to the following:
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\DataMart" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\ServerName\DataMart.cab". The job now fails & outputs nothing to the log file. The only thing it says when I view history on the job is : Executed as user: SqlAdmin. The step did not generate any output. Process Exit Code 1. The step failed.
At first I thought maybe AS 2000 couldn't archive over the network so I open up AS Manager & manually did an archive to the same network location. It was successfull. So that blew my theory.
I don't know why the job won't do the archive to the network location. Any ideas?
Thanks,
John
If you can manually run the command
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\DataMart" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\ServerName\DataMart.cab"
then it's possible that the SqlAdmin user doesn't have write permissions to the share.
Adrian
|||Adrian,
I forgot to mention that SQLAdmin does have privileges to the network backup location. We use this same login for all our SQL backups as well.
I wasn't ever able to get the command to run manually. I was able to manually run the archive process through Analysis manager. Don't know if that makes a difference or not.
Any other ideas?
Thanks,
JOhn
|||Unless you have changed the default data directory, I think you have an incorrect "datamart" sub folder in your data directory parameter.
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\DataMart" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\ServerName\DataMart.cab"
try removing it and see if the command works then.
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\ServerName\DataMart.cab"
Also, where are you running Analysis Manager from? Judging by the (x86) in the path I would say that your AS2k server is 64bit and all the management tools (including msmdarch.exe) are 32 bit. The last recommendation I saw said to try to run these tools from a 32bit machine and not on the 64bit server. I don't know if that means it would not work, but it might be another option to explore.
|||Darren,
I removed the extra "datamart" from the command but same result.
Sorry I didn't mention this earlier. I am running W2K3 64 bit with AS 2000 32 bit. I was running Analysis Manager on the 64 bit server when I was able to do the archive manually. WIth this command, I am running it under SQL 2005 EE 64 bit agent job.
I tried running the following command from our 32 bit test server but it had the same result:
"C:\Program Files\Microsoft Analysis Services\Bin\msmdarch" /a 64BitServer"C:\Program Files (x86)\Microsoft Analysis Services\Data\" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\64BitServer\DataMart.cab"
Any other ideas?
Thanks,
John
|||Hmm, running out of ideas.
Have you tried mapping a drive so that you are backing up to z:\... or something like that?
Have you tried specifying the other 2 optional parameter (the logfile and tempfolder)? The log file might give you some ideas, although it might be blank, I seem to remember having trouble like this once, but I can't remember how I resolved it.
Finally, if all else fails there was some documentation, I think in the operations guide whitepaper, on how to "manually" back up an AS2k server by taking a file back up of the data directory and the repository database.
|||Darren,
A mapped drive seems to work. Although, I don't like using mapped drives on our servers but I may have to make an exception in this instance. Maybe I will have it archive locally & then execute a batch job that would xcopy the .cab file to the backup server.
I also tried adding the log & temp folder parameters but that did not make any difference. I still got the useless blank log file. 
Thanks for the help,
JOhn
|||Hello,
Enjoyed reading the thread, I had a thought that might be helpful:
You might try enabling UNC support for your command prompt. By default, Microsoft ships this flag turned off, but I've yet to have any trouble with it turned on. YMMV.
Microsoft KB156276 instructions for doing this:
Under the registry path:
HKEY_CURRENT_USER
\Software
\Microsoft
\Command Processor
add the value DisableUNCCheck REG_DWORD and set the value to 0 x 1 (Hex).
http://support.microsoft.com/kb/156276
I hope this helps you. Good luck...!
-ed2
|||Ed,
Thanks for the thought. I added this to the registry & then ran my job but same result. It may need to have a reboot to get the change into effect. However, the KB article lists this as a bug for Win NT 4 & states that it would be fixed in a SP. So I would hope that this has been fixed in Windows 2003 server. I will leave it until after a reboot to see if it works or not.
THe batch job is working great btw.
John
|||I'm sorry to hear this wasn't a fix... WIth only 8 months of mainstream support remaining on SQL Server 2000, it's hard to imagine this will get much attention, but you might try opening a call if you can justify the expense...
Read the KB article I sent you over again, and you'll find out that the fix is in Win2K, XP, and Win2K3. The KB article said that NT4 originally had no check for UNC pathing in the command prompt, and that caused problems for users who would launch Windows apps from the command prompt session, then close the command prompt and the pipeline to the exe file would become broken. To remedy this Microsoft changed CMD.EXE such that whenever you use a UNC path at the command line it produces an error message UNLESS you put in the registry entry from the KB article. So basically the fix was to decide that it was inappropriate to use UNC pathing at the command prompt. However, I think that once you understand the limitations (and know what not to do), the benefits gained by using the UNC pathing outweigh the risks.
In one of the earlier posts it sounded as though you might be running the job from SQL Server Agent. I've seen some odd behavior from that in some ways -- for example, I wasn't able to call an osql command from SQL Server Agent using xp_cmdshell (pointless as that might seem). So, if you haven't already done so, try the Windows Job Scheduler instead.
Best wishes,
Ed
Archiving AS 2000 Database to a network backup server
WE are currently using the following to archive our AS 2000 OLAP cubes to the local directory on the server:
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\DataMart" "DataMart" "c:\BackupFiles\DataMart.cab" It runs inside an agent job. It works fine.
I wanted to change it to archive to our standard backup server location. So I changed it to the following:
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\DataMart" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\ServerName\DataMart.cab". The job now fails & outputs nothing to the log file. The only thing it says when I view history on the job is : Executed as user: SqlAdmin. The step did not generate any output. Process Exit Code 1. The step failed.
At first I thought maybe AS 2000 couldn't archive over the network so I open up AS Manager & manually did an archive to the same network location. It was successfull. So that blew my theory.
I don't know why the job won't do the archive to the network location. Any ideas?
Thanks,
John
If you can manually run the command
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\DataMart" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\ServerName\DataMart.cab"
then it's possible that the SqlAdmin user doesn't have write permissions to the share.
Adrian
|||Adrian,
I forgot to mention that SQLAdmin does have privileges to the network backup location. We use this same login for all our SQL backups as well.
I wasn't ever able to get the command to run manually. I was able to manually run the archive process through Analysis manager. Don't know if that makes a difference or not.
Any other ideas?
Thanks,
JOhn
|||Unless you have changed the default data directory, I think you have an incorrect "datamart" sub folder in your data directory parameter.
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\DataMart" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\ServerName\DataMart.cab"
try removing it and see if the command works then.
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\ServerName\DataMart.cab"
Also, where are you running Analysis Manager from? Judging by the (x86) in the path I would say that your AS2k server is 64bit and all the management tools (including msmdarch.exe) are 32 bit. The last recommendation I saw said to try to run these tools from a 32bit machine and not on the 64bit server. I don't know if that means it would not work, but it might be another option to explore.
|||Darren,
I removed the extra "datamart" from the command but same result.
Sorry I didn't mention this earlier. I am running W2K3 64 bit with AS 2000 32 bit. I was running Analysis Manager on the 64 bit server when I was able to do the archive manually. WIth this command, I am running it under SQL 2005 EE 64 bit agent job.
I tried running the following command from our 32 bit test server but it had the same result:
"C:\Program Files\Microsoft Analysis Services\Bin\msmdarch" /a 64BitServer"C:\Program Files (x86)\Microsoft Analysis Services\Data\" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\64BitServer\DataMart.cab"
Any other ideas?
Thanks,
John
|||Hmm, running out of ideas.
Have you tried mapping a drive so that you are backing up to z:\... or something like that?
Have you tried specifying the other 2 optional parameter (the logfile and tempfolder)? The log file might give you some ideas, although it might be blank, I seem to remember having trouble like this once, but I can't remember how I resolved it.
Finally, if all else fails there was some documentation, I think in the operations guide whitepaper, on how to "manually" back up an AS2k server by taking a file back up of the data directory and the repository database.
|||Darren,
A mapped drive seems to work. Although, I don't like using mapped drives on our servers but I may have to make an exception in this instance. Maybe I will have it archive locally & then execute a batch job that would xcopy the .cab file to the backup server.
I also tried adding the log & temp folder parameters but that did not make any difference. I still got the useless blank log file.
Thanks for the help,
JOhn
|||Hello,
Enjoyed reading the thread, I had a thought that might be helpful:
You might try enabling UNC support for your command prompt. By default, Microsoft ships this flag turned off, but I've yet to have any trouble with it turned on. YMMV.
Microsoft KB156276 instructions for doing this:
Under the registry path:
HKEY_CURRENT_USER
\Software
\Microsoft
\Command Processor
add the value DisableUNCCheck REG_DWORD and set the value to 0 x 1 (Hex).
http://support.microsoft.com/kb/156276
I hope this helps you. Good luck...!
-ed2
|||Ed,
Thanks for the thought. I added this to the registry & then ran my job but same result. It may need to have a reboot to get the change into effect. However, the KB article lists this as a bug for Win NT 4 & states that it would be fixed in a SP. So I would hope that this has been fixed in Windows 2003 server. I will leave it until after a reboot to see if it works or not.
THe batch job is working great btw.
John
|||I'm sorry to hear this wasn't a fix... WIth only 8 months of mainstream support remaining on SQL Server 2000, it's hard to imagine this will get much attention, but you might try opening a call if you can justify the expense...
Read the KB article I sent you over again, and you'll find out that the fix is in Win2K, XP, and Win2K3. The KB article said that NT4 originally had no check for UNC pathing in the command prompt, and that caused problems for users who would launch Windows apps from the command prompt session, then close the command prompt and the pipeline to the exe file would become broken. To remedy this Microsoft changed CMD.EXE such that whenever you use a UNC path at the command line it produces an error message UNLESS you put in the registry entry from the KB article. So basically the fix was to decide that it was inappropriate to use UNC pathing at the command prompt. However, I think that once you understand the limitations (and know what not to do), the benefits gained by using the UNC pathing outweigh the risks.
In one of the earlier posts it sounded as though you might be running the job from SQL Server Agent. I've seen some odd behavior from that in some ways -- for example, I wasn't able to call an osql command from SQL Server Agent using xp_cmdshell (pointless as that might seem). So, if you haven't already done so, try the Windows Job Scheduler instead.
Best wishes,
Ed
Archiving AS 2000 Database to a network backup server
WE are currently using the following to archive our AS 2000 OLAP cubes to the local directory on the server:
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\DataMart" "DataMart" "c:\BackupFiles\DataMart.cab" It runs inside an agent job. It works fine.
I wanted to change it to archive to our standard backup server location. So I changed it to the following:
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\DataMart" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\ServerName\DataMart.cab". The job now fails & outputs nothing to the log file. The only thing it says when I view history on the job is : Executed as user: SqlAdmin. The step did not generate any output. Process Exit Code 1. The step failed.
At first I thought maybe AS 2000 couldn't archive over the network so I open up AS Manager & manually did an archive to the same network location. It was successfull. So that blew my theory.
I don't know why the job won't do the archive to the network location. Any ideas?
Thanks,
John
If you can manually run the command
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\DataMart" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\ServerName\DataMart.cab"
then it's possible that the SqlAdmin user doesn't have write permissions to the share.
Adrian
|||
Adrian,
I forgot to mention that SQLAdmin does have privileges to the network backup location. We use this same login for all our SQL backups as well.
I wasn't ever able to get the command to run manually. I was able to manually run the archive process through Analysis manager. Don't know if that makes a difference or not.
Any other ideas?
Thanks,
JOhn
|||Unless you have changed the default data directory, I think you have an incorrect "datamart" sub folder in your data directory parameter.
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\DataMart" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\ServerName\DataMart.cab"
try removing it and see if the command works then.
"C:\Program Files (x86)\Microsoft Analysis Services\Bin\msmdarch" /a ServerName"C:\Program Files (x86)\Microsoft Analysis Services\Data\" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\ServerName\DataMart.cab"
Also, where are you running Analysis Manager from? Judging by the (x86) in the path I would say that your AS2k server is 64bit and all the management tools (including msmdarch.exe) are 32 bit. The last recommendation I saw said to try to run these tools from a 32bit machine and not on the 64bit server. I don't know if that means it would not work, but it might be another option to explore.
|||
Darren,
I removed the extra "datamart" from the command but same result.
Sorry I didn't mention this earlier. I am running W2K3 64 bit with AS 2000 32 bit. I was running Analysis Manager on the 64 bit server when I was able to do the archive manually. WIth this command, I am running it under SQL 2005 EE 64 bit agent job.
I tried running the following command from our 32 bit test server but it had the same result:
"C:\Program Files\Microsoft Analysis Services\Bin\msmdarch" /a 64BitServer"C:\Program Files (x86)\Microsoft Analysis Services\Data\" "DataMart" "\\10.0.50.115\Disk3\servers\SQL\64BitServer\DataMart.cab"
Any other ideas?
Thanks,
John
|||Hmm, running out of ideas.
Have you tried mapping a drive so that you are backing up to z:\... or something like that?
Have you tried specifying the other 2 optional parameter (the logfile and tempfolder)? The log file might give you some ideas, although it might be blank, I seem to remember having trouble like this once, but I can't remember how I resolved it.
Finally, if all else fails there was some documentation, I think in the operations guide whitepaper, on how to "manually" back up an AS2k server by taking a file back up of the data directory and the repository database.
|||Darren,
A mapped drive seems to work. Although, I don't like using mapped drives on our servers but I may have to make an exception in this instance. Maybe I will have it archive locally & then execute a batch job that would xcopy the .cab file to the backup server.
I also tried adding the log & temp folder parameters but that did not make any difference. I still got the useless blank log file.
Thanks for the help,
JOhn
|||Hello,
Enjoyed reading the thread, I had a thought that might be helpful:
You might try enabling UNC support for your command prompt. By default, Microsoft ships this flag turned off, but I've yet to have any trouble with it turned on. YMMV.
Microsoft KB156276 instructions for doing this:
Under the registry path:
HKEY_CURRENT_USER
\Software
\Microsoft
\Command Processor
add the value DisableUNCCheck REG_DWORD and set the value to 0 x 1 (Hex).
http://support.microsoft.com/kb/156276
I hope this helps you. Good luck...!
-ed2
|||
Ed,
Thanks for the thought. I added this to the registry & then ran my job but same result. It may need to have a reboot to get the change into effect. However, the KB article lists this as a bug for Win NT 4 & states that it would be fixed in a SP. So I would hope that this has been fixed in Windows 2003 server. I will leave it until after a reboot to see if it works or not.
THe batch job is working great btw.
John
|||I'm sorry to hear this wasn't a fix... WIth only 8 months of mainstream support remaining on SQL Server 2000, it's hard to imagine this will get much attention, but you might try opening a call if you can justify the expense...
Read the KB article I sent you over again, and you'll find out that the fix is in Win2K, XP, and Win2K3. The KB article said that NT4 originally had no check for UNC pathing in the command prompt, and that caused problems for users who would launch Windows apps from the command prompt session, then close the command prompt and the pipeline to the exe file would become broken. To remedy this Microsoft changed CMD.EXE such that whenever you use a UNC path at the command line it produces an error message UNLESS you put in the registry entry from the KB article. So basically the fix was to decide that it was inappropriate to use UNC pathing at the command prompt. However, I think that once you understand the limitations (and know what not to do), the benefits gained by using the UNC pathing outweigh the risks.
In one of the earlier posts it sounded as though you might be running the job from SQL Server Agent. I've seen some odd behavior from that in some ways -- for example, I wasn't able to call an osql command from SQL Server Agent using xp_cmdshell (pointless as that might seem). So, if you haven't already done so, try the Windows Job Scheduler instead.
Best wishes,
Ed
Sunday, March 25, 2012
Archive Olap Database
Hi All,
I am using the msmdarch.exe command to backup olap
database but it's getting stuck. Any clues.
Many thanks,
Yash
Hi Yash,
http://support.microsoft.com/default...312399&sd=tech
HOW TO: Archive and Restore an Analysis Services Database from the Command Prompt in SQL Server 2000 Analysis Services
http://www.microsoft.com/technet/pro.../anservog.mspx
Microsoft SQL Server 2000 Analysis Services Operations Guide
Hope it helps...
Cheers,
Sanka
"Yash" wrote:
> Hi All,
> I am using the msmdarch.exe command to backup olap
> database but it's getting stuck. Any clues.
> Many thanks,
> Yash
>
|||Hi Sanka,
Thanks a lot. I'll go through this link.
Cheers,
Yash
>--Original Message--
>Hi Yash,
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;312399&sd=tech
>HOW TO: Archive and Restore an Analysis Services Database
from the Command Prompt in SQL Server 2000 Analysis
Services
>http://www.microsoft.com/technet/pro.../sql/2000/main
tain/anservog.mspx
>Microsoft SQL Server 2000 Analysis Services Operations
Guide
>Hope it helps...
>Cheers,
>Sanka
>
>"Yash" wrote:
>.
>
I am using the msmdarch.exe command to backup olap
database but it's getting stuck. Any clues.
Many thanks,
Yash
Hi Yash,
http://support.microsoft.com/default...312399&sd=tech
HOW TO: Archive and Restore an Analysis Services Database from the Command Prompt in SQL Server 2000 Analysis Services
http://www.microsoft.com/technet/pro.../anservog.mspx
Microsoft SQL Server 2000 Analysis Services Operations Guide
Hope it helps...
Cheers,
Sanka
"Yash" wrote:
> Hi All,
> I am using the msmdarch.exe command to backup olap
> database but it's getting stuck. Any clues.
> Many thanks,
> Yash
>
|||Hi Sanka,
Thanks a lot. I'll go through this link.
Cheers,
Yash
>--Original Message--
>Hi Yash,
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;312399&sd=tech
>HOW TO: Archive and Restore an Analysis Services Database
from the Command Prompt in SQL Server 2000 Analysis
Services
>http://www.microsoft.com/technet/pro.../sql/2000/main
tain/anservog.mspx
>Microsoft SQL Server 2000 Analysis Services Operations
Guide
>Hope it helps...
>Cheers,
>Sanka
>
>"Yash" wrote:
>.
>
Archive Olap Database
Hi All,
I am using the msmdarch.exe command to backup olap
database but it's getting stuck. Any clues.
Many thanks,
YashHi Yash,
http://support.microsoft.com/defaul...;312399&sd=tech
HOW TO: Archive and Restore an Analysis Services Database from the Command P
rompt in SQL Server 2000 Analysis Services
http://www.microsoft.com/technet/pr...n/anservog.mspx
Microsoft SQL Server 2000 Analysis Services Operations Guide
Hope it helps...
Cheers,
Sanka
"Yash" wrote:
> Hi All,
> I am using the msmdarch.exe command to backup olap
> database but it's getting stuck. Any clues.
> Many thanks,
> Yash
>|||Hi Sanka,
Thanks a lot. I'll go through this link.
Cheers,
Yash
>--Original Message--
>Hi Yash,
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;312399&sd=tech
>HOW TO: Archive and Restore an Analysis Services Database
from the Command Prompt in SQL Server 2000 Analysis
Services
>http://www.microsoft.com/technet/pr...l/sql/2000/main
tain/anservog.mspx
>Microsoft SQL Server 2000 Analysis Services Operations
Guide
>Hope it helps...
>Cheers,
>Sanka
>
>"Yash" wrote:
>
>.
>
I am using the msmdarch.exe command to backup olap
database but it's getting stuck. Any clues.
Many thanks,
YashHi Yash,
http://support.microsoft.com/defaul...;312399&sd=tech
HOW TO: Archive and Restore an Analysis Services Database from the Command P
rompt in SQL Server 2000 Analysis Services
http://www.microsoft.com/technet/pr...n/anservog.mspx
Microsoft SQL Server 2000 Analysis Services Operations Guide
Hope it helps...
Cheers,
Sanka
"Yash" wrote:
> Hi All,
> I am using the msmdarch.exe command to backup olap
> database but it's getting stuck. Any clues.
> Many thanks,
> Yash
>|||Hi Sanka,
Thanks a lot. I'll go through this link.
Cheers,
Yash
>--Original Message--
>Hi Yash,
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;312399&sd=tech
>HOW TO: Archive and Restore an Analysis Services Database
from the Command Prompt in SQL Server 2000 Analysis
Services
>http://www.microsoft.com/technet/pr...l/sql/2000/main
tain/anservog.mspx
>Microsoft SQL Server 2000 Analysis Services Operations
Guide
>Hope it helps...
>Cheers,
>Sanka
>
>"Yash" wrote:
>
>.
>
Tuesday, March 20, 2012
Applying Tran logs in SQL 2000
Hi,
I have a SQL 2k database thats around 200 GB in size. I have restored this
from a backup, but while restoring I failed to realise that I needed to apply
tran logs (didnt specify NORECOVERY) once the full backup was restored.
There are 6 tran log files to apply now.
Can I do this without once again restoring the database (with NORECOVERY)? I
am asking this because it will save a lot of time.
Thank you.
Regards,
Karthik
No, once you did RECOVERY, you can't restore any more backups, since SQL Server performed the UNDO
phase. The other way around is possible, though...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Karthik" <Karthik@.discussions.microsoft.com> wrote in message
news:DAC80787-AC08-47B8-8046-CCF6DD770639@.microsoft.com...
> Hi,
> I have a SQL 2k database thats around 200 GB in size. I have restored this
> from a backup, but while restoring I failed to realise that I needed to apply
> tran logs (didnt specify NORECOVERY) once the full backup was restored.
> There are 6 tran log files to apply now.
> Can I do this without once again restoring the database (with NORECOVERY)? I
> am asking this because it will save a lot of time.
> Thank you.
> Regards,
> Karthik
|||Hi,
You cant. You need to start the full database restore again with NORECOVERY
option.
SQL Server requires that the WITH NORECOVERY option be used on all but the
final RESTORE statement when restoring a database
backup and multiple transaction logs. NORECOVERY Instructs the restore
operation to not roll back any uncommitted transactions
Thanks
Hari
"Karthik" <Karthik@.discussions.microsoft.com> wrote in message
news:DAC80787-AC08-47B8-8046-CCF6DD770639@.microsoft.com...
> Hi,
> I have a SQL 2k database thats around 200 GB in size. I have restored this
> from a backup, but while restoring I failed to realise that I needed to
> apply
> tran logs (didnt specify NORECOVERY) once the full backup was restored.
> There are 6 tran log files to apply now.
> Can I do this without once again restoring the database (with NORECOVERY)?
> I
> am asking this because it will save a lot of time.
> Thank you.
> Regards,
> Karthik
I have a SQL 2k database thats around 200 GB in size. I have restored this
from a backup, but while restoring I failed to realise that I needed to apply
tran logs (didnt specify NORECOVERY) once the full backup was restored.
There are 6 tran log files to apply now.
Can I do this without once again restoring the database (with NORECOVERY)? I
am asking this because it will save a lot of time.
Thank you.
Regards,
Karthik
No, once you did RECOVERY, you can't restore any more backups, since SQL Server performed the UNDO
phase. The other way around is possible, though...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Karthik" <Karthik@.discussions.microsoft.com> wrote in message
news:DAC80787-AC08-47B8-8046-CCF6DD770639@.microsoft.com...
> Hi,
> I have a SQL 2k database thats around 200 GB in size. I have restored this
> from a backup, but while restoring I failed to realise that I needed to apply
> tran logs (didnt specify NORECOVERY) once the full backup was restored.
> There are 6 tran log files to apply now.
> Can I do this without once again restoring the database (with NORECOVERY)? I
> am asking this because it will save a lot of time.
> Thank you.
> Regards,
> Karthik
|||Hi,
You cant. You need to start the full database restore again with NORECOVERY
option.
SQL Server requires that the WITH NORECOVERY option be used on all but the
final RESTORE statement when restoring a database
backup and multiple transaction logs. NORECOVERY Instructs the restore
operation to not roll back any uncommitted transactions
Thanks
Hari
"Karthik" <Karthik@.discussions.microsoft.com> wrote in message
news:DAC80787-AC08-47B8-8046-CCF6DD770639@.microsoft.com...
> Hi,
> I have a SQL 2k database thats around 200 GB in size. I have restored this
> from a backup, but while restoring I failed to realise that I needed to
> apply
> tran logs (didnt specify NORECOVERY) once the full backup was restored.
> There are 6 tran log files to apply now.
> Can I do this without once again restoring the database (with NORECOVERY)?
> I
> am asking this because it will save a lot of time.
> Thank you.
> Regards,
> Karthik
Applying Tran logs in SQL 2000
Hi,
I have a SQL 2k database thats around 200 GB in size. I have restored this
from a backup, but while restoring I failed to realise that I needed to appl
y
tran logs (didnt specify NORECOVERY) once the full backup was restored.
There are 6 tran log files to apply now.
Can I do this without once again restoring the database (with NORECOVERY)? I
am asking this because it will save a lot of time.
Thank you.
Regards,
KarthikNo, once you did RECOVERY, you can't restore any more backups, since SQL Ser
ver performed the UNDO
phase. The other way around is possible, though...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Karthik" <Karthik@.discussions.microsoft.com> wrote in message
news:DAC80787-AC08-47B8-8046-CCF6DD770639@.microsoft.com...
> Hi,
> I have a SQL 2k database thats around 200 GB in size. I have restored this
> from a backup, but while restoring I failed to realise that I needed to ap
ply
> tran logs (didnt specify NORECOVERY) once the full backup was restored.
> There are 6 tran log files to apply now.
> Can I do this without once again restoring the database (with NORECOVERY)?
I
> am asking this because it will save a lot of time.
> Thank you.
> Regards,
> Karthik|||Hi,
You cant. You need to start the full database restore again with NORECOVERY
option.
SQL Server requires that the WITH NORECOVERY option be used on all but the
final RESTORE statement when restoring a database
backup and multiple transaction logs. NORECOVERY Instructs the restore
operation to not roll back any uncommitted transactions
Thanks
Hari
"Karthik" <Karthik@.discussions.microsoft.com> wrote in message
news:DAC80787-AC08-47B8-8046-CCF6DD770639@.microsoft.com...
> Hi,
> I have a SQL 2k database thats around 200 GB in size. I have restored this
> from a backup, but while restoring I failed to realise that I needed to
> apply
> tran logs (didnt specify NORECOVERY) once the full backup was restored.
> There are 6 tran log files to apply now.
> Can I do this without once again restoring the database (with NORECOVERY)?
> I
> am asking this because it will save a lot of time.
> Thank you.
> Regards,
> Karthik
I have a SQL 2k database thats around 200 GB in size. I have restored this
from a backup, but while restoring I failed to realise that I needed to appl
y
tran logs (didnt specify NORECOVERY) once the full backup was restored.
There are 6 tran log files to apply now.
Can I do this without once again restoring the database (with NORECOVERY)? I
am asking this because it will save a lot of time.
Thank you.
Regards,
KarthikNo, once you did RECOVERY, you can't restore any more backups, since SQL Ser
ver performed the UNDO
phase. The other way around is possible, though...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Karthik" <Karthik@.discussions.microsoft.com> wrote in message
news:DAC80787-AC08-47B8-8046-CCF6DD770639@.microsoft.com...
> Hi,
> I have a SQL 2k database thats around 200 GB in size. I have restored this
> from a backup, but while restoring I failed to realise that I needed to ap
ply
> tran logs (didnt specify NORECOVERY) once the full backup was restored.
> There are 6 tran log files to apply now.
> Can I do this without once again restoring the database (with NORECOVERY)?
I
> am asking this because it will save a lot of time.
> Thank you.
> Regards,
> Karthik|||Hi,
You cant. You need to start the full database restore again with NORECOVERY
option.
SQL Server requires that the WITH NORECOVERY option be used on all but the
final RESTORE statement when restoring a database
backup and multiple transaction logs. NORECOVERY Instructs the restore
operation to not roll back any uncommitted transactions
Thanks
Hari
"Karthik" <Karthik@.discussions.microsoft.com> wrote in message
news:DAC80787-AC08-47B8-8046-CCF6DD770639@.microsoft.com...
> Hi,
> I have a SQL 2k database thats around 200 GB in size. I have restored this
> from a backup, but while restoring I failed to realise that I needed to
> apply
> tran logs (didnt specify NORECOVERY) once the full backup was restored.
> There are 6 tran log files to apply now.
> Can I do this without once again restoring the database (with NORECOVERY)?
> I
> am asking this because it will save a lot of time.
> Thank you.
> Regards,
> Karthik
Applying Tran logs in SQL 2000
Hi,
I have a SQL 2k database thats around 200 GB in size. I have restored this
from a backup, but while restoring I failed to realise that I needed to apply
tran logs (didnt specify NORECOVERY) once the full backup was restored.
There are 6 tran log files to apply now.
Can I do this without once again restoring the database (with NORECOVERY)? I
am asking this because it will save a lot of time.
Thank you.
Regards,
KarthikNo, once you did RECOVERY, you can't restore any more backups, since SQL Server performed the UNDO
phase. The other way around is possible, though...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Karthik" <Karthik@.discussions.microsoft.com> wrote in message
news:DAC80787-AC08-47B8-8046-CCF6DD770639@.microsoft.com...
> Hi,
> I have a SQL 2k database thats around 200 GB in size. I have restored this
> from a backup, but while restoring I failed to realise that I needed to apply
> tran logs (didnt specify NORECOVERY) once the full backup was restored.
> There are 6 tran log files to apply now.
> Can I do this without once again restoring the database (with NORECOVERY)? I
> am asking this because it will save a lot of time.
> Thank you.
> Regards,
> Karthik|||Hi,
You cant. You need to start the full database restore again with NORECOVERY
option.
SQL Server requires that the WITH NORECOVERY option be used on all but the
final RESTORE statement when restoring a database
backup and multiple transaction logs. NORECOVERY Instructs the restore
operation to not roll back any uncommitted transactions
Thanks
Hari
"Karthik" <Karthik@.discussions.microsoft.com> wrote in message
news:DAC80787-AC08-47B8-8046-CCF6DD770639@.microsoft.com...
> Hi,
> I have a SQL 2k database thats around 200 GB in size. I have restored this
> from a backup, but while restoring I failed to realise that I needed to
> apply
> tran logs (didnt specify NORECOVERY) once the full backup was restored.
> There are 6 tran log files to apply now.
> Can I do this without once again restoring the database (with NORECOVERY)?
> I
> am asking this because it will save a lot of time.
> Thank you.
> Regards,
> Karthik
I have a SQL 2k database thats around 200 GB in size. I have restored this
from a backup, but while restoring I failed to realise that I needed to apply
tran logs (didnt specify NORECOVERY) once the full backup was restored.
There are 6 tran log files to apply now.
Can I do this without once again restoring the database (with NORECOVERY)? I
am asking this because it will save a lot of time.
Thank you.
Regards,
KarthikNo, once you did RECOVERY, you can't restore any more backups, since SQL Server performed the UNDO
phase. The other way around is possible, though...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Karthik" <Karthik@.discussions.microsoft.com> wrote in message
news:DAC80787-AC08-47B8-8046-CCF6DD770639@.microsoft.com...
> Hi,
> I have a SQL 2k database thats around 200 GB in size. I have restored this
> from a backup, but while restoring I failed to realise that I needed to apply
> tran logs (didnt specify NORECOVERY) once the full backup was restored.
> There are 6 tran log files to apply now.
> Can I do this without once again restoring the database (with NORECOVERY)? I
> am asking this because it will save a lot of time.
> Thank you.
> Regards,
> Karthik|||Hi,
You cant. You need to start the full database restore again with NORECOVERY
option.
SQL Server requires that the WITH NORECOVERY option be used on all but the
final RESTORE statement when restoring a database
backup and multiple transaction logs. NORECOVERY Instructs the restore
operation to not roll back any uncommitted transactions
Thanks
Hari
"Karthik" <Karthik@.discussions.microsoft.com> wrote in message
news:DAC80787-AC08-47B8-8046-CCF6DD770639@.microsoft.com...
> Hi,
> I have a SQL 2k database thats around 200 GB in size. I have restored this
> from a backup, but while restoring I failed to realise that I needed to
> apply
> tran logs (didnt specify NORECOVERY) once the full backup was restored.
> There are 6 tran log files to apply now.
> Can I do this without once again restoring the database (with NORECOVERY)?
> I
> am asking this because it will save a lot of time.
> Thank you.
> Regards,
> Karthik
Sunday, March 11, 2012
Apply Log File Transactions
I lost my mdf because of a failure on the RAID. The log
file was on another disk and it is apparently good thru
this morning. My last complete backup was last Friday
morning. I made two copies of the good log file and
restored the database using the option to restore more
log files. I would like to apply the log file I saved to
this database but the restore process needs a file
created by backup. I cannot figure out how to back up the
saved log file using a file name. How can I do this?
BACKUP LOG XXX FILE = ? TO DISK
= 'D:\MSSQL\BACKUP\SAFE.BKP'
Hi
Perform BACKUP LOG databasename WITH NO_TRUNCATE (For more details please
refer to BOL)
"pbrattin" <pbrattin@.removethis-bigfoot.com> wrote in message
news:181501c426d5$a693f360$a101280a@.phx.gbl...
> I lost my mdf because of a failure on the RAID. The log
> file was on another disk and it is apparently good thru
> this morning. My last complete backup was last Friday
> morning. I made two copies of the good log file and
> restored the database using the option to restore more
> log files. I would like to apply the log file I saved to
> this database but the restore process needs a file
> created by backup. I cannot figure out how to back up the
> saved log file using a file name. How can I do this?
> BACKUP LOG XXX FILE = ? TO DISK
> = 'D:\MSSQL\BACKUP\SAFE.BKP'
>
>
file was on another disk and it is apparently good thru
this morning. My last complete backup was last Friday
morning. I made two copies of the good log file and
restored the database using the option to restore more
log files. I would like to apply the log file I saved to
this database but the restore process needs a file
created by backup. I cannot figure out how to back up the
saved log file using a file name. How can I do this?
BACKUP LOG XXX FILE = ? TO DISK
= 'D:\MSSQL\BACKUP\SAFE.BKP'
Hi
Perform BACKUP LOG databasename WITH NO_TRUNCATE (For more details please
refer to BOL)
"pbrattin" <pbrattin@.removethis-bigfoot.com> wrote in message
news:181501c426d5$a693f360$a101280a@.phx.gbl...
> I lost my mdf because of a failure on the RAID. The log
> file was on another disk and it is apparently good thru
> this morning. My last complete backup was last Friday
> morning. I made two copies of the good log file and
> restored the database using the option to restore more
> log files. I would like to apply the log file I saved to
> this database but the restore process needs a file
> created by backup. I cannot figure out how to back up the
> saved log file using a file name. How can I do this?
> BACKUP LOG XXX FILE = ? TO DISK
> = 'D:\MSSQL\BACKUP\SAFE.BKP'
>
>
Apply Log File Transactions
I lost my mdf because of a failure on the RAID. The log
file was on another disk and it is apparently good thru
this morning. My last complete backup was last Friday
morning. I made two copies of the good log file and
restored the database using the option to restore more
log files. I would like to apply the log file I saved to
this database but the restore process needs a file
created by backup. I cannot figure out how to back up the
saved log file using a file name. How can I do this?
BACKUP LOG XXX FILE = ' TO DISK
= 'D:\MSSQL\BACKUP\SAFE.BKP'Hi
Perform BACKUP LOG databasename WITH NO_TRUNCATE (For more details please
refer to BOL)
"pbrattin" <pbrattin@.removethis-bigfoot.com> wrote in message
news:181501c426d5$a693f360$a101280a@.phx.gbl...
> I lost my mdf because of a failure on the RAID. The log
> file was on another disk and it is apparently good thru
> this morning. My last complete backup was last Friday
> morning. I made two copies of the good log file and
> restored the database using the option to restore more
> log files. I would like to apply the log file I saved to
> this database but the restore process needs a file
> created by backup. I cannot figure out how to back up the
> saved log file using a file name. How can I do this?
> BACKUP LOG XXX FILE = ' TO DISK
> = 'D:\MSSQL\BACKUP\SAFE.BKP'
>
>
file was on another disk and it is apparently good thru
this morning. My last complete backup was last Friday
morning. I made two copies of the good log file and
restored the database using the option to restore more
log files. I would like to apply the log file I saved to
this database but the restore process needs a file
created by backup. I cannot figure out how to back up the
saved log file using a file name. How can I do this?
BACKUP LOG XXX FILE = ' TO DISK
= 'D:\MSSQL\BACKUP\SAFE.BKP'Hi
Perform BACKUP LOG databasename WITH NO_TRUNCATE (For more details please
refer to BOL)
"pbrattin" <pbrattin@.removethis-bigfoot.com> wrote in message
news:181501c426d5$a693f360$a101280a@.phx.gbl...
> I lost my mdf because of a failure on the RAID. The log
> file was on another disk and it is apparently good thru
> this morning. My last complete backup was last Friday
> morning. I made two copies of the good log file and
> restored the database using the option to restore more
> log files. I would like to apply the log file I saved to
> this database but the restore process needs a file
> created by backup. I cannot figure out how to back up the
> saved log file using a file name. How can I do this?
> BACKUP LOG XXX FILE = ' TO DISK
> = 'D:\MSSQL\BACKUP\SAFE.BKP'
>
>
Apply Log File Transactions
I lost my mdf because of a failure on the RAID. The log
file was on another disk and it is apparently good thru
this morning. My last complete backup was last Friday
morning. I made two copies of the good log file and
restored the database using the option to restore more
log files. I would like to apply the log file I saved to
this database but the restore process needs a file
created by backup. I cannot figure out how to back up the
saved log file using a file name. How can I do this?
BACKUP LOG XXX FILE = ' TO DISK
= 'D:\MSSQL\BACKUP\SAFE.BKP'Hi
Perform BACKUP LOG databasename WITH NO_TRUNCATE (For more details please
refer to BOL)
"pbrattin" <pbrattin@.removethis-bigfoot.com> wrote in message
news:181501c426d5$a693f360$a101280a@.phx.gbl...
> I lost my mdf because of a failure on the RAID. The log
> file was on another disk and it is apparently good thru
> this morning. My last complete backup was last Friday
> morning. I made two copies of the good log file and
> restored the database using the option to restore more
> log files. I would like to apply the log file I saved to
> this database but the restore process needs a file
> created by backup. I cannot figure out how to back up the
> saved log file using a file name. How can I do this?
> BACKUP LOG XXX FILE = ' TO DISK
> = 'D:\MSSQL\BACKUP\SAFE.BKP'
>
>
file was on another disk and it is apparently good thru
this morning. My last complete backup was last Friday
morning. I made two copies of the good log file and
restored the database using the option to restore more
log files. I would like to apply the log file I saved to
this database but the restore process needs a file
created by backup. I cannot figure out how to back up the
saved log file using a file name. How can I do this?
BACKUP LOG XXX FILE = ' TO DISK
= 'D:\MSSQL\BACKUP\SAFE.BKP'Hi
Perform BACKUP LOG databasename WITH NO_TRUNCATE (For more details please
refer to BOL)
"pbrattin" <pbrattin@.removethis-bigfoot.com> wrote in message
news:181501c426d5$a693f360$a101280a@.phx.gbl...
> I lost my mdf because of a failure on the RAID. The log
> file was on another disk and it is apparently good thru
> this morning. My last complete backup was last Friday
> morning. I made two copies of the good log file and
> restored the database using the option to restore more
> log files. I would like to apply the log file I saved to
> this database but the restore process needs a file
> created by backup. I cannot figure out how to back up the
> saved log file using a file name. How can I do this?
> BACKUP LOG XXX FILE = ' TO DISK
> = 'D:\MSSQL\BACKUP\SAFE.BKP'
>
>
Apply compression - XMLA
Hi there,
I intend to create a backup job for my cube, however I didn't find anywhere the XMLA configuration command for the "Apply Compression" option in the cube backup properties. Even if I check this box and script the setting it doesn't show up. I haven't find anything even in the XMLA command reference .
<Backup xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Object>
<DatabaseID>test</DatabaseID>
</Object>
<File>test.abf</File>
<AllowOverwrite>true</AllowOverwrite>
</Backup>
Any help would be appreciated!
Thanks,
Greg
There is an ApplyCompression element, which is in the latest BOL. You do not see this element when you turn compression on as the default value is on, you only see it when you turn compression off.
Code Snippet
<Backup xmlns=http://schemas.microsoft.com/analysisservices/2003/engine>
<Object>
<DatabaseID>Adventure Works DW</DatabaseID>
</Object>
<File>Adventure Works DW.abf</File>
<ApplyCompression>false</ApplyCompression>
</Backup>
Saturday, February 25, 2012
Application log and backuo operations
I'm using Log Shipping in order to update a backup database on SQL Server
2000. I scheduled the transaction log backup every 5 minutes. The problem is
that SQL Server logs an event into the Application Log every time backup is
completed so the Application Log becomes full very quickly.
Is there any way to disable this behaviour ?
Thank you for any suggestions.
Luigi
Hi,
In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
task. Double click above that and
select "Notifications"
In that screen "UNCHECK" the Write to windows Application log and clieck
Apply and OK.
Thanks
Hari
MCDBA
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> I'm using Log Shipping in order to update a backup database on SQL Server
> 2000. I scheduled the transaction log backup every 5 minutes. The problem
is
> that SQL Server logs an event into the Application Log every time backup
is
> completed so the Application Log becomes full very quickly.
> Is there any way to disable this behaviour ?
> Thank you for any suggestions.
> Luigi
|||Thank you Hari for your suggestion.
I tried it but it doesn't solve my problem. The problem isn't about the
job's result : the job is set up in order to write to tha application log in
case of error only. It seems instead that it is the BACKUP command that logs
the event: when I launch my job, I find in the application log the same log
that I find when I backup database by Enterprise Maganer's facilities.
Bye
Luigi
"Hari Prasad" wrote:
> Hi,
> In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
> task. Double click above that and
> select "Notifications"
> In that screen "UNCHECK" the Write to windows Application log and clieck
> Apply and OK.
> Thanks
> Hari
> MCDBA
>
> "Luigi" <Luigi@.discussions.microsoft.com> wrote in message
> news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> is
> is
>
>
|||SQL Server always write these messages to your logs. Even if you define in sysmessages that they shouldn't be
written. I have suggested to MS that SQL Server honors the setting in sysmessages, we'll see if any such
change appears in the future. If you want to communicate such a wish, you can use sqlwish@.microsoft.com.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:07C296BE-FD47-46D1-94A6-669FD6FB9C67@.microsoft.com...[vbcol=seagreen]
> Thank you Hari for your suggestion.
> I tried it but it doesn't solve my problem. The problem isn't about the
> job's result : the job is set up in order to write to tha application log in
> case of error only. It seems instead that it is the BACKUP command that logs
> the event: when I launch my job, I find in the application log the same log
> that I find when I backup database by Enterprise Maganer's facilities.
> Bye
> Luigi
>
> "Hari Prasad" wrote:
2000. I scheduled the transaction log backup every 5 minutes. The problem is
that SQL Server logs an event into the Application Log every time backup is
completed so the Application Log becomes full very quickly.
Is there any way to disable this behaviour ?
Thank you for any suggestions.
Luigi
Hi,
In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
task. Double click above that and
select "Notifications"
In that screen "UNCHECK" the Write to windows Application log and clieck
Apply and OK.
Thanks
Hari
MCDBA
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> I'm using Log Shipping in order to update a backup database on SQL Server
> 2000. I scheduled the transaction log backup every 5 minutes. The problem
is
> that SQL Server logs an event into the Application Log every time backup
is
> completed so the Application Log becomes full very quickly.
> Is there any way to disable this behaviour ?
> Thank you for any suggestions.
> Luigi
|||Thank you Hari for your suggestion.
I tried it but it doesn't solve my problem. The problem isn't about the
job's result : the job is set up in order to write to tha application log in
case of error only. It seems instead that it is the BACKUP command that logs
the event: when I launch my job, I find in the application log the same log
that I find when I backup database by Enterprise Maganer's facilities.
Bye
Luigi
"Hari Prasad" wrote:
> Hi,
> In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
> task. Double click above that and
> select "Notifications"
> In that screen "UNCHECK" the Write to windows Application log and clieck
> Apply and OK.
> Thanks
> Hari
> MCDBA
>
> "Luigi" <Luigi@.discussions.microsoft.com> wrote in message
> news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> is
> is
>
>
|||SQL Server always write these messages to your logs. Even if you define in sysmessages that they shouldn't be
written. I have suggested to MS that SQL Server honors the setting in sysmessages, we'll see if any such
change appears in the future. If you want to communicate such a wish, you can use sqlwish@.microsoft.com.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:07C296BE-FD47-46D1-94A6-669FD6FB9C67@.microsoft.com...[vbcol=seagreen]
> Thank you Hari for your suggestion.
> I tried it but it doesn't solve my problem. The problem isn't about the
> job's result : the job is set up in order to write to tha application log in
> case of error only. It seems instead that it is the BACKUP command that logs
> the event: when I launch my job, I find in the application log the same log
> that I find when I backup database by Enterprise Maganer's facilities.
> Bye
> Luigi
>
> "Hari Prasad" wrote:
Application log and backuo operations
I'm using Log Shipping in order to update a backup database on SQL Server
2000. I scheduled the transaction log backup every 5 minutes. The problem is
that SQL Server logs an event into the Application Log every time backup is
completed so the Application Log becomes full very quickly.
Is there any way to disable this behaviour '
Thank you for any suggestions.
LuigiHi,
In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
task. Double click above that and
select "Notifications"
In that screen "UNCHECK" the Write to windows Application log and clieck
Apply and OK.
Thanks
Hari
MCDBA
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> I'm using Log Shipping in order to update a backup database on SQL Server
> 2000. I scheduled the transaction log backup every 5 minutes. The problem
is
> that SQL Server logs an event into the Application Log every time backup
is
> completed so the Application Log becomes full very quickly.
> Is there any way to disable this behaviour '
> Thank you for any suggestions.
> Luigi|||SQL Server always write these messages to your logs. Even if you define in sysmessages that they shouldn't be
written. I have suggested to MS that SQL Server honors the setting in sysmessages, we'll see if any such
change appears in the future. If you want to communicate such a wish, you can use sqlwish@.microsoft.com.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:07C296BE-FD47-46D1-94A6-669FD6FB9C67@.microsoft.com...
> Thank you Hari for your suggestion.
> I tried it but it doesn't solve my problem. The problem isn't about the
> job's result : the job is set up in order to write to tha application log in
> case of error only. It seems instead that it is the BACKUP command that logs
> the event: when I launch my job, I find in the application log the same log
> that I find when I backup database by Enterprise Maganer's facilities.
> Bye
> Luigi
>
> "Hari Prasad" wrote:
> > Hi,
> >
> > In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
> > task. Double click above that and
> > select "Notifications"
> >
> > In that screen "UNCHECK" the Write to windows Application log and clieck
> > Apply and OK.
> >
> > Thanks
> > Hari
> > MCDBA
> >
> >
> >
> > "Luigi" <Luigi@.discussions.microsoft.com> wrote in message
> > news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> > > I'm using Log Shipping in order to update a backup database on SQL Server
> > > 2000. I scheduled the transaction log backup every 5 minutes. The problem
> > is
> > > that SQL Server logs an event into the Application Log every time backup
> > is
> > > completed so the Application Log becomes full very quickly.
> > >
> > > Is there any way to disable this behaviour '
> > >
> > > Thank you for any suggestions.
> > >
> > > Luigi
> >
> >
> >
2000. I scheduled the transaction log backup every 5 minutes. The problem is
that SQL Server logs an event into the Application Log every time backup is
completed so the Application Log becomes full very quickly.
Is there any way to disable this behaviour '
Thank you for any suggestions.
LuigiHi,
In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
task. Double click above that and
select "Notifications"
In that screen "UNCHECK" the Write to windows Application log and clieck
Apply and OK.
Thanks
Hari
MCDBA
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> I'm using Log Shipping in order to update a backup database on SQL Server
> 2000. I scheduled the transaction log backup every 5 minutes. The problem
is
> that SQL Server logs an event into the Application Log every time backup
is
> completed so the Application Log becomes full very quickly.
> Is there any way to disable this behaviour '
> Thank you for any suggestions.
> Luigi|||SQL Server always write these messages to your logs. Even if you define in sysmessages that they shouldn't be
written. I have suggested to MS that SQL Server honors the setting in sysmessages, we'll see if any such
change appears in the future. If you want to communicate such a wish, you can use sqlwish@.microsoft.com.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:07C296BE-FD47-46D1-94A6-669FD6FB9C67@.microsoft.com...
> Thank you Hari for your suggestion.
> I tried it but it doesn't solve my problem. The problem isn't about the
> job's result : the job is set up in order to write to tha application log in
> case of error only. It seems instead that it is the BACKUP command that logs
> the event: when I launch my job, I find in the application log the same log
> that I find when I backup database by Enterprise Maganer's facilities.
> Bye
> Luigi
>
> "Hari Prasad" wrote:
> > Hi,
> >
> > In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
> > task. Double click above that and
> > select "Notifications"
> >
> > In that screen "UNCHECK" the Write to windows Application log and clieck
> > Apply and OK.
> >
> > Thanks
> > Hari
> > MCDBA
> >
> >
> >
> > "Luigi" <Luigi@.discussions.microsoft.com> wrote in message
> > news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> > > I'm using Log Shipping in order to update a backup database on SQL Server
> > > 2000. I scheduled the transaction log backup every 5 minutes. The problem
> > is
> > > that SQL Server logs an event into the Application Log every time backup
> > is
> > > completed so the Application Log becomes full very quickly.
> > >
> > > Is there any way to disable this behaviour '
> > >
> > > Thank you for any suggestions.
> > >
> > > Luigi
> >
> >
> >
Application log and backuo operations
I'm using Log Shipping in order to update a backup database on SQL Server
2000. I scheduled the transaction log backup every 5 minutes. The problem is
that SQL Server logs an event into the Application Log every time backup is
completed so the Application Log becomes full very quickly.
Is there any way to disable this behaviour '
Thank you for any suggestions.
LuigiHi,
In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
task. Double click above that and
select "Notifications"
In that screen "UNCHECK" the Write to windows Application log and clieck
Apply and OK.
Thanks
Hari
MCDBA
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> I'm using Log Shipping in order to update a backup database on SQL Server
> 2000. I scheduled the transaction log backup every 5 minutes. The problem
is
> that SQL Server logs an event into the Application Log every time backup
is
> completed so the Application Log becomes full very quickly.
> Is there any way to disable this behaviour '
> Thank you for any suggestions.
> Luigi|||Thank you Hari for your suggestion.
I tried it but it doesn't solve my problem. The problem isn't about the
job's result : the job is set up in order to write to tha application log in
case of error only. It seems instead that it is the BACKUP command that logs
the event: when I launch my job, I find in the application log the same log
that I find when I backup database by Enterprise Maganer's facilities.
Bye
Luigi
"Hari Prasad" wrote:
> Hi,
> In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshippin
g
> task. Double click above that and
> select "Notifications"
> In that screen "UNCHECK" the Write to windows Application log and clieck
> Apply and OK.
> Thanks
> Hari
> MCDBA
>
> "Luigi" <Luigi@.discussions.microsoft.com> wrote in message
> news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> is
> is
>
>|||SQL Server always write these messages to your logs. Even if you define in s
ysmessages that they shouldn't be
written. I have suggested to MS that SQL Server honors the setting in sysmes
sages, we'll see if any such
change appears in the future. If you want to communicate such a wish, you ca
n use sqlwish@.microsoft.com.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:07C296BE-FD47-46D1-94A6-669FD6FB9C67@.microsoft.com...[vbcol=seagreen]
> Thank you Hari for your suggestion.
> I tried it but it doesn't solve my problem. The problem isn't about the
> job's result : the job is set up in order to write to tha application log
in
> case of error only. It seems instead that it is the BACKUP command that lo
gs
> the event: when I launch my job, I find in the application log the same lo
g
> that I find when I backup database by Enterprise Maganer's facilities.
> Bye
> Luigi
>
> "Hari Prasad" wrote:
>
2000. I scheduled the transaction log backup every 5 minutes. The problem is
that SQL Server logs an event into the Application Log every time backup is
completed so the Application Log becomes full very quickly.
Is there any way to disable this behaviour '
Thank you for any suggestions.
LuigiHi,
In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshipping
task. Double click above that and
select "Notifications"
In that screen "UNCHECK" the Write to windows Application log and clieck
Apply and OK.
Thanks
Hari
MCDBA
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> I'm using Log Shipping in order to update a backup database on SQL Server
> 2000. I scheduled the transaction log backup every 5 minutes. The problem
is
> that SQL Server logs an event into the Application Log every time backup
is
> completed so the Application Log becomes full very quickly.
> Is there any way to disable this behaviour '
> Thank you for any suggestions.
> Luigi|||Thank you Hari for your suggestion.
I tried it but it doesn't solve my problem. The problem isn't about the
job's result : the job is set up in order to write to tha application log in
case of error only. It seems instead that it is the BACKUP command that logs
the event: when I launch my job, I find in the application log the same log
that I find when I backup database by Enterprise Maganer's facilities.
Bye
Luigi
"Hari Prasad" wrote:
> Hi,
> In Enterprise manager -- SQL Server Agent -- Jobs -- Select the Logshippin
g
> task. Double click above that and
> select "Notifications"
> In that screen "UNCHECK" the Write to windows Application log and clieck
> Apply and OK.
> Thanks
> Hari
> MCDBA
>
> "Luigi" <Luigi@.discussions.microsoft.com> wrote in message
> news:3ACE4093-DD77-454C-B59C-A0369417D49D@.microsoft.com...
> is
> is
>
>|||SQL Server always write these messages to your logs. Even if you define in s
ysmessages that they shouldn't be
written. I have suggested to MS that SQL Server honors the setting in sysmes
sages, we'll see if any such
change appears in the future. If you want to communicate such a wish, you ca
n use sqlwish@.microsoft.com.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Luigi" <Luigi@.discussions.microsoft.com> wrote in message
news:07C296BE-FD47-46D1-94A6-669FD6FB9C67@.microsoft.com...[vbcol=seagreen]
> Thank you Hari for your suggestion.
> I tried it but it doesn't solve my problem. The problem isn't about the
> job's result : the job is set up in order to write to tha application log
in
> case of error only. It seems instead that it is the BACKUP command that lo
gs
> the event: when I launch my job, I find in the application log the same lo
g
> that I find when I backup database by Enterprise Maganer's facilities.
> Bye
> Luigi
>
> "Hari Prasad" wrote:
>
Sunday, February 19, 2012
Appending Backedup data During Restore Process
Dear All,
Can i append new database backup to the existing data, while restoring the backedup database? If so give me the solution. I had backups for 30 days backup and trying to restore all these bckups..
During the restore process, i had observed that the previsous data is getting deleted and new data is replaced on it (in the database). But i want to append the new data to the existing data.
Note : The backup format that i had taken for all these 30 days is of Full Backup (not differential backup)
Any solution(s) for the above stated...
Regards,Not possible using FULL BACKUP, you can use TLOG Backups to restore them on this server.
Can i append new database backup to the existing data, while restoring the backedup database? If so give me the solution. I had backups for 30 days backup and trying to restore all these bckups..
During the restore process, i had observed that the previsous data is getting deleted and new data is replaced on it (in the database). But i want to append the new data to the existing data.
Note : The backup format that i had taken for all these 30 days is of Full Backup (not differential backup)
Any solution(s) for the above stated...
Regards,Not possible using FULL BACKUP, you can use TLOG Backups to restore them on this server.
Subscribe to:
Posts (Atom)