Connect to a Novell NDS Datasoource via LDAP

Hi All,

Is there a connector in Connections Manager that can access a Novell NDS tree and help to pull data in an SSIS package?

Thanks,

BIG SYou might be able to use a script component (vb.net) as a source to get at your Novell tree.|||Can't. I run a component in CLR and it craps out.Would SSIS be any different?|||There is a Novell ODBC connector which allows you to do that. Check out Novell's website for "NDK:Novell

ODBC Driver for eDirectory".

You need to have rights to the NDS to get the information and you need to have the Novell CLIENT installed before you install the driver (which they don't tell you).|||Is that a connector that I can add to SSIS?|||

BIG S wrote:

Is that a connector that I can add to SSIS?

Once it's installed, you can use a datareader source against the ODBC driver.|||Would simply like to pull user object data back from eDirectory to MS SQL without having to implement the Novell Client, which I think is needed for the Novell ODBC driver. This can be done with a couple of lines of perl... Isn't there an easy way to make this connection and pull this data from within SQL Server? It's just an ldap query....sqlsql

Connect to a Novell NDS Datasoource via LDAP

Hi All,

Is there a connector in Connections Manager that can access a Novell NDS tree and help to pull data in an SSIS package?

Thanks,

BIG S
You might be able to use a script component (vb.net) as a source to get at your Novell tree.|||Can't. I run a component in CLR and it craps out.Would SSIS be any different?
|||There is a Novell ODBC connector which allows you to do that. Check out Novell's website for "NDK:Novell ODBC Driver for eDirectory".

You need to have rights to the NDS to get the information and you need to have the Novell CLIENT installed before you install the driver (which they don't tell you).

|||Is that a connector that I can add to SSIS?
|||

BIG S wrote:

Is that a connector that I can add to SSIS?

Once it's installed, you can use a datareader source against the ODBC driver.|||Would simply like to pull user object data back from eDirectory to MS SQL without having to implement the Novell Client, which I think is needed for the Novell ODBC driver. This can be done with a couple of lines of perl... Isn't there an easy way to make this connection and pull this data from within SQL Server? It's just an ldap query....

confused about pull

I have setup multiple merge replications that are continuously updating.
Now, we need to have laptops in the field that connect occasionally that
will merge. Because of that, I assume it needs merge PULL subscription.
I have had tons of problems and it has never worked. Right now it seems
to always be a permission issue.
First, I need to test this in the office to make sure it works. If it is
working, can I take that laptop out in the field, connect via the
internet, and it will work there with no changes? This is needed because
90% of the time the user is in the field, but occasionally he is in the
office, and I don't want to have to change configurations when he comes
and goes.
Next, to get a pull setup and functioning in the office, this seems to
require both access to SQL (via a sql login I created) AND access to the
server via a windows login - is this true? If so, what is the windows
login access for (the snapshot I beleive)?
So, I guess in a perfect world the laptop can be first configured and
replicated in the office (to get the snapshot) and then taken out of the
office and connect via the internet.
Does all of this sound reasonable. I know (according to Hilary) this is
a very complex issue and I am discovering it is. Hopefully this is like
a push/merge that seemed complex until it was working, then it was(is)
easy.
Let me know people's thoughts.
Thanks.
Darin
*** Sent via Developersdex http://www.codecomments.com ***
Darin,
the initial Initialization process will require access to the share holding
the snapshot files. This access is by default achieved using the sql server
agent and impersonation. If the account which the agent uses doesn't have
rights to the distributor's working folder (snapshot share) or if the
account is simply not recognised on this server, then there will be
problems. In the case of a non-trusted environment you then have to use an
alternative (usually FTP) to get the initialization going. Once it's going,
the merge agent uses whatever you've set up to do synchronization, over your
configured port. This can be trusted or sql authentication, and by default
it is also trusted.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Conflict Management

Hello:
If merge replication uses anonymous pull subscriptions and
the subscribers have no sql server tools installed, how can the
subscribers resolve conflicts? (Can we provide a program interface to
help do this?)
Does replication(merge) preserve transactional integrity
while doing updates to the publisher, if there is a conflict. (That
is, if a updated table, that was updated in a transaction on a
replicated database, conflicts with another replicated database, since
this information waits in conflict tables till resolved, will the
whole transaction wait or will the remaining tables proceed to update
themselves?)
Thanks for the help,
Hananiel
The conflict viewer is one possibility. I believe this ships with Office
2003. The SQL 2000 Resource kit has a chapter devoted to the Conflict
Resolver object. You might want to build your own conflict resolver app.
"Hananiel" <hananiel@.yahoo.com> wrote in message
news:e338e321.0410110813.771d55a8@.posting.google.c om...
> Hello:
> If merge replication uses anonymous pull subscriptions and
> the subscribers have no sql server tools installed, how can the
> subscribers resolve conflicts? (Can we provide a program interface to
> help do this?)
> Does replication(merge) preserve transactional integrity
> while doing updates to the publisher, if there is a conflict. (That
> is, if a updated table, that was updated in a transaction on a
> replicated database, conflicts with another replicated database, since
> this information waits in conflict tables till resolved, will the
> whole transaction wait or will the remaining tables proceed to update
> themselves?)
> Thanks for the help,
> Hananiel