Consequences of changing subscription expiry date SQL Server 2000

Hi,
I'm running a merge publication on a SQL Server 2000 database with
several anonymous subscribers. I want to change the subscription
expiry from 14 to 28 days. Aside from larger logging tables, are
there any important consequences to doing this? In particular, do I
need to reinitialise the subscriptions before the change takes effect?
Many thanks
Alex
There will be slower syncs. Yes you need to reinitialize.
Hilary Cotter
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
<WombatDeath@.gmail.com> wrote in message
news:1173701986.327352.14330@.h3g2000cwc.googlegrou ps.com...
> Hi,
> I'm running a merge publication on a SQL Server 2000 database with
> several anonymous subscribers. I want to change the subscription
> expiry from 14 to 28 days. Aside from larger logging tables, are
> there any important consequences to doing this? In particular, do I
> need to reinitialise the subscriptions before the change takes effect?
> Many thanks
> Alex
>
|||Thanks Hilary. If I don't reinitialize the existing subscriptions
will they break, or will they just keep the old 14-day expiration time
until I get around to reinitializing them for other reasons?
Thanks
Alex

Connection string

hi. I have trying to load packages from SQL server using "load from SQL comman" and then programmatically changing the connection manager's certain properties(as this property has to be changed in run time.

It works fine when these packages are running from same database but when programmatically I am changing its initial catalogue to some other database, then this is not reflecting even after changing the initial catalogue. Its referring to database which these are created upon. If anyone has some idea please reply back

Is your catalog hardcoded somewhere in the package (like in a table name)?

I would suggest you open your package, try to change the connection string manually and then debug your package step by step.

HTH.

|||

thanks for your reply ,

Well yes the database name is getting added along with the table name.

is ther any way to place just table name or a way to remove the database name ?

Thanks,

|||

Could you give us more details? What component are you referring to? Is it OLE DB Source/Destination?

Most probably it can be fixed; just tell us what component has the catalog name hard-coded.

Thanks.

|||

Anshu nautiyal wrote:

thanks for your reply ,

Well yes the database name is getting added along with the table name.

is ther any way to place just table name or a way to remove the database name ?

Thanks,

That is your problem; make sure all sql statements in the package do not have the dabase name as they may be diffrent when you change the connection strings. Just edit the sql statements and remove the database part of the name.

|||

Anshu nautiyal wrote:

thanks for your reply ,

Well yes the database name is getting added along with the table name.

is ther any way to place just table name or a way to remove the database name ?

Thanks,

That is your problem; make sure all sql statements in the package do not have the dabase name as they may be diffrent when you change the connection strings. Just edit the sql statements and remove the database part of the name.