[Help] Snapshot replication & Full Text Indexing

Hi
I have setup snapshot replication in one of my sql database. The article
which i publish, has full text index enabled in the subscription db. So when
the initial snap shot is applied, i get a error message saying "cannot drop
index PK_<<table name>> because it enforces full text key. It really drives
me crazy.
Here are my questions
1. In the Artcile properties, page i specify, under the name conflict
section, leave the table un changed. Then why is it that sql server tries
to drop the table and recreate it.(i checked in the sch table, what ever
option i specify, it is adament, it wants to recreate the table).
2. Is there a way, to publish full text indexed tables, without the initial
snapshot failing ?
I am in "Developer in Distress" mode, can anyone help ?
Thank You
Shrinivas
1 & 2) this should work, could you post the schema of this problem table
here?
"shrini" <senor20@.hotmail.com> wrote in message
news:%23R4xv8vJEHA.620@.tk2msftngp13.phx.gbl...
> Hi
> I have setup snapshot replication in one of my sql database. The article
> which i publish, has full text index enabled in the subscription db. So
when
> the initial snap shot is applied, i get a error message saying "cannot
drop
> index PK_<<table name>> because it enforces full text key. It really
drives
> me crazy.
> Here are my questions
> 1. In the Artcile properties, page i specify, under the name conflict
> section, leave the table un changed. Then why is it that sql server tries
> to drop the table and recreate it.(i checked in the sch table, what ever
> option i specify, it is adament, it wants to recreate the table).
> 2. Is there a way, to publish full text indexed tables, without the
initial
> snapshot failing ?
> I am in "Developer in Distress" mode, can anyone help ?
> Thank You
> Shrinivas
>
|||Hi Hilary
I managed to work around this, by dropping the Full Text index before
applying the snap (by specifying sql in the snap shot tab of properties) and
recreating the index after the snap shot is created. I think this is the
possible way for doing this. Thanks for your reply.
Shrini
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:e3KduPFKEHA.2808@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> 1 & 2) this should work, could you post the schema of this problem table
> here?
> "shrini" <senor20@.hotmail.com> wrote in message
> news:%23R4xv8vJEHA.620@.tk2msftngp13.phx.gbl...
> when
> drop
> drives
tries
> initial
>

[Expired subscription clean up] job failing

Hi,

The "Expired subscription clean up" job at the distributor keeps failing with the following error. Any ideas what it could be?

Message
Executed as user: domain\servicesql. The Distributor has not been installed correctly. [SQLSTATE 42000] (Error 20036). The step failed.

Thanks,
Priyanga

I came accross the following link which provides a workaround to the problem.
Thanks Narayana!

http://vyaskn.tripod.com/sql_server_2005_expired_subscription_cleanup.htm

Cheers,
Priyanga

|||This is a bug in replication for the case where distributor is not configured as publisher, this bug has been fixed and will be available in SQL Server 2005 SP1.|||This did not fix the error, and I'm running SP2 on SQL Server 2005. Any other solutions available? THANKS!

[Expired subscription clean up] job failing

Hi,

The "Expired subscription clean up" job at the distributor keeps failing with the following error. Any ideas what it could be?

Message
Executed as user: domain\servicesql. The Distributor has not been installed correctly. [SQLSTATE 42000] (Error 20036). The step failed.

Thanks,
Priyanga

I came accross the following link which provides a workaround to the problem.
Thanks Narayana!

http://vyaskn.tripod.com/sql_server_2005_expired_subscription_cleanup.htm

Cheers,
Priyanga

|||This is a bug in replication for the case where distributor is not configured as publisher, this bug has been fixed and will be available in SQL Server 2005 SP1.|||This did not fix the error, and I'm running SP2 on SQL Server 2005. Any other solutions available? THANKS!

@TimeStamp on file delivery

Hi guru,
I am running into a problem where I have no solution. I have created weekly
SQL subscription and choose delivery method to File Share which is working
fine. My manager wants to have date on each published file. I have found on
MSDN that I could use @.Timestamp variable at the end of file name that will
insert the time but the problem is the format. The timestamp is inserted in
Year_Min_Date_random numbers. It is not inserting month. e.g I published one
report today at 2:05 the time stamp was 2007_05_13_120552. I don;t know why
it is inserting min not months. Is it a bug or is there any solution to that.
I appreciate your help
Thanks
SaeedThat's strange...
I just tried it and got
Test2007_04_15_170209.xml
... which is correct.
What is the locale (regional information) for the computer that is running
Reporting Services? Anything in the way the regional formats are being
applied to date and times that might explain this?
If you open a table in the ReportServer database using Management Studio and
look at the contents of a date column in a table (say, ModifiedDate in the
Catalog table), do the contents look correct to you?
And, this is probably a completely stupid possibility but... any chance the
server itself has the WRONG date and time set?
>L<
"SA" <SA@.discussions.microsoft.com> wrote in message
news:DA8C1BFB-AFE6-419D-BAF8-3E49AB668629@.microsoft.com...
> Hi guru,
> I am running into a problem where I have no solution. I have created
> weekly
> SQL subscription and choose delivery method to File Share which is working
> fine. My manager wants to have date on each published file. I have found
> on
> MSDN that I could use @.Timestamp variable at the end of file name that
> will
> insert the time but the problem is the format. The timestamp is inserted
> in
> Year_Min_Date_random numbers. It is not inserting month. e.g I published
> one
> report today at 2:05 the time stamp was 2007_05_13_120552. I don;t know
> why
> it is inserting min not months. Is it a bug or is there any solution to
> that.
> I appreciate your help
> Thanks
> Saeed

@loopback_detection

How do I determine if a subscription has loopback
detection enabled?
sp_helpsubscription publicationname and look for the value of
loopback_detection. A non zero value means its enabled.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:0f3e01c4a59a$3c36afa0$a601280a@.phx.gbl...
> How do I determine if a subscription has loopback
> detection enabled?