Can The SqlServer Log/LogArchives be used for reporting a change/audit history of important database fields?
Cand the Logs be used to lookup when and how often certain fields were/are changed...
Cnn the log be used as an Audit control to prove to the customer that he changed his oun fields by date and time? And Provide before and after images of changes by date and time...
You might want to look into the products offered by Lumigent.
(www.lumigent.com)
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"SqlBob" <rplewis@.mindspring.com> wrote in message
news:855EDBB3-1857-456F-91BD-DB51947B0BE4@.microsoft.com...
Can The SqlServer Log/LogArchives be used for reporting a change/audit
history of important database fields?
Cand the Logs be used to lookup when and how often certain fields were/are
changed...
Cnn the log be used as an Audit control to prove to the customer that he
changed his oun fields by date and time? And Provide before and after
images of changes by date and time...
Showing posts with label log. Show all posts
Showing posts with label log. Show all posts
Saturday, February 25, 2012
Report and Audit Controls from Log??
Can The SqlServer Log/LogArchives be used for reporting a change/audit histo
ry of important database fields?
Cand the Logs be used to lookup when and how often certain fields were/are c
hanged...
Cnn the log be used as an Audit control to prove to the customer that he cha
nged his oun fields by date and time? And Provide before and after images
of changes by date and time...You might want to look into the products offered by Lumigent.
(www.lumigent.com)
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"SqlBob" <rplewis@.mindspring.com> wrote in message
news:855EDBB3-1857-456F-91BD-DB51947B0BE4@.microsoft.com...
Can The SqlServer Log/LogArchives be used for reporting a change/audit
history of important database fields?
Cand the Logs be used to lookup when and how often certain fields were/are
changed...
Cnn the log be used as an Audit control to prove to the customer that he
changed his oun fields by date and time? And Provide before and after
images of changes by date and time...
ry of important database fields?
Cand the Logs be used to lookup when and how often certain fields were/are c
hanged...
Cnn the log be used as an Audit control to prove to the customer that he cha
nged his oun fields by date and time? And Provide before and after images
of changes by date and time...You might want to look into the products offered by Lumigent.
(www.lumigent.com)
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"SqlBob" <rplewis@.mindspring.com> wrote in message
news:855EDBB3-1857-456F-91BD-DB51947B0BE4@.microsoft.com...
Can The SqlServer Log/LogArchives be used for reporting a change/audit
history of important database fields?
Cand the Logs be used to lookup when and how often certain fields were/are
changed...
Cnn the log be used as an Audit control to prove to the customer that he
changed his oun fields by date and time? And Provide before and after
images of changes by date and time...
Tuesday, February 21, 2012
reply
I am not using the SA account when I log in using windows authentication it seems to pick up my domain and active directory ID which is "us\app1dxd" it appears greyed out as well as the password on the login screen so you can't change it.
If you go into the management studio and right click on the server name in the left hand pane go to properties security the radio button for sql server and Windows authentication mode is selected.
It is normal because the BOL says if you install SQL Server with Windows Authentication the sa account gets disabled, the account remains disabled even when you change to mixed authentication you have to enable the account after changing to mixed authentication.
http://msdn2.microsoft.com/en-us/library/ms144284.aspx
replication-log reader, dbcc reindex and transaction log backup.
We are using SQL 2K standard with sp4 and Push replication. Let me explain
my situation here first.
We have a weekly dbcc reindex happen at 3:05 am on Sunday morning and
finished successfully at 3:42 am. The replication - log reader started
issuing error in the log reader agent history, "The process could not execute
'sp_replcmds' on serverA..." starting at 3:14 am and being recurred every 6
minutes until 3:44 am. At that time, this error became red and stopped. Our
hourly transaction backup job kicked in at 3:45 am and took 10 minutes to
finish and normally it would take less than 20 seconds to complete. Later in
the morning, someone reported that they don't see any changed data replicated
to the subscriber server and indeed it wasn't working. All these activities
were on the same server, publishing server.
I have some questions regarding replication in this siutation.
1. Will the changes make by dbcc reindex be replicated to the subscriber
server? If so, will this explain the situation described above. if this is
the case, what should I do to minimize the effect of dbcc reindex to
log-reader? It is hard to believe someone would get up at 3:00 am Sunday
morning and making data changes which triggered the transactional
replication.
2. The weekend prior, with the same setup except no transaction log
backup (at that time, the backup mode was still set to simple), we didn't
encounter the 'sp_replcmds' error in the log reader agent. Is there any
relationship between the transaction log backup proces and log reader process
or they run independ of each other?
3. Why does the 'could not execute sp_replcmds' error occur and how to cure
this problem? Until this is solved, replication is down.
4. Is there a way I can schedule the Log Reader agent to stop and start at
a specific time?
wingman
1. Replication moves insert, update, and delete statements. That is all.
No other operation is moved through the replication engine in SQL Server
2000. If you reindex, it only occurs locally. When you reindex, you write
a huge volume of changes into the transaction log which does impact the
response time on the log reader since it has to scan through all of that
data. A change doesn't trigger replication. Replication constantly polls
for changes which have occured and moves anything that it finds.
2. There is not relationship between the log reader and a transaction log
backup. Replication only picks up transactions which have been committed.
A transaction log backup will not remove a committed transaction from the
log until it has been successfully written to the distribution database.
So, the Log Reader can have an impact on the size of the transaction log,
because if the log reader isn't running or can't transfer transactions to
the distribution database for some reason, then the tran log continues to
grow.
3. Is the error continuing to be thrown or was it a transient issue occuring
during the reindex operation?
4. The Log Reader agent is just a job. You can start it and stop it
whenever you want. You can even create a job to stop and start it at
particular times.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:555110A9-6925-4308-8572-F5E2653521AA@.microsoft.com...
> We are using SQL 2K standard with sp4 and Push replication. Let me
> explain
> my situation here first.
> We have a weekly dbcc reindex happen at 3:05 am on Sunday morning and
> finished successfully at 3:42 am. The replication - log reader started
> issuing error in the log reader agent history, "The process could not
> execute
> 'sp_replcmds' on serverA..." starting at 3:14 am and being recurred every
> 6
> minutes until 3:44 am. At that time, this error became red and stopped.
> Our
> hourly transaction backup job kicked in at 3:45 am and took 10 minutes to
> finish and normally it would take less than 20 seconds to complete. Later
> in
> the morning, someone reported that they don't see any changed data
> replicated
> to the subscriber server and indeed it wasn't working. All these
> activities
> were on the same server, publishing server.
> I have some questions regarding replication in this siutation.
> 1. Will the changes make by dbcc reindex be replicated to the subscriber
> server? If so, will this explain the situation described above. if this
> is
> the case, what should I do to minimize the effect of dbcc reindex to
> log-reader? It is hard to believe someone would get up at 3:00 am Sunday
> morning and making data changes which triggered the transactional
> replication.
> 2. The weekend prior, with the same setup except no transaction log
> backup (at that time, the backup mode was still set to simple), we didn't
> encounter the 'sp_replcmds' error in the log reader agent. Is there any
> relationship between the transaction log backup proces and log reader
> process
> or they run independ of each other?
> 3. Why does the 'could not execute sp_replcmds' error occur and how to
> cure
> this problem? Until this is solved, replication is down.
> 4. Is there a way I can schedule the Log Reader agent to stop and start
> at
> a specific time?
> wingman
>
my situation here first.
We have a weekly dbcc reindex happen at 3:05 am on Sunday morning and
finished successfully at 3:42 am. The replication - log reader started
issuing error in the log reader agent history, "The process could not execute
'sp_replcmds' on serverA..." starting at 3:14 am and being recurred every 6
minutes until 3:44 am. At that time, this error became red and stopped. Our
hourly transaction backup job kicked in at 3:45 am and took 10 minutes to
finish and normally it would take less than 20 seconds to complete. Later in
the morning, someone reported that they don't see any changed data replicated
to the subscriber server and indeed it wasn't working. All these activities
were on the same server, publishing server.
I have some questions regarding replication in this siutation.
1. Will the changes make by dbcc reindex be replicated to the subscriber
server? If so, will this explain the situation described above. if this is
the case, what should I do to minimize the effect of dbcc reindex to
log-reader? It is hard to believe someone would get up at 3:00 am Sunday
morning and making data changes which triggered the transactional
replication.
2. The weekend prior, with the same setup except no transaction log
backup (at that time, the backup mode was still set to simple), we didn't
encounter the 'sp_replcmds' error in the log reader agent. Is there any
relationship between the transaction log backup proces and log reader process
or they run independ of each other?
3. Why does the 'could not execute sp_replcmds' error occur and how to cure
this problem? Until this is solved, replication is down.
4. Is there a way I can schedule the Log Reader agent to stop and start at
a specific time?
wingman
1. Replication moves insert, update, and delete statements. That is all.
No other operation is moved through the replication engine in SQL Server
2000. If you reindex, it only occurs locally. When you reindex, you write
a huge volume of changes into the transaction log which does impact the
response time on the log reader since it has to scan through all of that
data. A change doesn't trigger replication. Replication constantly polls
for changes which have occured and moves anything that it finds.
2. There is not relationship between the log reader and a transaction log
backup. Replication only picks up transactions which have been committed.
A transaction log backup will not remove a committed transaction from the
log until it has been successfully written to the distribution database.
So, the Log Reader can have an impact on the size of the transaction log,
because if the log reader isn't running or can't transfer transactions to
the distribution database for some reason, then the tran log continues to
grow.
3. Is the error continuing to be thrown or was it a transient issue occuring
during the reindex operation?
4. The Log Reader agent is just a job. You can start it and stop it
whenever you want. You can even create a job to stop and start it at
particular times.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:555110A9-6925-4308-8572-F5E2653521AA@.microsoft.com...
> We are using SQL 2K standard with sp4 and Push replication. Let me
> explain
> my situation here first.
> We have a weekly dbcc reindex happen at 3:05 am on Sunday morning and
> finished successfully at 3:42 am. The replication - log reader started
> issuing error in the log reader agent history, "The process could not
> execute
> 'sp_replcmds' on serverA..." starting at 3:14 am and being recurred every
> 6
> minutes until 3:44 am. At that time, this error became red and stopped.
> Our
> hourly transaction backup job kicked in at 3:45 am and took 10 minutes to
> finish and normally it would take less than 20 seconds to complete. Later
> in
> the morning, someone reported that they don't see any changed data
> replicated
> to the subscriber server and indeed it wasn't working. All these
> activities
> were on the same server, publishing server.
> I have some questions regarding replication in this siutation.
> 1. Will the changes make by dbcc reindex be replicated to the subscriber
> server? If so, will this explain the situation described above. if this
> is
> the case, what should I do to minimize the effect of dbcc reindex to
> log-reader? It is hard to believe someone would get up at 3:00 am Sunday
> morning and making data changes which triggered the transactional
> replication.
> 2. The weekend prior, with the same setup except no transaction log
> backup (at that time, the backup mode was still set to simple), we didn't
> encounter the 'sp_replcmds' error in the log reader agent. Is there any
> relationship between the transaction log backup proces and log reader
> process
> or they run independ of each other?
> 3. Why does the 'could not execute sp_replcmds' error occur and how to
> cure
> this problem? Until this is solved, replication is down.
> 4. Is there a way I can schedule the Log Reader agent to stop and start
> at
> a specific time?
> wingman
>
Replication\Log Shipping\Geogrpahical distributed cluster(W2003)
Friends,
have any one set up above said techs between datacenters (2 or 4, more).
please evaluate pros and cons.
Thanks,
Yes, to all of the above. How many hours do you have to read pages of
stuff? That is NOT an easy question and it doesn't have an answer that can
be laid out in a small set of bullet points. Each technology does
dramatically different things and maintains data in dramatically different
ways. It would help to have an idea of exactly what you are trying to
accomplish and what your physical infrastructure looks like.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"John" <John@.discussions.microsoft.com> wrote in message
news:10869D2C-491A-4B3B-AFF3-D55FA5A5220F@.microsoft.com...
> Friends,
> have any one set up above said techs between datacenters (2 or 4, more).
> please evaluate pros and cons.
> Thanks,
|||Log shipping does the entire database. For large databases it can be
unwieldy and difficult to get started again after a hiccup. The standby
server must go offline when the logs are being applied. In general log
shipping is not considered to be scalable, although I consulted for a very
large online brokerage who uses it exclusively and are very happy with it.
There is no automatic failover with log shipping.
Replication is generally a good choice when you want to
mirror/replicate/copy a subset of your data from one server to one or more
servers. Log shipping and clustering are not scalable to large numbers of
subscribers/standby servers/nodes. Replication does require a higher skill
set than log shipping.
Clustering, especially geospatial clustering requires expensive hardware,
and a significant skill set. It will replicate/mirror a database(s). It is a
good technology to provide high availability and other than database
mirroring it is the only technology to do automatic failover.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"John" <John@.discussions.microsoft.com> wrote in message
news:10869D2C-491A-4B3B-AFF3-D55FA5A5220F@.microsoft.com...
> Friends,
> have any one set up above said techs between datacenters (2 or 4, more).
> please evaluate pros and cons.
> Thanks,
have any one set up above said techs between datacenters (2 or 4, more).
please evaluate pros and cons.
Thanks,
Yes, to all of the above. How many hours do you have to read pages of
stuff? That is NOT an easy question and it doesn't have an answer that can
be laid out in a small set of bullet points. Each technology does
dramatically different things and maintains data in dramatically different
ways. It would help to have an idea of exactly what you are trying to
accomplish and what your physical infrastructure looks like.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"John" <John@.discussions.microsoft.com> wrote in message
news:10869D2C-491A-4B3B-AFF3-D55FA5A5220F@.microsoft.com...
> Friends,
> have any one set up above said techs between datacenters (2 or 4, more).
> please evaluate pros and cons.
> Thanks,
|||Log shipping does the entire database. For large databases it can be
unwieldy and difficult to get started again after a hiccup. The standby
server must go offline when the logs are being applied. In general log
shipping is not considered to be scalable, although I consulted for a very
large online brokerage who uses it exclusively and are very happy with it.
There is no automatic failover with log shipping.
Replication is generally a good choice when you want to
mirror/replicate/copy a subset of your data from one server to one or more
servers. Log shipping and clustering are not scalable to large numbers of
subscribers/standby servers/nodes. Replication does require a higher skill
set than log shipping.
Clustering, especially geospatial clustering requires expensive hardware,
and a significant skill set. It will replicate/mirror a database(s). It is a
good technology to provide high availability and other than database
mirroring it is the only technology to do automatic failover.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"John" <John@.discussions.microsoft.com> wrote in message
news:10869D2C-491A-4B3B-AFF3-D55FA5A5220F@.microsoft.com...
> Friends,
> have any one set up above said techs between datacenters (2 or 4, more).
> please evaluate pros and cons.
> Thanks,
replication, mirroring and log ship
dear all,
I have a case.
I have 1 production server and wanto to add 1 more server.
my production server is using sql 2000 stnd edition.
I want to have an indentical database from my production server.
the problem is my second server is using sql 2005 stnd edition.
I have try to use replication but because the my production database didn't have relationship on the database so I can't use transaction replication, I can't use mirroring and log ship too because the sql use the different version.
any idea or suggestion will be great....
regards,
-dedys
Transactional replication should work fine as it supports replicating between servers within two versions of each other.
Regards,
Matt Hollingsworth
SQL Server High Availability
|||The only thing that would prevent you from using transactional replication is if you have tables that do not have primary keys.
As far as log shipping goes. You can configure log shipping from SQL Server 2000 to SQL Server 2005, because 2000 backups can be restored to 2005. You can not configure it the other way around.
|||dear sir,
I already try to configure log ship on my server.
my primary server is on sql2000 and the secondary server is on sql 2005.
I find that on sql 2000 can't see the sql 2005.
do you have documentation regarding this. a web link ?
thanks
-dedys
|||You can't connect to and manage a 2005 instance from within Enterprise Manager. You can go the other way. Log shipping is nothing more than configuring jobs to backup the tran log, copy it to the secondary, and restore it on a recurring basis. From within Management Studio on 2005, you can point and click through the GUI and setup log shipping from 2000 to 2005. You can also just create three jobs manually and accomplish the same thing. I'm not sure what documentation you are looking for. The 2005 Books Online have step-by-step procedures for setting up log shipping.|||hi,
I have tries to set log shipping from 2000 to 2005 but it seem can't be done.
example : Server A is 2005 and B is 2000
I'm using management studio from A and register B. but when I right click on the database B, I can't find log shipping.
so I can't configure log shipping from 2000 to 2005.
if you know how to set it. could you share it with me.
I also try to do it manually like you said. using 3 simple step.
step 1 and 2 is done. I have difficulties with step 3. that is restoring the transaction log.
do you know how to restore transaction log more that 2 files at the same time or the name is keep on changing ?
please advice
-dedys
|||You can't restore more than 1 tran log simultaneously. Just like you can't restore more than one of any backup at the same time to the same database. You have to restore 1 log and then the next and then the next etc.|||hi mr michael,
I have tries but I still got problem.
the step that did,
restore fullbackup to other server.
then restore the transaction log one by one and at the last transaction log with recovery option.
that's part is ok.
but when I want add more transaction log, there is an error that said :
Msg 3117, Level 16, State 4, Line 1
The log or differential backup cannot be restored because no files are ready to rollforward.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
please advice
|||You have to restore all transaction logs using the NORECOVERY option. As soon as you recover the database, you can no longer restore tran logs.replication, mirroring and log ship
dear all,
I have a case.
I have 1 production server and wanto to add 1 more server.
my production server is using sql 2000 stnd edition.
I want to have an indentical database from my production server.
the problem is my second server is using sql 2005 stnd edition.
I have try to use replication but because the my production database didn't have relationship on the database so I can't use transaction replication, I can't use mirroring and log ship too because the sql use the different version.
any idea or suggestion will be great....
regards,
-dedys
Transactional replication should work fine as it supports replicating between servers within two versions of each other.
Regards,
Matt Hollingsworth
SQL Server High Availability
|||The only thing that would prevent you from using transactional replication is if you have tables that do not have primary keys.
As far as log shipping goes. You can configure log shipping from SQL Server 2000 to SQL Server 2005, because 2000 backups can be restored to 2005. You can not configure it the other way around.
|||dear sir,
I already try to configure log ship on my server.
my primary server is on sql2000 and the secondary server is on sql 2005.
I find that on sql 2000 can't see the sql 2005.
do you have documentation regarding this. a web link ?
thanks
-dedys
|||You can't connect to and manage a 2005 instance from within Enterprise Manager. You can go the other way. Log shipping is nothing more than configuring jobs to backup the tran log, copy it to the secondary, and restore it on a recurring basis. From within Management Studio on 2005, you can point and click through the GUI and setup log shipping from 2000 to 2005. You can also just create three jobs manually and accomplish the same thing. I'm not sure what documentation you are looking for. The 2005 Books Online have step-by-step procedures for setting up log shipping.|||hi,
I have tries to set log shipping from 2000 to 2005 but it seem can't be done.
example : Server A is 2005 and B is 2000
I'm using management studio from A and register B. but when I right click on the database B, I can't find log shipping.
so I can't configure log shipping from 2000 to 2005.
if you know how to set it. could you share it with me.
I also try to do it manually like you said. using 3 simple step.
step 1 and 2 is done. I have difficulties with step 3. that is restoring the transaction log.
do you know how to restore transaction log more that 2 files at the same time or the name is keep on changing ?
please advice
-dedys
|||You can't restore more than 1 tran log simultaneously. Just like you can't restore more than one of any backup at the same time to the same database. You have to restore 1 log and then the next and then the next etc.|||hi mr michael,
I have tries but I still got problem.
the step that did,
restore fullbackup to other server.
then restore the transaction log one by one and at the last transaction log with recovery option.
that's part is ok.
but when I want add more transaction log, there is an error that said :
Msg 3117, Level 16, State 4, Line 1
The log or differential backup cannot be restored because no files are ready to rollforward.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
please advice
|||You have to restore all transaction logs using the NORECOVERY option. As soon as you recover the database, you can no longer restore tran logs.replication, mirroring and log ship
dear all,
I have a case.
I have 1 production server and wanto to add 1 more server.
my production server is using sql 2000 stnd edition.
I want to have an indentical database from my production server.
the problem is my second server is using sql 2005 stnd edition.
I have try to use replication but because the my production database didn't have relationship on the database so I can't use transaction replication, I can't use mirroring and log ship too because the sql use the different version.
any idea or suggestion will be great....
regards,
-dedys
Transactional replication should work fine as it supports replicating between servers within two versions of each other.
Regards,
Matt Hollingsworth
SQL Server High Availability
|||The only thing that would prevent you from using transactional replication is if you have tables that do not have primary keys.
As far as log shipping goes. You can configure log shipping from SQL Server 2000 to SQL Server 2005, because 2000 backups can be restored to 2005. You can not configure it the other way around.
|||dear sir,
I already try to configure log ship on my server.
my primary server is on sql2000 and the secondary server is on sql 2005.
I find that on sql 2000 can't see the sql 2005.
do you have documentation regarding this. a web link ?
thanks
-dedys
|||You can't connect to and manage a 2005 instance from within Enterprise Manager. You can go the other way. Log shipping is nothing more than configuring jobs to backup the tran log, copy it to the secondary, and restore it on a recurring basis. From within Management Studio on 2005, you can point and click through the GUI and setup log shipping from 2000 to 2005. You can also just create three jobs manually and accomplish the same thing. I'm not sure what documentation you are looking for. The 2005 Books Online have step-by-step procedures for setting up log shipping.|||hi,
I have tries to set log shipping from 2000 to 2005 but it seem can't be done.
example : Server A is 2005 and B is 2000
I'm using management studio from A and register B. but when I right click on the database B, I can't find log shipping.
so I can't configure log shipping from 2000 to 2005.
if you know how to set it. could you share it with me.
I also try to do it manually like you said. using 3 simple step.
step 1 and 2 is done. I have difficulties with step 3. that is restoring the transaction log.
do you know how to restore transaction log more that 2 files at the same time or the name is keep on changing ?
please advice
-dedys
|||You can't restore more than 1 tran log simultaneously. Just like you can't restore more than one of any backup at the same time to the same database. You have to restore 1 log and then the next and then the next etc.|||hi mr michael,
I have tries but I still got problem.
the step that did,
restore fullbackup to other server.
then restore the transaction log one by one and at the last transaction log with recovery option.
that's part is ok.
but when I want add more transaction log, there is an error that said :
Msg 3117, Level 16, State 4, Line 1
The log or differential backup cannot be restored because no files are ready to rollforward.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
please advice
|||You have to restore all transaction logs using the NORECOVERY option. As soon as you recover the database, you can no longer restore tran logs.Replication, Log Shipping and Backup
Hi there all.
In my installation there is a main online DB which replicates
some of its data with transactional replication to another DB.
I also use log shipping so that there is always a stand by server
for my main DB.
1. With this installation, can I still keep backing up my log every
half an hour as I used to before log shipping? I would feel much more
safer if I could. Is there a way to do it?
2. Log shipping uses log backups, so it truncate the log every time
it posts changes to the standby server, is that correct?
Thank you all in advance.
George
1) yes, but you might want to back it up more frequently as replication
writes to the log too - not much, but some.
2) it doesn't truncate, but it does back it up.
"George Nentidis" <gnentid@.msn.com> wrote in message
news:%23rnPmmQ6FHA.3760@.TK2MSFTNGP14.phx.gbl...
> Hi there all.
> In my installation there is a main online DB which replicates
> some of its data with transactional replication to another DB.
> I also use log shipping so that there is always a stand by server
> for my main DB.
> 1. With this installation, can I still keep backing up my log every
> half an hour as I used to before log shipping? I would feel much more
> safer if I could. Is there a way to do it?
> 2. Log shipping uses log backups, so it truncate the log every time
> it posts changes to the standby server, is that correct?
> Thank you all in advance.
> George
In my installation there is a main online DB which replicates
some of its data with transactional replication to another DB.
I also use log shipping so that there is always a stand by server
for my main DB.
1. With this installation, can I still keep backing up my log every
half an hour as I used to before log shipping? I would feel much more
safer if I could. Is there a way to do it?
2. Log shipping uses log backups, so it truncate the log every time
it posts changes to the standby server, is that correct?
Thank you all in advance.
George
1) yes, but you might want to back it up more frequently as replication
writes to the log too - not much, but some.
2) it doesn't truncate, but it does back it up.
"George Nentidis" <gnentid@.msn.com> wrote in message
news:%23rnPmmQ6FHA.3760@.TK2MSFTNGP14.phx.gbl...
> Hi there all.
> In my installation there is a main online DB which replicates
> some of its data with transactional replication to another DB.
> I also use log shipping so that there is always a stand by server
> for my main DB.
> 1. With this installation, can I still keep backing up my log every
> half an hour as I used to before log shipping? I would feel much more
> safer if I could. Is there a way to do it?
> 2. Log shipping uses log backups, so it truncate the log every time
> it posts changes to the standby server, is that correct?
> Thank you all in advance.
> George
Subscribe to:
Posts (Atom)