Replication Distributor Version

What is the minimum SQL Server version I can use on my replication distributor server? My publisher and subscriber(s) will all be Enterprise Edition (64 bit). However, it seems awefully wasteful to put Enterprise Edition on a box that is just used for distribution. That's another $15K for a server that doesn't do much. Can I use a lower version (Express, Developer, Standard)?

Thank you,

Ben Wolf

This page (http://msdn2.microsoft.com/en-us/library/ms143761.aspx) lists the features (including replication) that are supported by various editions of SQL server. (Go all the way to the bottom for replication)

Basically, Express is not supproted for distributor. Developer edition includes all the functionalities of Enterprise edition SQL server, but it is only licensed for development and/or test purpose, not as a production server.

Peng

|||

Thank you, Peng. This is exactly what I needed. Looks like SE is the one for my distributor.

Thanks again,

Ben

sql

Replication Distributor Version

What is the minimum SQL Server version I can use on my replication distributor server? My publisher and subscriber(s) will all be Enterprise Edition (64 bit). However, it seems awefully wasteful to put Enterprise Edition on a box that is just used for distribution. That's another $15K for a server that doesn't do much. Can I use a lower version (Express, Developer, Standard)?

Thank you,

Ben Wolf

This page (http://msdn2.microsoft.com/en-us/library/ms143761.aspx) lists the features (including replication) that are supported by various editions of SQL server. (Go all the way to the bottom for replication)

Basically, Express is not supproted for distributor. Developer edition includes all the functionalities of Enterprise edition SQL server, but it is only licensed for development and/or test purpose, not as a production server.

Peng

|||

Thank you, Peng. This is exactly what I needed. Looks like SE is the one for my distributor.

Thanks again,

Ben

Replication between SQL Express 2005

Hi All,

I am trying to do a Replication between a network SQL Server Express Edition 2005 DB with a client SQL Server Express Edition 2005 DB. My question is

1. Can we do replicaiton between SQL Server Express Edition 2005. (No SQL SERVER present)

2. If yes can any of you provide me some guidance or some pointers on how to achieve it.

Thanks

Suresh

Quick answer is no. Check out the following posting for more info.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=941980&SiteID=1

Gary

Replication between SQL 2005 Express Edition and SQL 2005 Standard Edition

Hello everybody,

I got a problem in my development phase. I'm developing a web-application system that running merge database technology which is centralized database and distributed database. This is because my customer want a highly optimum system standby.

My centralized database running SQL Server 2005 Standard Edition and the distributed database running SQL Server 2005 Express Edition (because it is free). Each of these database, the users can change the data on its database. So, every database must have the same data. from my understanding, each server must act as Publisher and Subscriber. Can SQL Server 2005 Express Edition be a Publisher?

If not, what the solution you all may suggest, because cost is the first factor. If my architecture is not correct, so what you all suggest to me to resolve the problem.

Thanks so much. Any suggestion and opinion is highly appreciate and I'm highly thanks to you all.

You cannot republish with SQL Express, you need Standard Edition or higher. As for solutions, see if you can try to not republish and use the single publisher scenario, or pay for Standard Edition. If cost is a factor, then you have to weigh $$$ versus not being able to meet your business requirements.|||If your intent is that you want the Standard and the express editions to be in sync, and that you want the DML that happen at the Express to be sent to the Standard edition too, you dont need to make the Express as a publisher. By default when you setup merge replication between 2 nodes, they both are read-write. That is Express site and do DML and the merge agent can send across these DML to the Standard edition site.

Replication Between Instances Issue.

I'm doing Transactional Replication from Server1 to PC1.

Server1 Info:
Domain: A
SQL Server 2000 Enterprise Edition SP3.
SQL Server Services under Local System Account.

PC1 Info:
Domain: B
SQL Server 2000 Developer Edition SP3
SQL Server Services under Local System Account.

The process I did in EM was:

1. Create Remote Server to PC1 from Server1. Did not check RPC checkbox.Map all remote logins to same name. Did not check password.
2. Created Publisher and Distributer on Server1.
3. Publish new publication of DB1 in Server1.
4. Push new subscriber , auto create DB1_copy in PC1.
5. Snapshot successful.
6. Distributor Agent Failed.

Error Message:
The process could not connect to Subscriber 'Pc1'.

Error Details:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
(Source: PC1 (Data source); Error number: 18452)

I have identical local WINNT ID's and password on both machine. I was guessing that would solve it. But it didn't.

Previously I did snapshot and transactional replication on the same machine itself( Server1 only). It was succesful.

Did I miss out anything?
Has it got to do with any Remote Server setting?
I've heard that Replication can only be done on the same domain. Is this true?
What if there are cases of different domains? Or in a workgroup perharps?
Or can it be overwritten by having 2 identical local WINNT ids in both machines?
Lastly, Can Personal Edition SQL Server 2000 do replication?Help?|||By not knowing your environment completely, I would suggest that you change your sql startup account from local system account to a network account. Use the same network account for both machine and, of course, it has to be admin in both machine.

Good luck!|||I've actually solve the problem and concluded by myself that replication can be done on separate domains or workgroups or whatever.
As long as an IP can ping the other IP, it will work.

During registration of Publisher and Subcriber, check "show advanced options" during the wizard. From there, there will be a section where u can click to chose Windows Authetication or SQL Server Login.

Chose SQL Server Login during Publisher Wizard and also SQL Server Login during Subscriber Wizard. And voila!, that will solve the problem.

However, again, this is thru test and fail method of solving a problem, are there any pointer anybody would like to share?sql

replication between different sites

Can standard SQL2k replicate with enterprise edition within different sites?
*example - Central server(enterprise) in LA want to replicate with
branch(standard) in NY.
Imran,
these editions of sql server are completely compatible. As for different
sites, you'll need to follow the guidelines for replication across the
internet or non-trusted domains: http://support.microsoft.com/?id=321822.
HTH,
Paul Ibison
(The ONLY sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql

Replication between 64-bit and 32-bit?

We have a 32-bit edition today and want to secure the uptime by adding a cold
standby.
We want to purchase a new 64-bit machine with the 64-bit editions of OS/SQL.
The 64-bit should replicate data to our "old" 32-bit machine.
I have not found any information on MS-site about this, is this possible?
Will it work just to the same way as replicating between two 32-bit
enivironments?
You should be able to replicate between 32 bit and 64 bit SQL Server
editions. I have a scenario where distributor is 64 bit and publisher and
subscriber are 32 bit. It is working fine, and is transparent.
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Patrik" <Patrik@.nospam.nospam> wrote in message
news:4F9BA96C-F9AA-4C6E-BD30-391CD75F666A@.microsoft.com...
We have a 32-bit edition today and want to secure the uptime by adding a
cold
standby.
We want to purchase a new 64-bit machine with the 64-bit editions of OS/SQL.
The 64-bit should replicate data to our "old" 32-bit machine.
I have not found any information on MS-site about this, is this possible?
Will it work just to the same way as replicating between two 32-bit
enivironments?
|||Hello,
I suggest that you refer to the following information:
Features Supported by the Editions of SQL Server 2000 (64-bit)
http://msdn.microsoft.com/library/de...us/sql64/in_pr
eparing64_6184.asp
You can refer to the "Replication Features Supported by the Editions of SQL
Server 2000 (64-bit)" section.
advantages of a 64-Bit Environment :
http://www.microsoft.com/sql/64bit/p...Advantages.asp
Replication
The Replication features of SQL Server 2000 (64-bit) are nearly identical
to the 32-bit version, with the following features being supported:
"Snapshot Replication
"Transactional Replication
"Merge Replication
"Immediately updating subscribers
"Queued updating subscribers
However, there are a few special cases:
"As the Microsoft Jet engine is not supported, Microsoft Jet push
subscriptions for merge replication are not supported.
"Unless the subscriber provides a 64-bit ODBC or OLE DB driver,
transactional or snapshot push subscriptions for ODBC or OLE DB subscribers
are not supported.
"Because of the unavailability of 64-bit Data Transformation Services
(DTS), transformable push subscriptions are not supported.
In addition, the 64-bit versions of Windows Server 2003, Enterprise Edition
and Windows Server 2003, Datacenter Edition do not include certain features
that are included in the 32-bit versions of those operating systems.
These features are not included because of underlying differences between
the 32-bit and 64-bit architectures or because the features are not
appropriate in the environments where the 64-bit versions of Windows Server
2003, Enterprise Edition and Windows Server 2003, Datacenter Edition are
deployed.
For a complete list of differences, see "Differences Between 64-bit and
32-bit Releases (64-bit)" in SQL Server 2000 (64-bit) Books Online and
"Features unavailable on 64-bit versions of the Windows Server 2003 family"

Replication between 64-bit and 32-bit?

We have a 32-bit edition today and want to secure the uptime by adding a col
d
standby.
We want to purchase a new 64-bit machine with the 64-bit editions of OS/SQL.
The 64-bit should replicate data to our "old" 32-bit machine.
I have not found any information on MS-site about this, is this possible?
Will it work just to the same way as replicating between two 32-bit
enivironments?You should be able to replicate between 32 bit and 64 bit SQL Server
editions. I have a scenario where distributor is 64 bit and publisher and
subscriber are 32 bit. It is working fine, and is transparent.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Patrik" <Patrik@.nospam.nospam> wrote in message
news:4F9BA96C-F9AA-4C6E-BD30-391CD75F666A@.microsoft.com...
We have a 32-bit edition today and want to secure the uptime by adding a
cold
standby.
We want to purchase a new 64-bit machine with the 64-bit editions of OS/SQL.
The 64-bit should replicate data to our "old" 32-bit machine.
I have not found any information on MS-site about this, is this possible?
Will it work just to the same way as replicating between two 32-bit
enivironments?|||Hello,
I suggest that you refer to the following information:
Features Supported by the Editions of SQL Server 2000 (64-bit)
http://msdn.microsoft.com/library/d...-us/sql64/in_pr
eparing64_6184.asp
You can refer to the "Replication Features Supported by the Editions of SQL
Server 2000 (64-bit)" section.
advantages of a 64-Bit Environment :
http://www.microsoft.com/sql/64bit/...tAdvantages.asp
Replication
The Replication features of SQL Server 2000 (64-bit) are nearly identical
to the 32-bit version, with the following features being supported:
" Snapshot Replication
" Transactional Replication
" Merge Replication
" Immediately updating subscribers
" Queued updating subscribers
However, there are a few special cases:
" As the Microsoft Jet engine is not supported, Microsoft Jet push
subscriptions for merge replication are not supported.
" Unless the subscriber provides a 64-bit ODBC or OLE DB driver,
transactional or snapshot push subscriptions for ODBC or OLE DB subscribers
are not supported.
" Because of the unavailability of 64-bit Data Transformation Services
(DTS), transformable push subscriptions are not supported.
In addition, the 64-bit versions of Windows Server 2003, Enterprise Edition
and Windows Server 2003, Datacenter Edition do not include certain features
that are included in the 32-bit versions of those operating systems.
These features are not included because of underlying differences between
the 32-bit and 64-bit architectures or because the features are not
appropriate in the environments where the 64-bit versions of Windows Server
2003, Enterprise Edition and Windows Server 2003, Datacenter Edition are
deployed.
For a complete list of differences, see "Differences Between 64-bit and
32-bit Releases (64-bit)" in SQL Server 2000 (64-bit) Books Online and
"Features unavailable on 64-bit versions of the Windows Server 2003 family"

Replication between 64-bit and 32-bit?

We have a 32-bit edition today and want to secure the uptime by adding a cold
standby.
We want to purchase a new 64-bit machine with the 64-bit editions of OS/SQL.
The 64-bit should replicate data to our "old" 32-bit machine.
I have not found any information on MS-site about this, is this possible?
Will it work just to the same way as replicating between two 32-bit
enivironments?You should be able to replicate between 32 bit and 64 bit SQL Server
editions. I have a scenario where distributor is 64 bit and publisher and
subscriber are 32 bit. It is working fine, and is transparent.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Patrik" <Patrik@.nospam.nospam> wrote in message
news:4F9BA96C-F9AA-4C6E-BD30-391CD75F666A@.microsoft.com...
We have a 32-bit edition today and want to secure the uptime by adding a
cold
standby.
We want to purchase a new 64-bit machine with the 64-bit editions of OS/SQL.
The 64-bit should replicate data to our "old" 32-bit machine.
I have not found any information on MS-site about this, is this possible?
Will it work just to the same way as replicating between two 32-bit
enivironments?|||Hello,
I suggest that you refer to the following information:
Features Supported by the Editions of SQL Server 2000 (64-bit)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sql64/in_pr
eparing64_6184.asp
You can refer to the "Replication Features Supported by the Editions of SQL
Server 2000 (64-bit)" section.
advantages of a 64-Bit Environment :
http://www.microsoft.com/sql/64bit/productinfo/SQL64bitAdvantages.asp
--
Replication
The Replication features of SQL Server 2000 (64-bit) are nearly identical
to the 32-bit version, with the following features being supported:
" Snapshot Replication
" Transactional Replication
" Merge Replication
" Immediately updating subscribers
" Queued updating subscribers
However, there are a few special cases:
" As the Microsoft Jet engine is not supported, Microsoft Jet push
subscriptions for merge replication are not supported.
" Unless the subscriber provides a 64-bit ODBC or OLE DB driver,
transactional or snapshot push subscriptions for ODBC or OLE DB subscribers
are not supported.
" Because of the unavailability of 64-bit Data Transformation Services
(DTS), transformable push subscriptions are not supported.
In addition, the 64-bit versions of Windows Server 2003, Enterprise Edition
and Windows Server 2003, Datacenter Edition do not include certain features
that are included in the 32-bit versions of those operating systems.
These features are not included because of underlying differences between
the 32-bit and 64-bit architectures or because the features are not
appropriate in the environments where the 64-bit versions of Windows Server
2003, Enterprise Edition and Windows Server 2003, Datacenter Edition are
deployed.
For a complete list of differences, see "Differences Between 64-bit and
32-bit Releases (64-bit)" in SQL Server 2000 (64-bit) Books Online and
"Features unavailable on 64-bit versions of the Windows Server 2003 family"sql

Replication & Different Versions

Hi,
Apologies if the answer to this is obvious, I'm not a SQL expert!
We've got a W2k3 cluster running SQL 2000 Enterprise edition.
I'm investigating the possibility of replicating this back to a standalone,
SQL 2000 Standard server.
Is this possible, or is not recommended to mix clustering arrangements or
SQL versions when replicating?
Pocket
This arrangement is fine. There are some restrictions as to which edition
can be the publisher in transactional replication, but this applies to MSDE
and Personal Edition. For Enterprise and Standard there are no issues.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
Thank you: that's answered my question perfectly.
"Paul Ibison" wrote:

> This arrangement is fine. There are some restrictions as to which edition
> can be the publisher in transactional replication, but this applies to MSDE
> and Personal Edition. For Enterprise and Standard there are no issues.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>

Replication

Hi guys,
Is it possible to replicate in MSSQL SERVER standard edition and be
supported? Or do I need to buy enterprise edition.

Regards

Jaideepjai (dba_sybase2003@.yahoo.com) writes:
> Hi guys,
> Is it possible to replicate in MSSQL SERVER standard edition and be
> supported? Or do I need to buy enterprise edition.

You can do replicaiton in Standard Edition.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Yeah I kind of knew that replication is possible in the standard
edition but will MIcrosoft support it.

Regards

Jaideep|||jai (dba_sybase2003@.yahoo.com) writes:
> Yeah I kind of knew that replication is possible in the standard
> edition but will MIcrosoft support it.

Yes.

Please check Books Online, the book SQL Server Architecture ->
Implementation Details -> Editions of SQL Server 2000 ->
Features Supported by the Editions of SQL Server 2000.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland,
I am new to sql server replication but I have worked with sybase
replication. At present, the machine housing the sql server has 2 g of
memory with 1.4 g for sql server. How much more (memory), would I need
if I make the same machine work as publisher as well as the
distributor?

Regards

Jaideep|||jai (dba_sybase2003@.yahoo.com) writes:
> Erland,
> I am new to sql server replication but I have worked with sybase
> replication. At present, the machine housing the sql server has 2 g of
> memory with 1.4 g for sql server. How much more (memory), would I need
> if I make the same machine work as publisher as well as the
> distributor?

You will have to ask the friendly people in
microsoft.public.sqlserver.replication about that. My own experience
of replication is very thin. My gut feeling is that it would depend a
lot of the data volume you intend to replicate.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||"jai" <dba_sybase2003@.yahoo.com> wrote in message
news:1124737698.551148.233410@.z14g2000cwz.googlegr oups.com...
> Erland,
> I am new to sql server replication but I have worked with sybase
> replication. At present, the machine housing the sql server has 2 g of
> memory with 1.4 g for sql server. How much more (memory), would I need
> if I make the same machine work as publisher as well as the
> distributor?

Howmuch data do you expect to replicate at any time?

Basically all that happens is the log reader puts rows into a distribution
DB which then gets used to distribute them to the subscribers.

You probably have enough RAM since you can't get much more in Standard
version anyway.

> Regards
> Jaideep

Replicating to SQL 2000/2005 Express

We would like to replicate from SQL 2000/2005 Enterprise Edition to its
Express version and wanted to know if there we any issues around it. This
would be transactional replication
Hassan,
the main distinction that I know of is that for pull subscriptions there is
the limitation of Windows Synchronization Manager or RMO. Also obviously
there can be no republishing.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Replicating Sql Server to Express Edition as backup application

Hello!

We are running a business critical client-server application that needs to have high availability to the end user.
I was wondering if it would be possible to setup a replication/data transfer from an existing Sql Server 7.0/8.0/9.0 (regular online environment running on server) TO an instance of Sql 2005 Express Edition (backup env. running on klient PC).
In case of server failure the application would redirect - accessing the local PC Express edition.

Does anyone have any input on this, and if it would be a possible alternative to use as extra standby- system. ?

Kind regards
TomasYes this is possible but there are certain exceptions.
And it depends on what kind of replication technology you are looking at.
SQL Server 2005 Books Online has more information on supported topologies.

Search for "Using Multiple Versions of SQL Server in a Replication Topology"|||

Hi Tomas.

It would appear that I have a similar type of need. See this post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=677662&SiteID=1 which describes my situation. If you've got any further info on how this is achieved please respond. I'll do the same. We were able to create the windows form app and use Sql2005 Std to maintain a 'gold' standard db on our publisher/distributor machine. We have to replace our db daily with an entirely new dataset that is sent to us via a foreign host. We take that data an bulk copy it into our db. Then, we setup a snapshot replication scenario, installing SqlExpress w/ Advance Tools on the subscriber machine.

We install our offline viewer windows smart client application on the subscriber, and are able to bring in a view of the needed data. However, we need this view to be available offline, for use when the prefferred application is unavailable or when the network is down. At this point, if the network is down our replicated db is not available either. So, I'm lost with the way I've got it working now. I'm not sure if it is a setup issue or if I've misunderstood how replication works. At any rate, our need appears to be similar in scope to yours. I'll check back here, and on my post to update the status.

Right now, we are examining our setup of the replication subscription and whether there is a way to achieve the goal desired, or if we have to employ a bulk copy insert into a local database for our subscriber downtime usage.

|||

Hi,

You might want to talk to us about a product that we sell (WANSync) which provides real-time asynchronous data replication, full tree replication topologies to protect from server and site failures. Should an SQL database server fail for any reason, a geographically remote SQL replica takes it's place and will allow you to keep working.

If you want more information or want to trial this solution for free, please email me at paul.maziere@.dataplex-systems.com

Regards, Paul.

Replicating Sql Server to Express Edition as backup application

Hello!

We are running a business critical client-server application that needs to have high availability to the end user.
I was wondering if it would be possible to setup a replication/data transfer from an existing Sql Server 7.0/8.0/9.0 (regular online environment running on server) TO an instance of Sql 2005 Express Edition (backup env. running on klient PC).
In case of server failure the application would redirect - accessing the local PC Express edition.

Does anyone have any input on this, and if it would be a possible alternative to use as extra standby- system. ?

Kind regards
TomasYes this is possible but there are certain exceptions.
And it depends on what kind of replication technology you are looking at.
SQL Server 2005 Books Online has more information on supported topologies.

Search for "Using Multiple Versions of SQL Server in a Replication Topology"|||

Hi Tomas.

It would appear that I have a similar type of need. See this post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=677662&SiteID=1 which describes my situation. If you've got any further info on how this is achieved please respond. I'll do the same. We were able to create the windows form app and use Sql2005 Std to maintain a 'gold' standard db on our publisher/distributor machine. We have to replace our db daily with an entirely new dataset that is sent to us via a foreign host. We take that data an bulk copy it into our db. Then, we setup a snapshot replication scenario, installing SqlExpress w/ Advance Tools on the subscriber machine.

We install our offline viewer windows smart client application on the subscriber, and are able to bring in a view of the needed data. However, we need this view to be available offline, for use when the prefferred application is unavailable or when the network is down. At this point, if the network is down our replicated db is not available either. So, I'm lost with the way I've got it working now. I'm not sure if it is a setup issue or if I've misunderstood how replication works. At any rate, our need appears to be similar in scope to yours. I'll check back here, and on my post to update the status.

Right now, we are examining our setup of the replication subscription and whether there is a way to achieve the goal desired, or if we have to employ a bulk copy insert into a local database for our subscriber downtime usage.

|||

Hi,

You might want to talk to us about a product that we sell (WANSync) which provides real-time asynchronous data replication, full tree replication topologies to protect from server and site failures. Should an SQL database server fail for any reason, a geographically remote SQL replica takes it's place and will allow you to keep working.

If you want more information or want to trial this solution for free, please email me at paul.maziere@.dataplex-systems.com

Regards, Paul.