Publisher /distributor - same server SQL Server 7.0 SP 4
Subscriber - Oracle 9.2.0.3.0
After configuring Oracle subscriber whether as a linked server or a system
DSN, I run the distribution agent and get the following error message:
"Distributor must be running in per seat (named user) licensing mode to use
this replication feature"
SQL Server is set up in per server licensing mode. Now where in al the
documentation does it say that there is this restriction, I really don't
want to change my licensing mode just to work around this one issue. Is
there something I can change in my config to make this work?
Thanks in advance
Tony.
DTS and replication are two components that require the per seat option for
the desktop version of SQL Server.
http://support.microsoft.com/default...b;en-us;207809
Exactly which version of SQL Server are you running?
"TonyL" <anonymous@.discussions.microsoft.com> wrote in message
news:uUkqsDxIEHA.3572@.TK2MSFTNGP10.phx.gbl...
> Publisher /distributor - same server SQL Server 7.0 SP 4
> Subscriber - Oracle 9.2.0.3.0
> After configuring Oracle subscriber whether as a linked server or a system
> DSN, I run the distribution agent and get the following error message:
> "Distributor must be running in per seat (named user) licensing mode to
use
> this replication feature"
> SQL Server is set up in per server licensing mode. Now where in al the
> documentation does it say that there is this restriction, I really don't
> want to change my licensing mode just to work around this one issue. Is
> there something I can change in my config to make this work?
> Thanks in advance
> Tony.
>
|||It's standard edition. This SQL server has been happily replicating data to
other SQL Servers since I set it up 4 1/2 years ago. Ths week was when I
had the first requirement to replicate to an Oracle subscriber.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:u9fHO0xIEHA.940@.tk2msftngp13.phx.gbl...
> DTS and replication are two components that require the per seat option
for[vbcol=seagreen]
> the desktop version of SQL Server.
> http://support.microsoft.com/default...b;en-us;207809
> Exactly which version of SQL Server are you running?
>
> "TonyL" <anonymous@.discussions.microsoft.com> wrote in message
> news:uUkqsDxIEHA.3572@.TK2MSFTNGP10.phx.gbl...
system
> use
>
|||I have run into cases where it seems that the licensing info gets scrambled
on SQL 7. I think these occured when we upgraded from nt 4 to win2k.
Can you run a test where you set up a new publication and replicate locally
to perhaps the pubs or northwind database to see what happens?
"TonyL" <anonymous@.discussions.microsoft.com> wrote in message
news:uQI4r7xIEHA.1528@.TK2MSFTNGP09.phx.gbl...
> It's standard edition. This SQL server has been happily replicating data
to[vbcol=seagreen]
> other SQL Servers since I set it up 4 1/2 years ago. Ths week was when I
> had the first requirement to replicate to an Oracle subscriber.
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:u9fHO0xIEHA.940@.tk2msftngp13.phx.gbl...
> for
> system
to[vbcol=seagreen]
don't[vbcol=seagreen]
Is
>
|||Hilary,
I add SQL Server subscribers to publications on this server regularly, I
don't think this test will identify anything as the issue is with adding an
Oracle subscriber. I also set up a brand new publication on another SQL
Server and added an Oracle subscriber with the same result.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:ufGquUyIEHA.2908@.TK2MSFTNGP09.phx.gbl...
> I have run into cases where it seems that the licensing info gets
scrambled
> on SQL 7. I think these occured when we upgraded from nt 4 to win2k.
> Can you run a test where you set up a new publication and replicate
locally[vbcol=seagreen]
> to perhaps the pubs or northwind database to see what happens?
> "TonyL" <anonymous@.discussions.microsoft.com> wrote in message
> news:uQI4r7xIEHA.1528@.TK2MSFTNGP09.phx.gbl...
> to
I[vbcol=seagreen]
option[vbcol=seagreen]
message:[vbcol=seagreen]
> to
the
> don't
> Is
>
|||Hi Tony,
This isn't right. Please call in and open a case with PSS and keep me in the loop so that I can track the case.
Matt
Program Manager
Microsoft SQL Server Replication
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
|||OK, after talking to PSS here is an extract from the resolution email:
"In the article Q207809, if you set up replication with configuring a SQL
7.0 (using Per Server mode ) as distributor and the subscriber is SQL 7.0
desktop edition, then you will receive the error due to license restriction.
We researched and confirmed that it is by-design that any non-SQL server
subscriber will be considered as equivalent to SQL 7.0 desktop edition
license situation. This means the server that the subscriber communicates
with must evaluate connections based on the Per-Seat licensing model. "
My point is that this is not mentioned in any documentation anywhere.
Tony.
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:e1spcu$IEHA.3304@.TK2MSFTNGP10.phx.gbl...
> Hi Tony,
> This isn't right. Please call in and open a case with PSS and keep me in
the loop so that I can track the case.
> Matt
> Program Manager
> Microsoft SQL Server Replication
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
Monday, March 12, 2012
Heterogeneous Subscriber Oracle
Labels:
0after,
4subscriber,
configuring,
database,
distributor,
heterogeneous,
linked,
microsoft,
mysql,
oracle,
publisher,
server,
sql,
subscriber
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment