Hi all !
We have a database with publication on
SBS2003 Premium Edition,
and 4 subscribers on workstations in warehouses on:
- Windows XP Professional
- MSDE
The database is 1.6 GB now and growing
further. I should migrate from MSDE
to SQL Server 2000.
Which version of SQL has to be installed
at warehouses (on top of Win XP Prof)?
Do I have to break the replication before ?
Thanks,
Pagus
Paul,
what about Personal Edition + Win XP Pro ?
Win XP Pro is working OK with MSDE, I wouldn't like to
purchase Win Server product :-(
Pagus
On Mon, 6 Sep 2004 00:48:11 -0700, "Paul Ibison"
<Paul.Ibison@.Pygmalion.Com> wrote:
>Pagus,
>you'll need Standard or Enterprise Edition. The OSs=20
>required for these editions of sql server are:
>Windows Server 2003, Standard Edition1=20
>Windows Server 2003, Enterprise Edition1=20
>Windows Server 2003, Datacenter Edition1=20
>Windows=AE 2000 Server=20
>Windows 2000 Advanced Server=20
>Windows 2000 Datacenter Server=20
>Windows NT=AE Server version 4.0 with Service Pack 5 (SP5)=20
>or later=20
>Windows NT Server 4.0, Enterprise Edition, with SP5 or=20
>later=20
>HTH,
>Paul Ibison
>(The ONLY sql server 2000 replication book:
>http://www.nwsu.com/0974973602p.html)
>
|||Pagus,
you're quire right, subject to the following restrictions:
It includes a concurrent workload governor that limits
its scalability; performance degrades when more than five
Transact-SQL batches are executed concurrently.
It cannot act as a transactional replication publisher
(subscriber only).
Regards,
Paul Ibison
Showing posts with label subscriber. Show all posts
Showing posts with label subscriber. Show all posts
Friday, March 30, 2012
MSDE Subscriber names
I plan to set up merge replication and have laptops with an MSDE
subscription for replication. I want my application to use the database
name and wondered if I can (and should?) have the same database name on both
the laptop and the main publication. Thanks.
David
It helps to identify the subscriber database, but there is no real
requirement. All the subscribers should have the same database name if you
are publishing to multiple subscribers at once.
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
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:%23KWrAVCpFHA.320@.TK2MSFTNGP09.phx.gbl...
> I plan to set up merge replication and have laptops with an MSDE
> subscription for replication. I want my application to use the database
> name and wondered if I can (and should?) have the same database name on
both
> the laptop and the main publication. Thanks.
> David
>
subscription for replication. I want my application to use the database
name and wondered if I can (and should?) have the same database name on both
the laptop and the main publication. Thanks.
David
It helps to identify the subscriber database, but there is no real
requirement. All the subscribers should have the same database name if you
are publishing to multiple subscribers at once.
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
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:%23KWrAVCpFHA.320@.TK2MSFTNGP09.phx.gbl...
> I plan to set up merge replication and have laptops with an MSDE
> subscription for replication. I want my application to use the database
> name and wondered if I can (and should?) have the same database name on
both
> the laptop and the main publication. Thanks.
> David
>
Friday, March 23, 2012
MSDE publisher and subscriber with duplicated Identity column issues
I am new to SQL replication and I have an issue with the identity
column not properly synchronizing between two MSDE databases. I have
turned on the (not for replication) switch and changed the identity
seed and identity increment to be different on the subscriber, but as
soon as I pull the subscription it changes the seed back to the
original so both database are the same again. As both subscriber and
publisher are creating records, the identities are duplicated. I do
have Enterprise Manager installed to help configure the publishing,
but MSDE does not seem to allow the same control over the identity
range in replication as SQL 2000 does. How do I have a MSDE publisher
and a MSDE subscriber create records in different identity seeds
and/or increment?
What I am trying to accomplish:
Publisher -- seed 1, increment 2
Subscriber -- seed 2, increment 2
Or a similar function.
Thanks,
Daniel
Are you using replication's auto identity management feature. In SQL
identitites once a table is created you cannot change the identity increment
or the original seed. The only thing you can do is reseed to a value and SQL
with start inserting from that value onwards.
Thanks.
"Daniel" <dmaynes@.roinc.com> wrote in message
news:5ab2240f.0410061403.3923ef4a@.posting.google.c om...
> I am new to SQL replication and I have an issue with the identity
> column not properly synchronizing between two MSDE databases. I have
> turned on the (not for replication) switch and changed the identity
> seed and identity increment to be different on the subscriber, but as
> soon as I pull the subscription it changes the seed back to the
> original so both database are the same again. As both subscriber and
> publisher are creating records, the identities are duplicated. I do
> have Enterprise Manager installed to help configure the publishing,
> but MSDE does not seem to allow the same control over the identity
> range in replication as SQL 2000 does. How do I have a MSDE publisher
> and a MSDE subscriber create records in different identity seeds
> and/or increment?
> What I am trying to accomplish:
> Publisher -- seed 1, increment 2
> Subscriber -- seed 2, increment 2
> Or a similar function.
> Thanks,
> Daniel
|||I guess this is a newbi question, but how and when do I turn that on?
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Daniel,
when you create the publication, on the article properties (the elipsis
button) there is a series of tabs, one called 'identity range'. The checkbox
at the top allows for automatic range management. Some people don't use it
and prefer to roll their own, using formulas like odds on the publisher and
evens on the subscriber.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Right, I found that. I guess the trick is that it has to be checked as
you build the publication, and can be modified, but not added
afterwards. Thank you very much.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
column not properly synchronizing between two MSDE databases. I have
turned on the (not for replication) switch and changed the identity
seed and identity increment to be different on the subscriber, but as
soon as I pull the subscription it changes the seed back to the
original so both database are the same again. As both subscriber and
publisher are creating records, the identities are duplicated. I do
have Enterprise Manager installed to help configure the publishing,
but MSDE does not seem to allow the same control over the identity
range in replication as SQL 2000 does. How do I have a MSDE publisher
and a MSDE subscriber create records in different identity seeds
and/or increment?
What I am trying to accomplish:
Publisher -- seed 1, increment 2
Subscriber -- seed 2, increment 2
Or a similar function.
Thanks,
Daniel
Are you using replication's auto identity management feature. In SQL
identitites once a table is created you cannot change the identity increment
or the original seed. The only thing you can do is reseed to a value and SQL
with start inserting from that value onwards.
Thanks.
"Daniel" <dmaynes@.roinc.com> wrote in message
news:5ab2240f.0410061403.3923ef4a@.posting.google.c om...
> I am new to SQL replication and I have an issue with the identity
> column not properly synchronizing between two MSDE databases. I have
> turned on the (not for replication) switch and changed the identity
> seed and identity increment to be different on the subscriber, but as
> soon as I pull the subscription it changes the seed back to the
> original so both database are the same again. As both subscriber and
> publisher are creating records, the identities are duplicated. I do
> have Enterprise Manager installed to help configure the publishing,
> but MSDE does not seem to allow the same control over the identity
> range in replication as SQL 2000 does. How do I have a MSDE publisher
> and a MSDE subscriber create records in different identity seeds
> and/or increment?
> What I am trying to accomplish:
> Publisher -- seed 1, increment 2
> Subscriber -- seed 2, increment 2
> Or a similar function.
> Thanks,
> Daniel
|||I guess this is a newbi question, but how and when do I turn that on?
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Daniel,
when you create the publication, on the article properties (the elipsis
button) there is a series of tabs, one called 'identity range'. The checkbox
at the top allows for automatic range management. Some people don't use it
and prefer to roll their own, using formulas like odds on the publisher and
evens on the subscriber.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Right, I found that. I guess the trick is that it has to be checked as
you build the publication, and can be modified, but not added
afterwards. Thank you very much.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Subscribe to:
Posts (Atom)