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"
Showing posts with label adding. Show all posts
Showing posts with label adding. Show all posts
Wednesday, March 21, 2012
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"
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
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
Wednesday, March 7, 2012
Replication - adding new articles
Hi ,
Previously , i have set up replication to replication Table A , B & C .
However , now that i need to replicate tables D , E & F , can i simply go to
the properties of for that replication and add in the new tables under
articles ?
Will this cause a new snapshot to be created and thus bulk copy all the
previously replicated tables as well ? as i do not want such thing to happen
appreciate ur advise
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200602/1
Yes - you can add the articles to an existing publication. If you run the
snapshot agent, the new articles will be passed over on synchronization.
Running the snapshot will snapshot just the new articles in the case of
transactional, or all the articles in the case of merge. Either way, just
the new tables will be synchronized.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||tk u very much ..
Paul Ibison wrote:
>Yes - you can add the articles to an existing publication. If you run the
>snapshot agent, the new articles will be passed over on synchronization.
>Running the snapshot will snapshot just the new articles in the case of
>transactional, or all the articles in the case of merge. Either way, just
>the new tables will be synchronized.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
Message posted via http://www.droptable.com
|||Hi ,
After i have added a new article and when i tried to change it's name i was
prompted "
Changing this property automatically marks for reinitialization all
subscriptions that support automatic intialization. Reinitialization will
occur the next time the snapshot agent and disribution agent run. note that
you must manually reinitialize the affected replicated objects at
subscriptions that do not support automatica reinitialization.
are you sure you want to change this property and reinitlization all
subscriptions ?"
my quest :
1) wat's meant by automatic initalization ? i have set up my replication to
be continuous mode, is it referring to this ?
2) will it reinitilizates ALL subscriptions ? or just the subscription that
is affected by this change ?
appreciate ur further advise
tks & rdgs
Paul Ibison wrote:
>Yes - you can add the articles to an existing publication. If you run the
>snapshot agent, the new articles will be passed over on synchronization.
>Running the snapshot will snapshot just the new articles in the case of
>transactional, or all the articles in the case of merge. Either way, just
>the new tables will be synchronized.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
Message posted via http://www.droptable.com
|||You should be able to avoid this error by dropping the article then readding
with the new destination name specified at the time of creation:
exec sp_dropsubscription @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.subscriber = 'RSCOMPUTER'
, @.destination_db = 'testrep'
exec sp_droparticle @.publication = 'tTestFNames'
, @.article = 'tEmployees'
exec sp_addarticle @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.source_table = 'tEmployees'
, @.destination_table = 'mynewname'
exec sp_addsubscription @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.subscriber = 'RSCOMPUTER'
, @.destination_db = 'testrep'
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Previously , i have set up replication to replication Table A , B & C .
However , now that i need to replicate tables D , E & F , can i simply go to
the properties of for that replication and add in the new tables under
articles ?
Will this cause a new snapshot to be created and thus bulk copy all the
previously replicated tables as well ? as i do not want such thing to happen
appreciate ur advise
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200602/1
Yes - you can add the articles to an existing publication. If you run the
snapshot agent, the new articles will be passed over on synchronization.
Running the snapshot will snapshot just the new articles in the case of
transactional, or all the articles in the case of merge. Either way, just
the new tables will be synchronized.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||tk u very much ..
Paul Ibison wrote:
>Yes - you can add the articles to an existing publication. If you run the
>snapshot agent, the new articles will be passed over on synchronization.
>Running the snapshot will snapshot just the new articles in the case of
>transactional, or all the articles in the case of merge. Either way, just
>the new tables will be synchronized.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
Message posted via http://www.droptable.com
|||Hi ,
After i have added a new article and when i tried to change it's name i was
prompted "
Changing this property automatically marks for reinitialization all
subscriptions that support automatic intialization. Reinitialization will
occur the next time the snapshot agent and disribution agent run. note that
you must manually reinitialize the affected replicated objects at
subscriptions that do not support automatica reinitialization.
are you sure you want to change this property and reinitlization all
subscriptions ?"
my quest :
1) wat's meant by automatic initalization ? i have set up my replication to
be continuous mode, is it referring to this ?
2) will it reinitilizates ALL subscriptions ? or just the subscription that
is affected by this change ?
appreciate ur further advise
tks & rdgs
Paul Ibison wrote:
>Yes - you can add the articles to an existing publication. If you run the
>snapshot agent, the new articles will be passed over on synchronization.
>Running the snapshot will snapshot just the new articles in the case of
>transactional, or all the articles in the case of merge. Either way, just
>the new tables will be synchronized.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
Message posted via http://www.droptable.com
|||You should be able to avoid this error by dropping the article then readding
with the new destination name specified at the time of creation:
exec sp_dropsubscription @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.subscriber = 'RSCOMPUTER'
, @.destination_db = 'testrep'
exec sp_droparticle @.publication = 'tTestFNames'
, @.article = 'tEmployees'
exec sp_addarticle @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.source_table = 'tEmployees'
, @.destination_table = 'mynewname'
exec sp_addsubscription @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.subscriber = 'RSCOMPUTER'
, @.destination_db = 'testrep'
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Subscribe to:
Posts (Atom)