Showing posts with label primary. Show all posts
Showing posts with label primary. Show all posts

Thursday, February 16, 2012

backup log in sqlserver 2000

Hi
I want to activate my standby database.
My primary database is fine and I want to continue to use it for some other
purpose.
My question :
Do I need to use no_truncate option during the remaining transactions backup
?
If I use NO_TRUNCATE option can I continue to use my primary database for
other work.
What is the difference between the regular T-LOG bkup and backup with
NO_TRUNCATE option.
Tks
MangeshNo, you shouldn't use NO_TRUNCATE. This is only there to support backing up
log of a corrupted
database. See http://www.karaszi.com/SQLServer/in...no_truncate.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in me
ssage
news:49D98498-C81E-4B7C-B117-F8E5AB7B7E3B@.microsoft.com...
> Hi
> I want to activate my standby database.
> My primary database is fine and I want to continue to use it for some othe
r
> purpose.
> My question :
> Do I need to use no_truncate option during the remaining transactions back
up?
> If I use NO_TRUNCATE option can I continue to use my primary database for
> other work.
> What is the difference between the regular T-LOG bkup and backup with
> NO_TRUNCATE option.
> Tks
> Mangesh|||Hi,
Backup Log command is used to backup the transaction log when database is
accessible. NO_TRUNCATE option is used when a database is inaccessi le and
you need to take a log backup. See the detailed explanation by tibor:-
http://www.karaszi.com/SQLServer/in...no_truncate.asp
Thanks
Hari
SQL server MVP
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:49D98498-C81E-4B7C-B117-F8E5AB7B7E3B@.microsoft.com...
> Hi
> I want to activate my standby database.
> My primary database is fine and I want to continue to use it for some
> other
> purpose.
> My question :
> Do I need to use no_truncate option during the remaining transactions
> backup?
> If I use NO_TRUNCATE option can I continue to use my primary database for
> other work.
> What is the difference between the regular T-LOG bkup and backup with
> NO_TRUNCATE option.
> Tks
> Mangesh

backup log in sqlserver 2000

Hi
I want to activate my standby database.
My primary database is fine and I want to continue to use it for some other
purpose.
My question :
Do I need to use no_truncate option during the remaining transactions backup?
If I use NO_TRUNCATE option can I continue to use my primary database for
other work.
What is the difference between the regular T-LOG bkup and backup with
NO_TRUNCATE option.
Tks
Mangesh
No, you shouldn't use NO_TRUNCATE. This is only there to support backing up log of a corrupted
database. See http://www.karaszi.com/SQLServer/inf...o_truncate.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
news:49D98498-C81E-4B7C-B117-F8E5AB7B7E3B@.microsoft.com...
> Hi
> I want to activate my standby database.
> My primary database is fine and I want to continue to use it for some other
> purpose.
> My question :
> Do I need to use no_truncate option during the remaining transactions backup?
> If I use NO_TRUNCATE option can I continue to use my primary database for
> other work.
> What is the difference between the regular T-LOG bkup and backup with
> NO_TRUNCATE option.
> Tks
> Mangesh
|||Hi,
Backup Log command is used to backup the transaction log when database is
accessible. NO_TRUNCATE option is used when a database is inaccessi le and
you need to take a log backup. See the detailed explanation by tibor:-
http://www.karaszi.com/SQLServer/inf...o_truncate.asp
Thanks
Hari
SQL server MVP
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:49D98498-C81E-4B7C-B117-F8E5AB7B7E3B@.microsoft.com...
> Hi
> I want to activate my standby database.
> My primary database is fine and I want to continue to use it for some
> other
> purpose.
> My question :
> Do I need to use no_truncate option during the remaining transactions
> backup?
> If I use NO_TRUNCATE option can I continue to use my primary database for
> other work.
> What is the difference between the regular T-LOG bkup and backup with
> NO_TRUNCATE option.
> Tks
> Mangesh

backup log in sqlserver 2000

Hi
I want to activate my standby database.
My primary database is fine and I want to continue to use it for some other
purpose.
My question :
Do I need to use no_truncate option during the remaining transactions backup?
If I use NO_TRUNCATE option can I continue to use my primary database for
other work.
What is the difference between the regular T-LOG bkup and backup with
NO_TRUNCATE option.
Tks
MangeshNo, you shouldn't use NO_TRUNCATE. This is only there to support backing up log of a corrupted
database. See http://www.karaszi.com/SQLServer/info_restore_no_truncate.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in message
news:49D98498-C81E-4B7C-B117-F8E5AB7B7E3B@.microsoft.com...
> Hi
> I want to activate my standby database.
> My primary database is fine and I want to continue to use it for some other
> purpose.
> My question :
> Do I need to use no_truncate option during the remaining transactions backup?
> If I use NO_TRUNCATE option can I continue to use my primary database for
> other work.
> What is the difference between the regular T-LOG bkup and backup with
> NO_TRUNCATE option.
> Tks
> Mangesh|||Hi,
Backup Log command is used to backup the transaction log when database is
accessible. NO_TRUNCATE option is used when a database is inaccessi le and
you need to take a log backup. See the detailed explanation by tibor:-
http://www.karaszi.com/SQLServer/info_restore_no_truncate.asp
Thanks
Hari
SQL server MVP
"Mangesh Deshpande" <MangeshDeshpande@.discussions.microsoft.com> wrote in
message news:49D98498-C81E-4B7C-B117-F8E5AB7B7E3B@.microsoft.com...
> Hi
> I want to activate my standby database.
> My primary database is fine and I want to continue to use it for some
> other
> purpose.
> My question :
> Do I need to use no_truncate option during the remaining transactions
> backup?
> If I use NO_TRUNCATE option can I continue to use my primary database for
> other work.
> What is the difference between the regular T-LOG bkup and backup with
> NO_TRUNCATE option.
> Tks
> Mangesh

Backup Llast log - Primary crashed

HAs any one backed up the log when data files are damaged? I am
following KB article Q253817. It is not working. When I run the backup
command , it gives mdf not exists in sql server 2000. Any one has
success?If you show us the BACKUP LOG command and the exact error message (including
error number etc) we can
hopefully comment. Easiest s to execute these commands from Query Analyzer a
nd not try to drive the UI in EM.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"tram" <tram_e@.hotmail.com> wrote in message news:26ee1067.0404010502.2f64ff17@.posting.goog
le.com...
> HAs any one backed up the log when data files are damaged? I am
> following KB article Q253817. It is not working. When I run the backup
> command , it gives mdf not exists in sql server 2000. Any one has
> success?|||Thanks for your reply. The first scenario was master was intcact, lost
the datafile of DB. Then the backup log with no_truncate worked
fine.(though it giving errors with MSDE version).
The second scenario, master was intact. The datafile of DB lost. I've
created another db and dropped both daat and log of newly created db.
Copy the crashed DB log to new DB as per KB article except using the
same master. When sql server starts up, that is making the new DB
offline. When run the backup log with no_truncate, it gives error.
Could not open FCB for invalid file ID 0 in database 'test1'
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message news:<#
#mDbq#FEHA.3540@.TK2MSFTNGP09.phx.gbl>...
> If you show us the BACKUP LOG command and the exact error message (includi
ng error number etc) we can
> hopefully comment. Easiest s to execute these commands from Query Analyzer
and not try to drive the UI in EM.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "tram" <tram_e@.hotmail.com> wrote in message news:26ee1067.0404010502.2f64
ff17@.posting.google.com...

Backup Llast log - Primary crashed

HAs any one backed up the log when data files are damaged? I am
following KB article Q253817. It is not working. When I run the backup
command , it gives mdf not exists in sql server 2000. Any one has
success?
If you show us the BACKUP LOG command and the exact error message (including error number etc) we can
hopefully comment. Easiest s to execute these commands from Query Analyzer and not try to drive the UI in EM.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"tram" <tram_e@.hotmail.com> wrote in message news:26ee1067.0404010502.2f64ff17@.posting.google.c om...
> HAs any one backed up the log when data files are damaged? I am
> following KB article Q253817. It is not working. When I run the backup
> command , it gives mdf not exists in sql server 2000. Any one has
> success?
|||Thanks for your reply. The first scenario was master was intcact, lost
the datafile of DB. Then the backup log with no_truncate worked
fine.(though it giving errors with MSDE version).
The second scenario, master was intact. The datafile of DB lost. I've
created another db and dropped both daat and log of newly created db.
Copy the crashed DB log to new DB as per KB article except using the
same master. When sql server starts up, that is making the new DB
offline. When run the backup log with no_truncate, it gives error.
Could not open FCB for invalid file ID 0 in database 'test1'
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message news:<##mDbq#FEHA.3540@.TK2MSFTNGP09.phx.gbl>...
> If you show us the BACKUP LOG command and the exact error message (including error number etc) we can
> hopefully comment. Easiest s to execute these commands from Query Analyzer and not try to drive the UI in EM.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "tram" <tram_e@.hotmail.com> wrote in message news:26ee1067.0404010502.2f64ff17@.posting.google.c om...