I can't start Distributed Transaction Coordinator (MSDTC)
I have following entries in event log
Event Type: Information
Event Source: MSDTC
Event Category: TM
Event ID: 53283
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
DTC Security Configuration values. Network Administration of Transactions =
1, Network Clients = 0, Distributed Transactions using Native MSDTC
Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions = 1.
(OFF = 0 and ON = 1).
Event Type: Error
Event Source: MSDTC
Event Category: LOG
Event ID: 4163
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: some
Description:
MS DTC log file not found. After ensuring that all Resource Managers
coordinated by MS DTC have no indoubt transactions, please run
msdtc -resetlog to create the log file.
[I have tried it and with no success]
Event Type: Error
Event Source: MSDTC
Event Category: SVC
Event ID: 4437
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
The account that the MS DTC service is running under is invalid. This can
happen if the service account information has been changed using the
Services snap-in in Microsoft Management Console (MMC). MS DTC service will
continue to start. Please make sure that the MS DTC service account
information is updated using the Component Services Explorer.
How can I fix it?
It seems that because of it I can't install SQL Server 2005 Express.
If it is wrong newsgroup maybe someone can redirect me to the right one.
Thanks,
Shimon.
Go to Control panel->services or Administrative Tools-> services and find
the MS DTC service. There will be a properties box where you can change the
login/password under which dtc run... The first error message states that
the login/password is bad... (Maybe someone changed the password for the DTC
login...)
Hope this helps.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shimon Sim" <estshim@.att.net> wrote in message
news:ufa0SmIZEHA.728@.TK2MSFTNGP09.phx.gbl...
> I can't start Distributed Transaction Coordinator (MSDTC)
> I have following entries in event log
>
> Event Type: Information
> Event Source: MSDTC
> Event Category: TM
> Event ID: 53283
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> DTC Security Configuration values. Network Administration of Transactions
=
> 1, Network Clients = 0, Distributed Transactions using Native MSDTC
> Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions =
1.
> (OFF = 0 and ON = 1).
> Event Type: Error
> Event Source: MSDTC
> Event Category: LOG
> Event ID: 4163
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: some
> Description:
> MS DTC log file not found. After ensuring that all Resource Managers
> coordinated by MS DTC have no indoubt transactions, please run
> msdtc -resetlog to create the log file.
> [I have tried it and with no success]
> Event Type: Error
> Event Source: MSDTC
> Event Category: SVC
> Event ID: 4437
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> The account that the MS DTC service is running under is invalid. This can
> happen if the service account information has been changed using the
> Services snap-in in Microsoft Management Console (MMC). MS DTC service
will
> continue to start. Please make sure that the MS DTC service account
> information is updated using the Component Services Explorer.
> How can I fix it?
> It seems that because of it I can't install SQL Server 2005 Express.
> If it is wrong newsgroup maybe someone can redirect me to the right one.
> Thanks,
> Shimon.
>
>
|||Is a local account option is good for this?
Shimon
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:O3zSJSOZEHA.3476@.tk2msftngp13.phx.gbl...
> Go to Control panel->services or Administrative Tools-> services and find
> the MS DTC service. There will be a properties box where you can change
the
> login/password under which dtc run... The first error message states that
> the login/password is bad... (Maybe someone changed the password for the
DTC[vbcol=seagreen]
> login...)
> Hope this helps.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Shimon Sim" <estshim@.att.net> wrote in message
> news:ufa0SmIZEHA.728@.TK2MSFTNGP09.phx.gbl...
Transactions[vbcol=seagreen]
> =
=[vbcol=seagreen]
> 1.
can
> will
>
Showing posts with label entries. Show all posts
Showing posts with label entries. Show all posts
Sunday, March 25, 2012
Can't start MSDTC
I can't start Distributed Transaction Coordinator (MSDTC)
I have following entries in event log
Event Type: Information
Event Source: MSDTC
Event Category: TM
Event ID: 53283
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
DTC Security Configuration values. Network Administration of Transactions =
1, Network Clients = 0, Distributed Transactions using Native MSDTC
Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions = 1.
(OFF = 0 and ON = 1).
Event Type: Error
Event Source: MSDTC
Event Category: LOG
Event ID: 4163
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: some
Description:
MS DTC log file not found. After ensuring that all Resource Managers
coordinated by MS DTC have no indoubt transactions, please run
msdtc -resetlog to create the log file.
[I have tried it and with no success]
Event Type: Error
Event Source: MSDTC
Event Category: SVC
Event ID: 4437
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
The account that the MS DTC service is running under is invalid. This can
happen if the service account information has been changed using the
Services snap-in in Microsoft Management Console (MMC). MS DTC service will
continue to start. Please make sure that the MS DTC service account
information is updated using the Component Services Explorer.
How can I fix it?
It seems that because of it I can't install SQL Server 2005 Express.
If it is wrong newsgroup maybe someone can redirect me to the right one.
Thanks,
Shimon.Go to Control panel->services or Administrative Tools-> services and find
the MS DTC service. There will be a properties box where you can change the
login/password under which dtc run... The first error message states that
the login/password is bad... (Maybe someone changed the password for the DTC
login...)
Hope this helps.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shimon Sim" <estshim@.att.net> wrote in message
news:ufa0SmIZEHA.728@.TK2MSFTNGP09.phx.gbl...
> I can't start Distributed Transaction Coordinator (MSDTC)
> I have following entries in event log
>
> Event Type: Information
> Event Source: MSDTC
> Event Category: TM
> Event ID: 53283
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> DTC Security Configuration values. Network Administration of Transactions
=
> 1, Network Clients = 0, Distributed Transactions using Native MSDTC
> Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions =
1.
> (OFF = 0 and ON = 1).
> Event Type: Error
> Event Source: MSDTC
> Event Category: LOG
> Event ID: 4163
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: some
> Description:
> MS DTC log file not found. After ensuring that all Resource Managers
> coordinated by MS DTC have no indoubt transactions, please run
> msdtc -resetlog to create the log file.
> [I have tried it and with no success]
> Event Type: Error
> Event Source: MSDTC
> Event Category: SVC
> Event ID: 4437
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> The account that the MS DTC service is running under is invalid. This can
> happen if the service account information has been changed using the
> Services snap-in in Microsoft Management Console (MMC). MS DTC service
will
> continue to start. Please make sure that the MS DTC service account
> information is updated using the Component Services Explorer.
> How can I fix it?
> It seems that because of it I can't install SQL Server 2005 Express.
> If it is wrong newsgroup maybe someone can redirect me to the right one.
> Thanks,
> Shimon.
>
>|||Is a local account option is good for this?
Shimon
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:O3zSJSOZEHA.3476@.tk2msftngp13.phx.gbl...
> Go to Control panel->services or Administrative Tools-> services and find
> the MS DTC service. There will be a properties box where you can change
the
> login/password under which dtc run... The first error message states that
> the login/password is bad... (Maybe someone changed the password for the
DTC
> login...)
> Hope this helps.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Shimon Sim" <estshim@.att.net> wrote in message
> news:ufa0SmIZEHA.728@.TK2MSFTNGP09.phx.gbl...
Transactions[vbcol=seagreen]
> =
=[vbcol=seagreen]
> 1.
can[vbcol=seagreen]
> will
>
I have following entries in event log
Event Type: Information
Event Source: MSDTC
Event Category: TM
Event ID: 53283
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
DTC Security Configuration values. Network Administration of Transactions =
1, Network Clients = 0, Distributed Transactions using Native MSDTC
Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions = 1.
(OFF = 0 and ON = 1).
Event Type: Error
Event Source: MSDTC
Event Category: LOG
Event ID: 4163
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: some
Description:
MS DTC log file not found. After ensuring that all Resource Managers
coordinated by MS DTC have no indoubt transactions, please run
msdtc -resetlog to create the log file.
[I have tried it and with no success]
Event Type: Error
Event Source: MSDTC
Event Category: SVC
Event ID: 4437
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
The account that the MS DTC service is running under is invalid. This can
happen if the service account information has been changed using the
Services snap-in in Microsoft Management Console (MMC). MS DTC service will
continue to start. Please make sure that the MS DTC service account
information is updated using the Component Services Explorer.
How can I fix it?
It seems that because of it I can't install SQL Server 2005 Express.
If it is wrong newsgroup maybe someone can redirect me to the right one.
Thanks,
Shimon.Go to Control panel->services or Administrative Tools-> services and find
the MS DTC service. There will be a properties box where you can change the
login/password under which dtc run... The first error message states that
the login/password is bad... (Maybe someone changed the password for the DTC
login...)
Hope this helps.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shimon Sim" <estshim@.att.net> wrote in message
news:ufa0SmIZEHA.728@.TK2MSFTNGP09.phx.gbl...
> I can't start Distributed Transaction Coordinator (MSDTC)
> I have following entries in event log
>
> Event Type: Information
> Event Source: MSDTC
> Event Category: TM
> Event ID: 53283
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> DTC Security Configuration values. Network Administration of Transactions
=
> 1, Network Clients = 0, Distributed Transactions using Native MSDTC
> Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions =
1.
> (OFF = 0 and ON = 1).
> Event Type: Error
> Event Source: MSDTC
> Event Category: LOG
> Event ID: 4163
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: some
> Description:
> MS DTC log file not found. After ensuring that all Resource Managers
> coordinated by MS DTC have no indoubt transactions, please run
> msdtc -resetlog to create the log file.
> [I have tried it and with no success]
> Event Type: Error
> Event Source: MSDTC
> Event Category: SVC
> Event ID: 4437
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> The account that the MS DTC service is running under is invalid. This can
> happen if the service account information has been changed using the
> Services snap-in in Microsoft Management Console (MMC). MS DTC service
will
> continue to start. Please make sure that the MS DTC service account
> information is updated using the Component Services Explorer.
> How can I fix it?
> It seems that because of it I can't install SQL Server 2005 Express.
> If it is wrong newsgroup maybe someone can redirect me to the right one.
> Thanks,
> Shimon.
>
>|||Is a local account option is good for this?
Shimon
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:O3zSJSOZEHA.3476@.tk2msftngp13.phx.gbl...
> Go to Control panel->services or Administrative Tools-> services and find
> the MS DTC service. There will be a properties box where you can change
the
> login/password under which dtc run... The first error message states that
> the login/password is bad... (Maybe someone changed the password for the
DTC
> login...)
> Hope this helps.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Shimon Sim" <estshim@.att.net> wrote in message
> news:ufa0SmIZEHA.728@.TK2MSFTNGP09.phx.gbl...
Transactions[vbcol=seagreen]
> =
=[vbcol=seagreen]
> 1.
can[vbcol=seagreen]
> will
>
Can't start MSDTC
I can't start Distributed Transaction Coordinator (MSDTC)
I have following entries in event log
Event Type: Information
Event Source: MSDTC
Event Category: TM
Event ID: 53283
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
DTC Security Configuration values. Network Administration of Transactions = 1, Network Clients = 0, Distributed Transactions using Native MSDTC
Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions = 1.
(OFF = 0 and ON = 1).
Event Type: Error
Event Source: MSDTC
Event Category: LOG
Event ID: 4163
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: some
Description:
MS DTC log file not found. After ensuring that all Resource Managers
coordinated by MS DTC have no indoubt transactions, please run
msdtc -resetlog to create the log file.
[I have tried it and with no success]
Event Type: Error
Event Source: MSDTC
Event Category: SVC
Event ID: 4437
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
The account that the MS DTC service is running under is invalid. This can
happen if the service account information has been changed using the
Services snap-in in Microsoft Management Console (MMC). MS DTC service will
continue to start. Please make sure that the MS DTC service account
information is updated using the Component Services Explorer.
How can I fix it?
It seems that because of it I can't install SQL Server 2005 Express.
If it is wrong newsgroup maybe someone can redirect me to the right one.
Thanks,
Shimon.Go to Control panel->services or Administrative Tools-> services and find
the MS DTC service. There will be a properties box where you can change the
login/password under which dtc run... The first error message states that
the login/password is bad... (Maybe someone changed the password for the DTC
login...)
Hope this helps.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shimon Sim" <estshim@.att.net> wrote in message
news:ufa0SmIZEHA.728@.TK2MSFTNGP09.phx.gbl...
> I can't start Distributed Transaction Coordinator (MSDTC)
> I have following entries in event log
>
> Event Type: Information
> Event Source: MSDTC
> Event Category: TM
> Event ID: 53283
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> DTC Security Configuration values. Network Administration of Transactions
=> 1, Network Clients = 0, Distributed Transactions using Native MSDTC
> Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions =1.
> (OFF = 0 and ON = 1).
> Event Type: Error
> Event Source: MSDTC
> Event Category: LOG
> Event ID: 4163
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: some
> Description:
> MS DTC log file not found. After ensuring that all Resource Managers
> coordinated by MS DTC have no indoubt transactions, please run
> msdtc -resetlog to create the log file.
> [I have tried it and with no success]
> Event Type: Error
> Event Source: MSDTC
> Event Category: SVC
> Event ID: 4437
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> The account that the MS DTC service is running under is invalid. This can
> happen if the service account information has been changed using the
> Services snap-in in Microsoft Management Console (MMC). MS DTC service
will
> continue to start. Please make sure that the MS DTC service account
> information is updated using the Component Services Explorer.
> How can I fix it?
> It seems that because of it I can't install SQL Server 2005 Express.
> If it is wrong newsgroup maybe someone can redirect me to the right one.
> Thanks,
> Shimon.
>
>|||Is a local account option is good for this?
Shimon
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:O3zSJSOZEHA.3476@.tk2msftngp13.phx.gbl...
> Go to Control panel->services or Administrative Tools-> services and find
> the MS DTC service. There will be a properties box where you can change
the
> login/password under which dtc run... The first error message states that
> the login/password is bad... (Maybe someone changed the password for the
DTC
> login...)
> Hope this helps.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Shimon Sim" <estshim@.att.net> wrote in message
> news:ufa0SmIZEHA.728@.TK2MSFTNGP09.phx.gbl...
> > I can't start Distributed Transaction Coordinator (MSDTC)
> > I have following entries in event log
> >
> >
> > Event Type: Information
> > Event Source: MSDTC
> > Event Category: TM
> > Event ID: 53283
> > Date: 7/7/2004
> > Time: 9:19:01 AM
> > User: N/A
> > Computer: Some
> > Description:
> > DTC Security Configuration values. Network Administration of
Transactions
> => > 1, Network Clients = 0, Distributed Transactions using Native MSDTC
> > Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions
=> 1.
> > (OFF = 0 and ON = 1).
> >
> > Event Type: Error
> > Event Source: MSDTC
> > Event Category: LOG
> > Event ID: 4163
> > Date: 7/7/2004
> > Time: 9:19:01 AM
> > User: N/A
> > Computer: some
> > Description:
> > MS DTC log file not found. After ensuring that all Resource Managers
> > coordinated by MS DTC have no indoubt transactions, please run
> > msdtc -resetlog to create the log file.
> > [I have tried it and with no success]
> >
> > Event Type: Error
> > Event Source: MSDTC
> > Event Category: SVC
> > Event ID: 4437
> > Date: 7/7/2004
> > Time: 9:19:01 AM
> > User: N/A
> > Computer: Some
> > Description:
> > The account that the MS DTC service is running under is invalid. This
can
> > happen if the service account information has been changed using the
> > Services snap-in in Microsoft Management Console (MMC). MS DTC service
> will
> > continue to start. Please make sure that the MS DTC service account
> > information is updated using the Component Services Explorer.
> >
> > How can I fix it?
> > It seems that because of it I can't install SQL Server 2005 Express.
> > If it is wrong newsgroup maybe someone can redirect me to the right one.
> > Thanks,
> > Shimon.
> >
> >
> >
> >
>sql
I have following entries in event log
Event Type: Information
Event Source: MSDTC
Event Category: TM
Event ID: 53283
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
DTC Security Configuration values. Network Administration of Transactions = 1, Network Clients = 0, Distributed Transactions using Native MSDTC
Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions = 1.
(OFF = 0 and ON = 1).
Event Type: Error
Event Source: MSDTC
Event Category: LOG
Event ID: 4163
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: some
Description:
MS DTC log file not found. After ensuring that all Resource Managers
coordinated by MS DTC have no indoubt transactions, please run
msdtc -resetlog to create the log file.
[I have tried it and with no success]
Event Type: Error
Event Source: MSDTC
Event Category: SVC
Event ID: 4437
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
The account that the MS DTC service is running under is invalid. This can
happen if the service account information has been changed using the
Services snap-in in Microsoft Management Console (MMC). MS DTC service will
continue to start. Please make sure that the MS DTC service account
information is updated using the Component Services Explorer.
How can I fix it?
It seems that because of it I can't install SQL Server 2005 Express.
If it is wrong newsgroup maybe someone can redirect me to the right one.
Thanks,
Shimon.Go to Control panel->services or Administrative Tools-> services and find
the MS DTC service. There will be a properties box where you can change the
login/password under which dtc run... The first error message states that
the login/password is bad... (Maybe someone changed the password for the DTC
login...)
Hope this helps.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shimon Sim" <estshim@.att.net> wrote in message
news:ufa0SmIZEHA.728@.TK2MSFTNGP09.phx.gbl...
> I can't start Distributed Transaction Coordinator (MSDTC)
> I have following entries in event log
>
> Event Type: Information
> Event Source: MSDTC
> Event Category: TM
> Event ID: 53283
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> DTC Security Configuration values. Network Administration of Transactions
=> 1, Network Clients = 0, Distributed Transactions using Native MSDTC
> Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions =1.
> (OFF = 0 and ON = 1).
> Event Type: Error
> Event Source: MSDTC
> Event Category: LOG
> Event ID: 4163
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: some
> Description:
> MS DTC log file not found. After ensuring that all Resource Managers
> coordinated by MS DTC have no indoubt transactions, please run
> msdtc -resetlog to create the log file.
> [I have tried it and with no success]
> Event Type: Error
> Event Source: MSDTC
> Event Category: SVC
> Event ID: 4437
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> The account that the MS DTC service is running under is invalid. This can
> happen if the service account information has been changed using the
> Services snap-in in Microsoft Management Console (MMC). MS DTC service
will
> continue to start. Please make sure that the MS DTC service account
> information is updated using the Component Services Explorer.
> How can I fix it?
> It seems that because of it I can't install SQL Server 2005 Express.
> If it is wrong newsgroup maybe someone can redirect me to the right one.
> Thanks,
> Shimon.
>
>|||Is a local account option is good for this?
Shimon
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:O3zSJSOZEHA.3476@.tk2msftngp13.phx.gbl...
> Go to Control panel->services or Administrative Tools-> services and find
> the MS DTC service. There will be a properties box where you can change
the
> login/password under which dtc run... The first error message states that
> the login/password is bad... (Maybe someone changed the password for the
DTC
> login...)
> Hope this helps.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Shimon Sim" <estshim@.att.net> wrote in message
> news:ufa0SmIZEHA.728@.TK2MSFTNGP09.phx.gbl...
> > I can't start Distributed Transaction Coordinator (MSDTC)
> > I have following entries in event log
> >
> >
> > Event Type: Information
> > Event Source: MSDTC
> > Event Category: TM
> > Event ID: 53283
> > Date: 7/7/2004
> > Time: 9:19:01 AM
> > User: N/A
> > Computer: Some
> > Description:
> > DTC Security Configuration values. Network Administration of
Transactions
> => > 1, Network Clients = 0, Distributed Transactions using Native MSDTC
> > Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions
=> 1.
> > (OFF = 0 and ON = 1).
> >
> > Event Type: Error
> > Event Source: MSDTC
> > Event Category: LOG
> > Event ID: 4163
> > Date: 7/7/2004
> > Time: 9:19:01 AM
> > User: N/A
> > Computer: some
> > Description:
> > MS DTC log file not found. After ensuring that all Resource Managers
> > coordinated by MS DTC have no indoubt transactions, please run
> > msdtc -resetlog to create the log file.
> > [I have tried it and with no success]
> >
> > Event Type: Error
> > Event Source: MSDTC
> > Event Category: SVC
> > Event ID: 4437
> > Date: 7/7/2004
> > Time: 9:19:01 AM
> > User: N/A
> > Computer: Some
> > Description:
> > The account that the MS DTC service is running under is invalid. This
can
> > happen if the service account information has been changed using the
> > Services snap-in in Microsoft Management Console (MMC). MS DTC service
> will
> > continue to start. Please make sure that the MS DTC service account
> > information is updated using the Component Services Explorer.
> >
> > How can I fix it?
> > It seems that because of it I can't install SQL Server 2005 Express.
> > If it is wrong newsgroup maybe someone can redirect me to the right one.
> > Thanks,
> > Shimon.
> >
> >
> >
> >
>sql
Can't start DTC
I can't start Distributed Transaction Coordinator (MSDTC)
I have following entries in event log
Event Type: Information
Event Source: MSDTC
Event Category: TM
Event ID: 53283
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
DTC Security Configuration values. Network Administration of Transactions =
1, Network Clients = 0, Distributed Transactions using Native MSDTC
Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions = 1.
(OFF = 0 and ON = 1).
Event Type: Error
Event Source: MSDTC
Event Category: LOG
Event ID: 4163
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: some
Description:
MS DTC log file not found. After ensuring that all Resource Managers
coordinated by MS DTC have no indoubt transactions, please run
msdtc -resetlog to create the log file.
Event Type: Error
Event Source: MSDTC
Event Category: SVC
Event ID: 4437
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
The account that the MS DTC service is running under is invalid. This can
happen if the service account information has been changed using the
Services snap-in in Microsoft Management Console (MMC). MS DTC service will
continue to start. Please make sure that the MS DTC service account
information is updated using the Component Services Explorer.
How can I fix it?
It seems that because of it I can't install SQL Server 2005 Express.
If it is wrong newsgroup maybe someone can redirect me to the right one.
Thanks,
Shimon.
Check what account is used to start MSDTC and its privileges.
"Shimon Sim" wrote:
> I can't start Distributed Transaction Coordinator (MSDTC)
> I have following entries in event log
>
> Event Type: Information
> Event Source: MSDTC
> Event Category: TM
> Event ID: 53283
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> DTC Security Configuration values. Network Administration of Transactions =
> 1, Network Clients = 0, Distributed Transactions using Native MSDTC
> Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions = 1.
> (OFF = 0 and ON = 1).
> Event Type: Error
> Event Source: MSDTC
> Event Category: LOG
> Event ID: 4163
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: some
> Description:
> MS DTC log file not found. After ensuring that all Resource Managers
> coordinated by MS DTC have no indoubt transactions, please run
> msdtc -resetlog to create the log file.
>
> Event Type: Error
> Event Source: MSDTC
> Event Category: SVC
> Event ID: 4437
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> The account that the MS DTC service is running under is invalid. This can
> happen if the service account information has been changed using the
> Services snap-in in Microsoft Management Console (MMC). MS DTC service will
> continue to start. Please make sure that the MS DTC service account
> information is updated using the Component Services Explorer.
> How can I fix it?
> It seems that because of it I can't install SQL Server 2005 Express.
> If it is wrong newsgroup maybe someone can redirect me to the right one.
> Thanks,
> Shimon.
>
>
|||Thanks,
I found the problem. I tried to use local account for this service but it
must use special account. And also Log for it go corrupted (It seems that
because of using wrong account I had to reset log )
Shimon.
"SatyaSKJ" <SatyaSKJ@.discussions.microsoft.com> wrote in message
news:15DD352E-627F-46FF-8EA1-B70197A45C32@.microsoft.com...[vbcol=seagreen]
> Check what account is used to start MSDTC and its privileges.
> "Shimon Sim" wrote:
Transactions =[vbcol=seagreen]
= 1.[vbcol=seagreen]
can[vbcol=seagreen]
will[vbcol=seagreen]
I have following entries in event log
Event Type: Information
Event Source: MSDTC
Event Category: TM
Event ID: 53283
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
DTC Security Configuration values. Network Administration of Transactions =
1, Network Clients = 0, Distributed Transactions using Native MSDTC
Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions = 1.
(OFF = 0 and ON = 1).
Event Type: Error
Event Source: MSDTC
Event Category: LOG
Event ID: 4163
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: some
Description:
MS DTC log file not found. After ensuring that all Resource Managers
coordinated by MS DTC have no indoubt transactions, please run
msdtc -resetlog to create the log file.
Event Type: Error
Event Source: MSDTC
Event Category: SVC
Event ID: 4437
Date: 7/7/2004
Time: 9:19:01 AM
User: N/A
Computer: Some
Description:
The account that the MS DTC service is running under is invalid. This can
happen if the service account information has been changed using the
Services snap-in in Microsoft Management Console (MMC). MS DTC service will
continue to start. Please make sure that the MS DTC service account
information is updated using the Component Services Explorer.
How can I fix it?
It seems that because of it I can't install SQL Server 2005 Express.
If it is wrong newsgroup maybe someone can redirect me to the right one.
Thanks,
Shimon.
Check what account is used to start MSDTC and its privileges.
"Shimon Sim" wrote:
> I can't start Distributed Transaction Coordinator (MSDTC)
> I have following entries in event log
>
> Event Type: Information
> Event Source: MSDTC
> Event Category: TM
> Event ID: 53283
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> DTC Security Configuration values. Network Administration of Transactions =
> 1, Network Clients = 0, Distributed Transactions using Native MSDTC
> Protocol = 1, Transaction Internet Protocol (TIP) = 0, XA Transactions = 1.
> (OFF = 0 and ON = 1).
> Event Type: Error
> Event Source: MSDTC
> Event Category: LOG
> Event ID: 4163
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: some
> Description:
> MS DTC log file not found. After ensuring that all Resource Managers
> coordinated by MS DTC have no indoubt transactions, please run
> msdtc -resetlog to create the log file.
>
> Event Type: Error
> Event Source: MSDTC
> Event Category: SVC
> Event ID: 4437
> Date: 7/7/2004
> Time: 9:19:01 AM
> User: N/A
> Computer: Some
> Description:
> The account that the MS DTC service is running under is invalid. This can
> happen if the service account information has been changed using the
> Services snap-in in Microsoft Management Console (MMC). MS DTC service will
> continue to start. Please make sure that the MS DTC service account
> information is updated using the Component Services Explorer.
> How can I fix it?
> It seems that because of it I can't install SQL Server 2005 Express.
> If it is wrong newsgroup maybe someone can redirect me to the right one.
> Thanks,
> Shimon.
>
>
|||Thanks,
I found the problem. I tried to use local account for this service but it
must use special account. And also Log for it go corrupted (It seems that
because of using wrong account I had to reset log )
Shimon.
"SatyaSKJ" <SatyaSKJ@.discussions.microsoft.com> wrote in message
news:15DD352E-627F-46FF-8EA1-B70197A45C32@.microsoft.com...[vbcol=seagreen]
> Check what account is used to start MSDTC and its privileges.
> "Shimon Sim" wrote:
Transactions =[vbcol=seagreen]
= 1.[vbcol=seagreen]
can[vbcol=seagreen]
will[vbcol=seagreen]
Thursday, March 8, 2012
Can't remove inactive entries from transaction log
My database is set to Full Recovery model. I can shrink my transaction log
by executing a logfile backup, but when I execute a Full or Incremental
backup, this option is disabled. I don't understand why. With the execution
of a successful backup, entries in the log prior to the point of backup
become irrelevant! I might need subsequent logfile transactions in the event
of a failure, but I won't need the logfile prior to the point of backup. So
why can't I shrink the logfile as part and parcel of the backup operation?
Must I always execute a separate logfile backup prior to my Full /
Incremental backup for the sole purpose of shrinking the logfile? I don't
get it.
Thanks for your advice!
- Joe Geretz -
Joseph
If I understood you correctly you have to run LOG file backup with INIT
option to clear all entries prior the FULL backup database.
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> My database is set to Full Recovery model. I can shrink my transaction log
> by executing a logfile backup, but when I execute a Full or Incremental
> backup, this option is disabled. I don't understand why. With the
execution
> of a successful backup, entries in the log prior to the point of backup
> become irrelevant! I might need subsequent logfile transactions in the
event
> of a failure, but I won't need the logfile prior to the point of backup.
So
> why can't I shrink the logfile as part and parcel of the backup operation?
> Must I always execute a separate logfile backup prior to my Full /
> Incremental backup for the sole purpose of shrinking the logfile? I don't
> get it.
> Thanks for your advice!
> - Joe Geretz -
>
|||Joe,
A full database backup or differential backup DO NOT truncate the log ( as
you have discovered.) This is by design... Here is a sample backup plan
Full1 Full2
log1 log2 log3 log4 log5,,,, etc
If we die are the log 5 backup, we can restore from FULL2, then restore all
of the logs and we are good to go... But what if the FULL2 backup tape is
missing or corrupted? You can begin by restoring the FULL1 backup, then
log1, log2, log3, log4. etc and still get up-to-the-minute recover without
loss of data... Log 4 contains ALL OF THE CHANGES since log3, Even when a
full or differential database backup was done between 3 and 4. The full,
and differential backups do NOT truncate the log SPECIFICALLY to give us the
opportunity to restore from a grandparent ( FULL1 ) or even older full or
differential backup and not lose data...
If you do not need the log backups, and wish to keep the log small, you
might wish to consider using the Simple recovery model for the database...
This means you will only be able to recover to the last full or differential
backup however.
Hope this helps..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> My database is set to Full Recovery model. I can shrink my transaction log
> by executing a logfile backup, but when I execute a Full or Incremental
> backup, this option is disabled. I don't understand why. With the
execution
> of a successful backup, entries in the log prior to the point of backup
> become irrelevant! I might need subsequent logfile transactions in the
event
> of a failure, but I won't need the logfile prior to the point of backup.
So
> why can't I shrink the logfile as part and parcel of the backup operation?
> Must I always execute a separate logfile backup prior to my Full /
> Incremental backup for the sole purpose of shrinking the logfile? I don't
> get it.
> Thanks for your advice!
> - Joe Geretz -
>
|||Wayne
Why not just clean up with INIT option the LOG file after each FULL backup?
Why to blow the LOG file?
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eqD5jF9cEHA.3944@.tk2msftngp13.phx.gbl...
> Joe,
> A full database backup or differential backup DO NOT truncate the log ( as
> you have discovered.) This is by design... Here is a sample backup plan
> Full1 Full2
> log1 log2 log3 log4 log5,,,, etc
> If we die are the log 5 backup, we can restore from FULL2, then restore
all
> of the logs and we are good to go... But what if the FULL2 backup tape is
> missing or corrupted? You can begin by restoring the FULL1 backup, then
> log1, log2, log3, log4. etc and still get up-to-the-minute recover without
> loss of data... Log 4 contains ALL OF THE CHANGES since log3, Even when a
> full or differential database backup was done between 3 and 4. The full,
> and differential backups do NOT truncate the log SPECIFICALLY to give us
the
> opportunity to restore from a grandparent ( FULL1 ) or even older full or
> differential backup and not lose data...
> If you do not need the log backups, and wish to keep the log small, you
> might wish to consider using the Simple recovery model for the database...
> This means you will only be able to recover to the last full or
differential[vbcol=seagreen]
> backup however.
> Hope this helps..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
log[vbcol=seagreen]
> execution
> event
> So
operation?[vbcol=seagreen]
don't
>
by executing a logfile backup, but when I execute a Full or Incremental
backup, this option is disabled. I don't understand why. With the execution
of a successful backup, entries in the log prior to the point of backup
become irrelevant! I might need subsequent logfile transactions in the event
of a failure, but I won't need the logfile prior to the point of backup. So
why can't I shrink the logfile as part and parcel of the backup operation?
Must I always execute a separate logfile backup prior to my Full /
Incremental backup for the sole purpose of shrinking the logfile? I don't
get it.
Thanks for your advice!
- Joe Geretz -
Joseph
If I understood you correctly you have to run LOG file backup with INIT
option to clear all entries prior the FULL backup database.
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> My database is set to Full Recovery model. I can shrink my transaction log
> by executing a logfile backup, but when I execute a Full or Incremental
> backup, this option is disabled. I don't understand why. With the
execution
> of a successful backup, entries in the log prior to the point of backup
> become irrelevant! I might need subsequent logfile transactions in the
event
> of a failure, but I won't need the logfile prior to the point of backup.
So
> why can't I shrink the logfile as part and parcel of the backup operation?
> Must I always execute a separate logfile backup prior to my Full /
> Incremental backup for the sole purpose of shrinking the logfile? I don't
> get it.
> Thanks for your advice!
> - Joe Geretz -
>
|||Joe,
A full database backup or differential backup DO NOT truncate the log ( as
you have discovered.) This is by design... Here is a sample backup plan
Full1 Full2
log1 log2 log3 log4 log5,,,, etc
If we die are the log 5 backup, we can restore from FULL2, then restore all
of the logs and we are good to go... But what if the FULL2 backup tape is
missing or corrupted? You can begin by restoring the FULL1 backup, then
log1, log2, log3, log4. etc and still get up-to-the-minute recover without
loss of data... Log 4 contains ALL OF THE CHANGES since log3, Even when a
full or differential database backup was done between 3 and 4. The full,
and differential backups do NOT truncate the log SPECIFICALLY to give us the
opportunity to restore from a grandparent ( FULL1 ) or even older full or
differential backup and not lose data...
If you do not need the log backups, and wish to keep the log small, you
might wish to consider using the Simple recovery model for the database...
This means you will only be able to recover to the last full or differential
backup however.
Hope this helps..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> My database is set to Full Recovery model. I can shrink my transaction log
> by executing a logfile backup, but when I execute a Full or Incremental
> backup, this option is disabled. I don't understand why. With the
execution
> of a successful backup, entries in the log prior to the point of backup
> become irrelevant! I might need subsequent logfile transactions in the
event
> of a failure, but I won't need the logfile prior to the point of backup.
So
> why can't I shrink the logfile as part and parcel of the backup operation?
> Must I always execute a separate logfile backup prior to my Full /
> Incremental backup for the sole purpose of shrinking the logfile? I don't
> get it.
> Thanks for your advice!
> - Joe Geretz -
>
|||Wayne
Why not just clean up with INIT option the LOG file after each FULL backup?
Why to blow the LOG file?
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eqD5jF9cEHA.3944@.tk2msftngp13.phx.gbl...
> Joe,
> A full database backup or differential backup DO NOT truncate the log ( as
> you have discovered.) This is by design... Here is a sample backup plan
> Full1 Full2
> log1 log2 log3 log4 log5,,,, etc
> If we die are the log 5 backup, we can restore from FULL2, then restore
all
> of the logs and we are good to go... But what if the FULL2 backup tape is
> missing or corrupted? You can begin by restoring the FULL1 backup, then
> log1, log2, log3, log4. etc and still get up-to-the-minute recover without
> loss of data... Log 4 contains ALL OF THE CHANGES since log3, Even when a
> full or differential database backup was done between 3 and 4. The full,
> and differential backups do NOT truncate the log SPECIFICALLY to give us
the
> opportunity to restore from a grandparent ( FULL1 ) or even older full or
> differential backup and not lose data...
> If you do not need the log backups, and wish to keep the log small, you
> might wish to consider using the Simple recovery model for the database...
> This means you will only be able to recover to the last full or
differential[vbcol=seagreen]
> backup however.
> Hope this helps..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
log[vbcol=seagreen]
> execution
> event
> So
operation?[vbcol=seagreen]
don't
>
Can't remove inactive entries from transaction log
My database is set to Full Recovery model. I can shrink my transaction log
by executing a logfile backup, but when I execute a Full or Incremental
backup, this option is disabled. I don't understand why. With the execution
of a successful backup, entries in the log prior to the point of backup
become irrelevant! I might need subsequent logfile transactions in the event
of a failure, but I won't need the logfile prior to the point of backup. So
why can't I shrink the logfile as part and parcel of the backup operation?
Must I always execute a separate logfile backup prior to my Full /
Incremental backup for the sole purpose of shrinking the logfile? I don't
get it.
Thanks for your advice!
- Joe Geretz -Joseph
If I understood you correctly you have to run LOG file backup with INIT
option to clear all entries prior the FULL backup database.
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> My database is set to Full Recovery model. I can shrink my transaction log
> by executing a logfile backup, but when I execute a Full or Incremental
> backup, this option is disabled. I don't understand why. With the
execution
> of a successful backup, entries in the log prior to the point of backup
> become irrelevant! I might need subsequent logfile transactions in the
event
> of a failure, but I won't need the logfile prior to the point of backup.
So
> why can't I shrink the logfile as part and parcel of the backup operation?
> Must I always execute a separate logfile backup prior to my Full /
> Incremental backup for the sole purpose of shrinking the logfile? I don't
> get it.
> Thanks for your advice!
> - Joe Geretz -
>|||Joe,
A full database backup or differential backup DO NOT truncate the log ( as
you have discovered.) This is by design... Here is a sample backup plan
Full1 Full2
log1 log2 log3 log4 log5,,,, etc
If we die are the log 5 backup, we can restore from FULL2, then restore all
of the logs and we are good to go... But what if the FULL2 backup tape is
missing or corrupted? You can begin by restoring the FULL1 backup, then
log1, log2, log3, log4. etc and still get up-to-the-minute recover without
loss of data... Log 4 contains ALL OF THE CHANGES since log3, Even when a
full or differential database backup was done between 3 and 4. The full,
and differential backups do NOT truncate the log SPECIFICALLY to give us the
opportunity to restore from a grandparent ( FULL1 ) or even older full or
differential backup and not lose data...
If you do not need the log backups, and wish to keep the log small, you
might wish to consider using the Simple recovery model for the database...
This means you will only be able to recover to the last full or differential
backup however.
Hope this helps..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> My database is set to Full Recovery model. I can shrink my transaction log
> by executing a logfile backup, but when I execute a Full or Incremental
> backup, this option is disabled. I don't understand why. With the
execution
> of a successful backup, entries in the log prior to the point of backup
> become irrelevant! I might need subsequent logfile transactions in the
event
> of a failure, but I won't need the logfile prior to the point of backup.
So
> why can't I shrink the logfile as part and parcel of the backup operation?
> Must I always execute a separate logfile backup prior to my Full /
> Incremental backup for the sole purpose of shrinking the logfile? I don't
> get it.
> Thanks for your advice!
> - Joe Geretz -
>|||Wayne
Why not just clean up with INIT option the LOG file after each FULL backup?
Why to blow the LOG file?
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eqD5jF9cEHA.3944@.tk2msftngp13.phx.gbl...
> Joe,
> A full database backup or differential backup DO NOT truncate the log ( as
> you have discovered.) This is by design... Here is a sample backup plan
> Full1 Full2
> log1 log2 log3 log4 log5,,,, etc
> If we die are the log 5 backup, we can restore from FULL2, then restore
all
> of the logs and we are good to go... But what if the FULL2 backup tape is
> missing or corrupted? You can begin by restoring the FULL1 backup, then
> log1, log2, log3, log4. etc and still get up-to-the-minute recover without
> loss of data... Log 4 contains ALL OF THE CHANGES since log3, Even when a
> full or differential database backup was done between 3 and 4. The full,
> and differential backups do NOT truncate the log SPECIFICALLY to give us
the
> opportunity to restore from a grandparent ( FULL1 ) or even older full or
> differential backup and not lose data...
> If you do not need the log backups, and wish to keep the log small, you
> might wish to consider using the Simple recovery model for the database...
> This means you will only be able to recover to the last full or
differential
> backup however.
> Hope this helps..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> > My database is set to Full Recovery model. I can shrink my transaction
log
> > by executing a logfile backup, but when I execute a Full or Incremental
> > backup, this option is disabled. I don't understand why. With the
> execution
> > of a successful backup, entries in the log prior to the point of backup
> > become irrelevant! I might need subsequent logfile transactions in the
> event
> > of a failure, but I won't need the logfile prior to the point of backup.
> So
> > why can't I shrink the logfile as part and parcel of the backup
operation?
> > Must I always execute a separate logfile backup prior to my Full /
> > Incremental backup for the sole purpose of shrinking the logfile? I
don't
> > get it.
> >
> > Thanks for your advice!
> >
> > - Joe Geretz -
> >
> >
>
by executing a logfile backup, but when I execute a Full or Incremental
backup, this option is disabled. I don't understand why. With the execution
of a successful backup, entries in the log prior to the point of backup
become irrelevant! I might need subsequent logfile transactions in the event
of a failure, but I won't need the logfile prior to the point of backup. So
why can't I shrink the logfile as part and parcel of the backup operation?
Must I always execute a separate logfile backup prior to my Full /
Incremental backup for the sole purpose of shrinking the logfile? I don't
get it.
Thanks for your advice!
- Joe Geretz -Joseph
If I understood you correctly you have to run LOG file backup with INIT
option to clear all entries prior the FULL backup database.
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> My database is set to Full Recovery model. I can shrink my transaction log
> by executing a logfile backup, but when I execute a Full or Incremental
> backup, this option is disabled. I don't understand why. With the
execution
> of a successful backup, entries in the log prior to the point of backup
> become irrelevant! I might need subsequent logfile transactions in the
event
> of a failure, but I won't need the logfile prior to the point of backup.
So
> why can't I shrink the logfile as part and parcel of the backup operation?
> Must I always execute a separate logfile backup prior to my Full /
> Incremental backup for the sole purpose of shrinking the logfile? I don't
> get it.
> Thanks for your advice!
> - Joe Geretz -
>|||Joe,
A full database backup or differential backup DO NOT truncate the log ( as
you have discovered.) This is by design... Here is a sample backup plan
Full1 Full2
log1 log2 log3 log4 log5,,,, etc
If we die are the log 5 backup, we can restore from FULL2, then restore all
of the logs and we are good to go... But what if the FULL2 backup tape is
missing or corrupted? You can begin by restoring the FULL1 backup, then
log1, log2, log3, log4. etc and still get up-to-the-minute recover without
loss of data... Log 4 contains ALL OF THE CHANGES since log3, Even when a
full or differential database backup was done between 3 and 4. The full,
and differential backups do NOT truncate the log SPECIFICALLY to give us the
opportunity to restore from a grandparent ( FULL1 ) or even older full or
differential backup and not lose data...
If you do not need the log backups, and wish to keep the log small, you
might wish to consider using the Simple recovery model for the database...
This means you will only be able to recover to the last full or differential
backup however.
Hope this helps..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> My database is set to Full Recovery model. I can shrink my transaction log
> by executing a logfile backup, but when I execute a Full or Incremental
> backup, this option is disabled. I don't understand why. With the
execution
> of a successful backup, entries in the log prior to the point of backup
> become irrelevant! I might need subsequent logfile transactions in the
event
> of a failure, but I won't need the logfile prior to the point of backup.
So
> why can't I shrink the logfile as part and parcel of the backup operation?
> Must I always execute a separate logfile backup prior to my Full /
> Incremental backup for the sole purpose of shrinking the logfile? I don't
> get it.
> Thanks for your advice!
> - Joe Geretz -
>|||Wayne
Why not just clean up with INIT option the LOG file after each FULL backup?
Why to blow the LOG file?
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eqD5jF9cEHA.3944@.tk2msftngp13.phx.gbl...
> Joe,
> A full database backup or differential backup DO NOT truncate the log ( as
> you have discovered.) This is by design... Here is a sample backup plan
> Full1 Full2
> log1 log2 log3 log4 log5,,,, etc
> If we die are the log 5 backup, we can restore from FULL2, then restore
all
> of the logs and we are good to go... But what if the FULL2 backup tape is
> missing or corrupted? You can begin by restoring the FULL1 backup, then
> log1, log2, log3, log4. etc and still get up-to-the-minute recover without
> loss of data... Log 4 contains ALL OF THE CHANGES since log3, Even when a
> full or differential database backup was done between 3 and 4. The full,
> and differential backups do NOT truncate the log SPECIFICALLY to give us
the
> opportunity to restore from a grandparent ( FULL1 ) or even older full or
> differential backup and not lose data...
> If you do not need the log backups, and wish to keep the log small, you
> might wish to consider using the Simple recovery model for the database...
> This means you will only be able to recover to the last full or
differential
> backup however.
> Hope this helps..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> > My database is set to Full Recovery model. I can shrink my transaction
log
> > by executing a logfile backup, but when I execute a Full or Incremental
> > backup, this option is disabled. I don't understand why. With the
> execution
> > of a successful backup, entries in the log prior to the point of backup
> > become irrelevant! I might need subsequent logfile transactions in the
> event
> > of a failure, but I won't need the logfile prior to the point of backup.
> So
> > why can't I shrink the logfile as part and parcel of the backup
operation?
> > Must I always execute a separate logfile backup prior to my Full /
> > Incremental backup for the sole purpose of shrinking the logfile? I
don't
> > get it.
> >
> > Thanks for your advice!
> >
> > - Joe Geretz -
> >
> >
>
Can't remove inactive entries from transaction log
My database is set to Full Recovery model. I can shrink my transaction log
by executing a logfile backup, but when I execute a Full or Incremental
backup, this option is disabled. I don't understand why. With the execution
of a successful backup, entries in the log prior to the point of backup
become irrelevant! I might need subsequent logfile transactions in the event
of a failure, but I won't need the logfile prior to the point of backup. So
why can't I shrink the logfile as part and parcel of the backup operation?
Must I always execute a separate logfile backup prior to my Full /
Incremental backup for the sole purpose of shrinking the logfile? I don't
get it.
Thanks for your advice!
- Joe Geretz -Joseph
If I understood you correctly you have to run LOG file backup with INIT
option to clear all entries prior the FULL backup database.
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> My database is set to Full Recovery model. I can shrink my transaction log
> by executing a logfile backup, but when I execute a Full or Incremental
> backup, this option is disabled. I don't understand why. With the
execution
> of a successful backup, entries in the log prior to the point of backup
> become irrelevant! I might need subsequent logfile transactions in the
event
> of a failure, but I won't need the logfile prior to the point of backup.
So
> why can't I shrink the logfile as part and parcel of the backup operation?
> Must I always execute a separate logfile backup prior to my Full /
> Incremental backup for the sole purpose of shrinking the logfile? I don't
> get it.
> Thanks for your advice!
> - Joe Geretz -
>|||Joe,
A full database backup or differential backup DO NOT truncate the log ( as
you have discovered.) This is by design... Here is a sample backup plan
Full1 Full2
log1 log2 log3 log4 log5,,,, etc
If we die are the log 5 backup, we can restore from FULL2, then restore all
of the logs and we are good to go... But what if the FULL2 backup tape is
missing or corrupted? You can begin by restoring the FULL1 backup, then
log1, log2, log3, log4. etc and still get up-to-the-minute recover without
loss of data... Log 4 contains ALL OF THE CHANGES since log3, Even when a
full or differential database backup was done between 3 and 4. The full,
and differential backups do NOT truncate the log SPECIFICALLY to give us the
opportunity to restore from a grandparent ( FULL1 ) or even older full or
differential backup and not lose data...
If you do not need the log backups, and wish to keep the log small, you
might wish to consider using the Simple recovery model for the database...
This means you will only be able to recover to the last full or differential
backup however.
Hope this helps..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> My database is set to Full Recovery model. I can shrink my transaction log
> by executing a logfile backup, but when I execute a Full or Incremental
> backup, this option is disabled. I don't understand why. With the
execution
> of a successful backup, entries in the log prior to the point of backup
> become irrelevant! I might need subsequent logfile transactions in the
event
> of a failure, but I won't need the logfile prior to the point of backup.
So
> why can't I shrink the logfile as part and parcel of the backup operation?
> Must I always execute a separate logfile backup prior to my Full /
> Incremental backup for the sole purpose of shrinking the logfile? I don't
> get it.
> Thanks for your advice!
> - Joe Geretz -
>|||Wayne
Why not just clean up with INIT option the LOG file after each FULL backup?
Why to blow the LOG file?
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eqD5jF9cEHA.3944@.tk2msftngp13.phx.gbl...
> Joe,
> A full database backup or differential backup DO NOT truncate the log ( as
> you have discovered.) This is by design... Here is a sample backup plan
> Full1 Full2
> log1 log2 log3 log4 log5,,,, etc
> If we die are the log 5 backup, we can restore from FULL2, then restore
all
> of the logs and we are good to go... But what if the FULL2 backup tape is
> missing or corrupted? You can begin by restoring the FULL1 backup, then
> log1, log2, log3, log4. etc and still get up-to-the-minute recover without
> loss of data... Log 4 contains ALL OF THE CHANGES since log3, Even when a
> full or differential database backup was done between 3 and 4. The full,
> and differential backups do NOT truncate the log SPECIFICALLY to give us
the
> opportunity to restore from a grandparent ( FULL1 ) or even older full or
> differential backup and not lose data...
> If you do not need the log backups, and wish to keep the log small, you
> might wish to consider using the Simple recovery model for the database...
> This means you will only be able to recover to the last full or
differential
> backup however.
> Hope this helps..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
log[vbcol=seagreen]
> execution
> event
> So
operation?[vbcol=seagreen]
don't[vbcol=seagreen]
>
by executing a logfile backup, but when I execute a Full or Incremental
backup, this option is disabled. I don't understand why. With the execution
of a successful backup, entries in the log prior to the point of backup
become irrelevant! I might need subsequent logfile transactions in the event
of a failure, but I won't need the logfile prior to the point of backup. So
why can't I shrink the logfile as part and parcel of the backup operation?
Must I always execute a separate logfile backup prior to my Full /
Incremental backup for the sole purpose of shrinking the logfile? I don't
get it.
Thanks for your advice!
- Joe Geretz -Joseph
If I understood you correctly you have to run LOG file backup with INIT
option to clear all entries prior the FULL backup database.
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> My database is set to Full Recovery model. I can shrink my transaction log
> by executing a logfile backup, but when I execute a Full or Incremental
> backup, this option is disabled. I don't understand why. With the
execution
> of a successful backup, entries in the log prior to the point of backup
> become irrelevant! I might need subsequent logfile transactions in the
event
> of a failure, but I won't need the logfile prior to the point of backup.
So
> why can't I shrink the logfile as part and parcel of the backup operation?
> Must I always execute a separate logfile backup prior to my Full /
> Incremental backup for the sole purpose of shrinking the logfile? I don't
> get it.
> Thanks for your advice!
> - Joe Geretz -
>|||Joe,
A full database backup or differential backup DO NOT truncate the log ( as
you have discovered.) This is by design... Here is a sample backup plan
Full1 Full2
log1 log2 log3 log4 log5,,,, etc
If we die are the log 5 backup, we can restore from FULL2, then restore all
of the logs and we are good to go... But what if the FULL2 backup tape is
missing or corrupted? You can begin by restoring the FULL1 backup, then
log1, log2, log3, log4. etc and still get up-to-the-minute recover without
loss of data... Log 4 contains ALL OF THE CHANGES since log3, Even when a
full or differential database backup was done between 3 and 4. The full,
and differential backups do NOT truncate the log SPECIFICALLY to give us the
opportunity to restore from a grandparent ( FULL1 ) or even older full or
differential backup and not lose data...
If you do not need the log backups, and wish to keep the log small, you
might wish to consider using the Simple recovery model for the database...
This means you will only be able to recover to the last full or differential
backup however.
Hope this helps..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
> My database is set to Full Recovery model. I can shrink my transaction log
> by executing a logfile backup, but when I execute a Full or Incremental
> backup, this option is disabled. I don't understand why. With the
execution
> of a successful backup, entries in the log prior to the point of backup
> become irrelevant! I might need subsequent logfile transactions in the
event
> of a failure, but I won't need the logfile prior to the point of backup.
So
> why can't I shrink the logfile as part and parcel of the backup operation?
> Must I always execute a separate logfile backup prior to my Full /
> Incremental backup for the sole purpose of shrinking the logfile? I don't
> get it.
> Thanks for your advice!
> - Joe Geretz -
>|||Wayne
Why not just clean up with INIT option the LOG file after each FULL backup?
Why to blow the LOG file?
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:eqD5jF9cEHA.3944@.tk2msftngp13.phx.gbl...
> Joe,
> A full database backup or differential backup DO NOT truncate the log ( as
> you have discovered.) This is by design... Here is a sample backup plan
> Full1 Full2
> log1 log2 log3 log4 log5,,,, etc
> If we die are the log 5 backup, we can restore from FULL2, then restore
all
> of the logs and we are good to go... But what if the FULL2 backup tape is
> missing or corrupted? You can begin by restoring the FULL1 backup, then
> log1, log2, log3, log4. etc and still get up-to-the-minute recover without
> loss of data... Log 4 contains ALL OF THE CHANGES since log3, Even when a
> full or differential database backup was done between 3 and 4. The full,
> and differential backups do NOT truncate the log SPECIFICALLY to give us
the
> opportunity to restore from a grandparent ( FULL1 ) or even older full or
> differential backup and not lose data...
> If you do not need the log backups, and wish to keep the log small, you
> might wish to consider using the Simple recovery model for the database...
> This means you will only be able to recover to the last full or
differential
> backup however.
> Hope this helps..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Joseph Geretz" <jgeretz@.nospam.com> wrote in message
> news:Ol669krcEHA.2384@.TK2MSFTNGP09.phx.gbl...
log[vbcol=seagreen]
> execution
> event
> So
operation?[vbcol=seagreen]
don't[vbcol=seagreen]
>
Subscribe to:
Posts (Atom)