Sql-server – Windows SQL Server Express 2012 and LDAP external server integration

ldapsql-server-2012windows-server

I have a new installation of Windows Server 2012 with SQL Server Express 2012 with the management tools.

I'm planning to create there a simple synchronization that will make queries twice per day to an external LDAP service (not a Windows active directory server) and fill a table in the local SQL instance. I've seen other questions here about this, and all of them refer to the creation of a Linked Server, but I think that will only work if the remote LDAP service was a Windows AD server.

I'm able to query this server using the LDP tool, but looks like I cannot add it as a linked server. Any ideas?

Best Answer

Do you just want to configure this? Or are you not averse to writing some code?

In the latter case, it should be relatively easy to write a small program that connects to both the LDAP server and the database and synchronizes the data. I've written such a thing once in PL/SQL in Oracle -- if it's possible there it should be possible in most languages and environments!

Related Solutions

SQL Server 2012 – Kerberos Authentication Not Working with Linked Servers

Dealing with Active Directory is always so much fun. The single most important thing here is to realize you are dealing with distributed data that can take time to propagate across your network.

The SQL Servers in question had their name changed as part of an upgrade procedure; we replaced an existing machine (SQL01) running SQL Server 2005 with a new machine (SQL03) running SQL Server 2012. SQL03 was the name of the new machine when I initially set it up in the domain. SQL01 had an existing SPN associated with a single domain account we used for several SQL Servers running 2005. Since it is a best practice to only run a single machine under any given domain account, I created a new account and configured SQL03 to run with that account name. After taking the original SQL01 out of service, and renaming SQL03 to SQL01, there was an SPN conflict.

I used the SetSPN.exe utility to delete the conflicting SPN (on the old domain account) - and it still didn't work. At this point, I did nothing further and moved on to other items. When I came back around 30 minutes later, KERBEROS authentication was working. I simply needed to wait for the SPN change to propagate among our domain controllers.

I used SetSPN -L DOMAIN\Account and compared that output with SetSPN -Q MSSQLSvc/Machine.domain.inet:1433 to find the duplicate SPNs, and then used SetSPN -D MSSQLSvc/Machine.domain.inet:1433 DOMAIN\Account to remove the old SPNs.

Sql-server – SQL Server Service Account login or password is not valid error

The issue isn't with the account you are attempting to use, but your account. If you look in the setup log file, which is created during the installation of the SQL Server application, you will see the details of the issue, with technical jargon that will indicate the issue is probably a permission issue with your account having permission to perform a check on the service account credentials:

Slp: Sco: Attempting to check if container ‘WinNT://DOMAIN’ of user account exists
Slp: UserSecurity.ValidateCredentials — Exception caught and ignored, exception is Access is denied.
Slp: UserSecurity.ValidateCredentials — user validation failed

Rebooting usually fixes this issue, as does changing the service account value after installation is complete. A minor issue that sometimes appears.

Best Answer

Related Solutions

SQL Server 2012 – Kerberos Authentication Not Working with Linked Servers

Sql-server – SQL Server Service Account login or password is not valid error

Related Question