Showing posts with label transactional. Show all posts
Showing posts with label transactional. Show all posts

Tuesday, March 27, 2012

Archiving data

You could possibly use transactional replication for this.
All the tables would be in the same publication and
relationships may also be registered there. Foreign keys
would be marked as Yes (Not for Replication). You'd have
to ensure that deletes are not replicated (using None for
the replication command).
Initially I mentioned 'possibly' - this is because there
may be some deletes that you really want to be replicated -
it all depends on how your system is set up. EG on one
database I worked on, there were no deletes allowed -
updates of a bit flag would effectively remove the record
from the user's vision. If your system is like this then
transactional would be ok. If not, then DTS, or snapshot
replication to append records could be used before the
deletes take place.
HTH,
Paul Ibison
I agree with Paul. I would incorporate the business logic for deletes in
custom stored procedures.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:17eb01c46f48$46da5a20$a301280a@.phx.gbl...
> You could possibly use transactional replication for this.
> All the tables would be in the same publication and
> relationships may also be registered there. Foreign keys
> would be marked as Yes (Not for Replication). You'd have
> to ensure that deletes are not replicated (using None for
> the replication command).
> Initially I mentioned 'possibly' - this is because there
> may be some deletes that you really want to be replicated -
> it all depends on how your system is set up. EG on one
> database I worked on, there were no deletes allowed -
> updates of a bit flag would effectively remove the record
> from the user's vision. If your system is like this then
> transactional would be ok. If not, then DTS, or snapshot
> replication to append records could be used before the
> deletes take place.
> HTH,
> Paul Ibison

Tuesday, March 20, 2012

Applying SP4 on Replicated databases

Hi,
We have transactional replication with 30 subscribers. We are planning to
upgrade to sp4 from sp3a. Publisher and distributor are in the same server.
So is there any order(sequence) like first we have to upgrade publisher and
then subscriber...
Is there any known issues/impact on publisher or subscriber.
Thanks in advance for your help.
Thanks
Prabhu
The rule is
Local Distributor - upgrade the publisher/distributor first then the
subscribers
Remote Distributor - upgrade the distributor, then the publisher, and
finally the subscriber(s).
"Prabhu" <Prabhu@.discussions.microsoft.com> wrote in message
news:B7770777-C2B2-4E30-9F13-354A18A3666E@.microsoft.com...
> Hi,
> We have transactional replication with 30 subscribers. We are planning to
> upgrade to sp4 from sp3a. Publisher and distributor are in the same
> server.
> So is there any order(sequence) like first we have to upgrade publisher
> and
> then subscriber...
> Is there any known issues/impact on publisher or subscriber.
> Thanks in advance for your help.
> Thanks
> Prabhu
>
|||Thanks cotter,
So we don't need to worry about the subscriber type, whether its read-only
or updatable subscriber. Am i right ? or is there any difference for these
types.
Thanks
Prabhu
"Hilary Cotter" wrote:

> The rule is
> Local Distributor - upgrade the publisher/distributor first then the
> subscribers
> Remote Distributor - upgrade the distributor, then the publisher, and
> finally the subscriber(s).
> "Prabhu" <Prabhu@.discussions.microsoft.com> wrote in message
> news:B7770777-C2B2-4E30-9F13-354A18A3666E@.microsoft.com...
>
>
|||Yes you don't have to worry about the subscribers. Just do them last.
I always shut down the SQL Server agents on the boxes before doing the
upgrades. You will need to notify your users that you are doing upgrades so
you can kick them off.
Hilary
"Prabhu" <Prabhu@.discussions.microsoft.com> wrote in message
news:EC578700-3B73-4C38-9255-4FA97C79A7B4@.microsoft.com...[vbcol=seagreen]
> Thanks cotter,
> So we don't need to worry about the subscriber type, whether its
> read-only
> or updatable subscriber. Am i right ? or is there any difference for these
> types.
> Thanks
> Prabhu
>
>
> "Hilary Cotter" wrote:

Monday, March 19, 2012

Applying DBCC DBREINDEX on a database that is part of Transaction Replication

I am about to apply DBCC DBREINDEX to a large database that is part of transactional replication and synchronised every 3 minutes. What are the likely implication and what precautions I must take.

Thanks in advance

Regards

R Suresh

Logreader will not replicate the index rebuild operation. Also if you use SQL 2005, I recommend you to use ALTER INDEX to rebuild index because DBCC DBREINDEX is a deprecated feature.

Of course, you need to do some experiment to see the performance impact if you do it frequently.

Peng

Applying DBCC DBREINDEX on a database that is part of Transaction Replication

I am about to apply DBCC DBREINDEX to a large database that is part of transactional replication and synchronised every 3 minutes. What are the likely implication and what precautions I must take.

Thanks in advance

Regards

R Suresh

Logreader will not replicate the index rebuild operation. Also if you use SQL 2005, I recommend you to use ALTER INDEX to rebuild index because DBCC DBREINDEX is a deprecated feature.

Of course, you need to do some experiment to see the performance impact if you do it frequently.

Peng

Thursday, March 8, 2012

appling DTS custom transformation to replication problem (Urgent)

Hi all,
In my production environment, there is a source database that replicates
data to another server (using transactional replication).
Because of some upgrade needs, I need to change the subscriber database to
store Unicode. As a result, I want to customize the replication such that our
Big5 data in source database can be converted to UNICODE automatically during
replication.
Firstly, I want to know whether applying DTS custom transformation in
replication can solve my problem. Is there any better methods?
In addition, how can I configure DTS custom transforamtion.?
I have tried using Define Transformation of Published Data Wizard but error
occurs at the step of adding task of creating the DTS package. The error is
"SQL Server Enterprise Manager cannot complete this operation".
I also try to use DTS designer to create the package. But I cannot select
the package created bt DTS designer when I create a transformable
subscription.
Please help me
Thanks
"kazom" wrote:

> Hi all,
> In my production environment, there is a source database that replicates
> data to another server (using transactional replication).
> Because of some upgrade needs, I need to change the subscriber database to
> store Unicode. As a result, I want to customize the replication such that our
> Big5 data in source database can be converted to UNICODE automatically during
> replication.
> Firstly, I want to know whether applying DTS custom transformation in
> replication can solve my problem. Is there any better methods?
> In addition, how can I configure DTS custom transforamtion.?
> I have tried using Define Transformation of Published Data Wizard but error
> occurs at the step of adding task of creating the DTS package. The error is
> "SQL Server Enterprise Manager cannot complete this operation".
> I also try to use DTS designer to create the package. But I cannot select
> the package created bt DTS designer when I create a transformable
> subscription.
> Please help me
> Thanks
>
Hi all,
Let me make the question be more specific.
I just follow this document to configure the DTS custom transformation
replication.
But error occurs after step 11 of the part Define a DTS Package for the
Transformation
The error is:
SQL Server Enterprise Manager could not complete this operation
Both the publisher and subscripter is at the same server but different
database
The server is SQL Server 2000 service pack 4
Please help me. I really need your professional help
This is very urgent
Thanks