We have a network consisting of some Win2K workstations that connect
to two machines running SQL Server 2000 on Windows Server 2000.
Everything has been running OK for quite a while. I just bought a new
WIN 2003 server to replace the two Win2K servers. The new server is

Problem described below occured when trying to connect to my SQL-
server from the outside (calling my external IP-address). Running
Vista I can't seem to connect to my SQL-server using IP-address at
all:

My WAN group recently made a change to our pivate WAN which removed the PIX
firewalls between sites.  All traffic is now routed over layer three switches.
Since this change happened I can no longer connect to a SQL 2000 server
located in a remote office, BUT only from XP and ...

we've an Java application which select some records from SQL Server 2005. If
connection parameter unicode is active, every select executes an full table
scan an the app is very slow (> 1hour). After changing unicode=false, the
index is used and executing is processed in seconds.

I've been trying to set-up an SSL secured SOAP endpoint to my development SQL Server. But I just can't get this to work...
If I set the PORTS parameter to CLEAR and the LOGIN_TYPE to Windows everything works fine using http://localhost/MyDB/SQL?wsdl.
But if I set PORTS=(SSL) and ...

I've created a web service endpoint on SQL Server 2005. But I failed trying to give access to a database role. I can only grant access to SQL Server users.
Am I doing something wrong here?
Your help is appreciated.
Axel Dahmen

My client has a 3rd party app with SQL 2005, (using SQL, not Windows
authentication) as the backend and mostly XP Pro workstations, two with
Vista Business, all with Gigabit Nic's.  Every screen that involves database
queries runs faster on the Vista's (or on the SQL server ...