I wrote a blog post some time ago about using SQL Developer 3.x to connect to SQL Server. I tried the same thing today from SQL Developer 4 EA2 and it works just fine.
You have to download the 3rd party JDBC driver and point SQL Developer to it. You can read how to do it here.
Cheers
Tim…
Update: My colleague just told me this.
“If you at any point decide to use Windows authentication to connect (like I just did), you might hit this error:
Status : Failure -I/O Error: SSO Failed: Native SSPI library not loaded. Check the java.library.path system property.
…found a work around, which involves copying the ‘jtds-1.2\x86 (or X64)\SSO\ntlmauth.dll’ from the JTDS directory to the JDK’s \jdk\jre\bin folder. Then I restarted SQL Developer and it worked J”
SQL Developer 4 EA2 Connecting to SQL Server | The ORACLE-BASE Blog http://t.co/2NpU415LSf
RT @oraclebase: SQL Developer 4 EA2 Connecting to SQL Server | The ORACLE-BASE Blog http://t.co/2NpU415LSf
RT @oraclebase: SQL Developer 4 EA2 Connecting to SQL Server | The ORACLE-BASE Blog http://t.co/2NpU415LSf
For SQLDev EA3 I had to use JTDS 1.3.1. (based on a suggestion from the product manager)
I was finally able to connect to SQL Server 2008 after a specific user ID and password was created on the SQL Server database. I was not able to connect using my own User ID or Windows Authentication
I was not able to connect to SQL Server 2008 until a User ID was createdon the SQL Server database. I could not connect using my own User ID or Windows Authentication.