Connecting to MSDE via client

Hope someone can explain why this happened.
I installed MSDE on a Winxp workstation.
I then setup clients to access MSDE via TCP/IP using the (Static) IP Address
address of the workstation.
Connection successful
I then removed MSDE2000 and installed MSDE2000 sp3a
Went I to connect to MSDE via TCP/IP and could not connect using the IP
When I changed to The machine name I could connect to MSDE2000
Anyone with any idea.
Server was winXP and workstations Win98 and Win08se.
Regards
Jeff
--
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003Jeff Williams wrote:
> Hope someone can explain why this happened.
> I installed MSDE on a Winxp workstation.
> I then setup clients to access MSDE via TCP/IP using the (Static) IP
> Address address of the workstation.
> Connection successful
> I then removed MSDE2000 and installed MSDE2000 sp3a
> Went I to connect to MSDE via TCP/IP and could not connect using the
> IP When I changed to The machine name I could connect to MSDE2000
> Anyone with any idea.
> Server was winXP and workstations Win98 and Win08se.
> Regards
> Jeff
>
> --
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003
Check that the Server (via sql server network utility) is configured to
use TCP/IP. Also check your client is configured like this too (client
network utility).
Br,
Mark Broadbent
mcdba , mcse+i
=============

Connecting SQL Mgr to non-1433 port?

Ok, if I change the TCP Listen port for SQL Svr to a port other than 1433, I
have been unable to get SQL Mgr to connect to it (this is even if I'm using
SM on the same machine as the SQL service).
I can connect if instead of the IP address I use ".", but trying to connect
via the IP address, no go.
Anyone have a workaround for this?
Thanks,
CC
cc wrote:
> Ok, if I change the TCP Listen port for SQL Svr to a port other than 1433, I
> have been unable to get SQL Mgr to connect to it (this is even if I'm using
> SM on the same machine as the SQL service).
> I can connect if instead of the IP address I use ".", but trying to connect
> via the IP address, no go.
> Anyone have a workaround for this?
> Thanks,
> CC
Include the port number in the hostname that you connect to, i.e.
myserver,1433
or
100.100.100.100,1433
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Tracy:
Ah, thank you, I had been using a ':'
CC
"Tracy McKibben" wrote:

> cc wrote:
> Include the port number in the hostname that you connect to, i.e.
> myserver,1433
> or
> 100.100.100.100,1433
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Connecting SQL Mgr to non-1433 port?

Ok, if I change the TCP Listen port for SQL Svr to a port other than 1433, I
have been unable to get SQL Mgr to connect to it (this is even if I'm using
SM on the same machine as the SQL service).
I can connect if instead of the IP address I use ".", but trying to connect
via the IP address, no go.
Anyone have a workaround for this?
Thanks,
CCcc wrote:
> Ok, if I change the TCP Listen port for SQL Svr to a port other than 1433,
I
> have been unable to get SQL Mgr to connect to it (this is even if I'm usin
g
> SM on the same machine as the SQL service).
> I can connect if instead of the IP address I use ".", but trying to connec
t
> via the IP address, no go.
> Anyone have a workaround for this?
> Thanks,
> CC
Include the port number in the hostname that you connect to, i.e.
myserver,1433
or
100.100.100.100,1433
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy:
Ah, thank you, I had been using a ':'
CC
"Tracy McKibben" wrote:

> cc wrote:
> Include the port number in the hostname that you connect to, i.e.
> myserver,1433
> or
> 100.100.100.100,1433
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Connecting is slow on just one machine, iSQLW, EM

We have one WinXP Client machine here that is having some issues connecting
to Any SQL Server...
We have tried with both TCP/IP-1433 and with NamedPipes with the same
results. in CNU we forced the connection with an Alias and had the same
results.
If we open EM, it takes about a minute to expand a server, and a bit more
then a minute to expand the Databases folder.
if I open iSQLw it takes for ever to connect to the DB, When I click the
drop down to select a DB, it takes 40+ seconds. Doing a Query on a Table
took 5 minutes...
On another machine sitting next to this one, we did the same tests.
Expanding the server took 2 seconds, DB same. iSQLw connected immediately
and the drop down did just that. The Query took 1 second....
If we look at the Data packets in a protocol analyzer it looks like the
machine thatis requesting the data from the SQL Server is requesting info
over and over and over and over... Where the one that work asks for it and
boom it all comes back.
We have a Custom App Written to use OLEDB and it works great on the machine.
Any suggestions?
Thanks,
Scott<-
Scott,
Could be an MDAC issue. You might want to reinstall MDAC 2.8 (I believe the
latest version for XP).
Steve
"Scott Townsend" <scott-i@..-N0-SPAMplease.enm.com> wrote in message
news:%23y7WbbYCFHA.4020@.TK2MSFTNGP15.phx.gbl...
> We have one WinXP Client machine here that is having some issues
connecting
> to Any SQL Server...
> We have tried with both TCP/IP-1433 and with NamedPipes with the same
> results. in CNU we forced the connection with an Alias and had the same
> results.
> If we open EM, it takes about a minute to expand a server, and a bit more
> then a minute to expand the Databases folder.
> if I open iSQLw it takes for ever to connect to the DB, When I click the
> drop down to select a DB, it takes 40+ seconds. Doing a Query on a Table
> took 5 minutes...
> On another machine sitting next to this one, we did the same tests.
> Expanding the server took 2 seconds, DB same. iSQLw connected immediately
> and the drop down did just that. The Query took 1 second....
>
> If we look at the Data packets in a protocol analyzer it looks like the
> machine thatis requesting the data from the SQL Server is requesting info
> over and over and over and over... Where the one that work asks for it
and
> boom it all comes back.
>
> We have a Custom App Written to use OLEDB and it works great on the
machine.
> Any suggestions?
> Thanks,
> Scott<-
>

Connecting client to SQL Server via Cisco VPN

We are having one client PC running Win XP. SQL Server has been set to
Windows Authentication, TCP/IP 1433, Windows 2003 (!).
Via Cisco VPN we are making a connection. IAS has been configurated, so the
local user profile doesn't matter. The server recognizes the user that is
part of the domain that has been defined at the server. So far so good.
When the user tries to connect via any client software (Enterprise Manager,
Query Analyzer, Access DAP) it sometimes fails. To do this test we used:
osql -l -S <hostname> -E
We have used several providers (dail-in, ADSL etc) and some of them works
fine, some not. You would probably say: use the one that works fine, but this
is not satisfying. Some client users are connected to a local network (no
dail in) and do also have the same problem.
The message we got is:
Login failed user '(null)'. Reason: not associated with trusted SQL Server
connection
I have seen at one of the Microsoft pages that we have to set the local
policies correct at the server where the domain has been defined (in case of
Windows 2003). We have done so. No results.
We first thought that it was a problem at the client, but since we have
proved that the same PC can connect to SQL it seems to be a networking
problem. We have also tried Named Pipes as a protocal but we did not succeed.
Since 50% of our clients are not able to connect (this is a world wide
application) we have serious problems. If anyone has any suggestion please
help us.
Thanks in advance
Jeroen
"Jeroen" <Jeroen@.discussions.microsoft.com> wrote in message
news:A750B079-A4AF-4B44-9A84-2E6A227B4029@.microsoft.com...
> We are having one client PC running Win XP. SQL Server has been set to
> Windows Authentication, TCP/IP 1433, Windows 2003 (!).
> Via Cisco VPN we are making a connection. IAS has been configurated, so
the
> local user profile doesn't matter. The server recognizes the user that is
> part of the domain that has been defined at the server. So far so good.
> When the user tries to connect via any client software (Enterprise
Manager,
> Query Analyzer, Access DAP) it sometimes fails. To do this test we used:
> osql -l -S <hostname> -E
> We have used several providers (dail-in, ADSL etc) and some of them works
> fine, some not. You would probably say: use the one that works fine, but
this
> is not satisfying. Some client users are connected to a local network (no
> dail in) and do also have the same problem.
> The message we got is:
> Login failed user '(null)'. Reason: not associated with trusted SQL Server
> connection
> I have seen at one of the Microsoft pages that we have to set the local
> policies correct at the server where the domain has been defined (in case
of
> Windows 2003). We have done so. No results.
> We first thought that it was a problem at the client, but since we have
> proved that the same PC can connect to SQL it seems to be a networking
> problem. We have also tried Named Pipes as a protocal but we did not
succeed.
> Since 50% of our clients are not able to connect (this is a world wide
> application) we have serious problems. If anyone has any suggestion please
> help us.
There are a number of areas that these clients could be failing... name
resolution, TCP ports being blocked, etc.. Perhaps this troubleshooting
guide will help:
How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/kb/827422
Steve
|||Thanks Steve,
The article helped us to get better focus on the issue. Instead of 50% of
the clients, almost all of them cannot connect when the try to establish a
connection via their local LAN.
We are almost sure that port 1433 is the problem. Since we got 3 dial in
providers 1 of them doesn't work. We have seen that NETSTAT -an shows us that
1433 is the problem. We have asked the provider and they have confirmed that
they give a random range of ports available.
Now the local LAN's... We have asked them to open port 1433 ingoing and
outgoing. But it still doesn't solve our problem. The VPN connection is
established via port 80 and this goes fine from any local LAN.
Windows authentication is chosen for a single point of entry. Some people do
not recommend this, but it is supported by Microsoft...
We are really lost, maybe someone has other ideas, maybe we can trace
somehow what goes wrong.
Regards,
Jeroen
"Steve Thompson" wrote:

> "Jeroen" <Jeroen@.discussions.microsoft.com> wrote in message
> news:A750B079-A4AF-4B44-9A84-2E6A227B4029@.microsoft.com...
> the
> Manager,
> this
> of
> succeed.
> There are a number of areas that these clients could be failing... name
> resolution, TCP ports being blocked, etc.. Perhaps this troubleshooting
> guide will help:
> How to troubleshoot connectivity issues in SQL Server 2000
> http://support.microsoft.com/kb/827422
> Steve
>
>

Connecting client to SQL Server via Cisco VPN

We are having one client PC running Win XP. SQL Server has been set to
Windows Authentication, TCP/IP 1433, Windows 2003 (!).
Via cisco VPN we are making a connection. IAS has been configurated, so the
local user profile doesn't matter. The server recognizes the user that is
part of the domain that has been defined at the server. So far so good.
When the user tries to connect via any client software (Enterprise Manager,
Query Analyzer, Access DAP) it sometimes fails. To do this test we used:
osql -l -S <hostname> -E
We have used several providers (dail-in, ADSL etc) and some of them works
fine, some not. You would probably say: use the one that works fine, but thi
s
is not satisfying. Some client users are connected to a local network (no
dail in) and do also have the same problem.
The message we got is:
Login failed user '(null)'. Reason: not associated with trusted SQL Server
connection
I have seen at one of the Microsoft pages that we have to set the local
policies correct at the server where the domain has been defined (in case of
Windows 2003). We have done so. No results.
We first thought that it was a problem at the client, but since we have
proved that the same PC can connect to SQL it seems to be a networking
problem. We have also tried Named Pipes as a protocal but we did not succeed
.
Since 50% of our clients are not able to connect (this is a world wide
application) we have serious problems. If anyone has any suggestion please
help us.
Thanks in advance
Jeroen"Jeroen" <Jeroen@.discussions.microsoft.com> wrote in message
news:A750B079-A4AF-4B44-9A84-2E6A227B4029@.microsoft.com...
> We are having one client PC running Win XP. SQL Server has been set to
> Windows Authentication, TCP/IP 1433, Windows 2003 (!).
> Via cisco VPN we are making a connection. IAS has been configurated, so
the
> local user profile doesn't matter. The server recognizes the user that is
> part of the domain that has been defined at the server. So far so good.
> When the user tries to connect via any client software (Enterprise
Manager,
> Query Analyzer, Access DAP) it sometimes fails. To do this test we used:
> osql -l -S <hostname> -E
> We have used several providers (dail-in, ADSL etc) and some of them works
> fine, some not. You would probably say: use the one that works fine, but
this
> is not satisfying. Some client users are connected to a local network (no
> dail in) and do also have the same problem.
> The message we got is:
> Login failed user '(null)'. Reason: not associated with trusted SQL Server
> connection
> I have seen at one of the Microsoft pages that we have to set the local
> policies correct at the server where the domain has been defined (in case
of
> Windows 2003). We have done so. No results.
> We first thought that it was a problem at the client, but since we have
> proved that the same PC can connect to SQL it seems to be a networking
> problem. We have also tried Named Pipes as a protocal but we did not
succeed.
> Since 50% of our clients are not able to connect (this is a world wide
> application) we have serious problems. If anyone has any suggestion please
> help us.
There are a number of areas that these clients could be failing... name
resolution, TCP ports being blocked, etc.. Perhaps this troubleshooting
guide will help:
How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/kb/827422
Steve|||Thanks Steve,
The article helped us to get better focus on the issue. Instead of 50% of
the clients, almost all of them cannot connect when the try to establish a
connection via their local LAN.
We are almost sure that port 1433 is the problem. Since we got 3 dial in
providers 1 of them doesn't work. We have seen that NETSTAT -an shows us tha
t
1433 is the problem. We have asked the provider and they have confirmed that
they give a random range of ports available.
Now the local LAN's... We have asked them to open port 1433 ingoing and
outgoing. But it still doesn't solve our problem. The VPN connection is
established via port 80 and this goes fine from any local LAN.
Windows authentication is chosen for a single point of entry. Some people do
not recommend this, but it is supported by Microsoft...
We are really lost, maybe someone has other ideas, maybe we can trace
somehow what goes wrong.
Regards,
Jeroen
"Steve Thompson" wrote:

> "Jeroen" <Jeroen@.discussions.microsoft.com> wrote in message
> news:A750B079-A4AF-4B44-9A84-2E6A227B4029@.microsoft.com...
> the
> Manager,
> this
> of
> succeed.
> There are a number of areas that these clients could be failing... name
> resolution, TCP ports being blocked, etc.. Perhaps this troubleshooting
> guide will help:
> How to troubleshoot connectivity issues in SQL Server 2000
> http://support.microsoft.com/kb/827422
> Steve
>
>

Connect with TCP

Hello,
I hope I'm posting this in the right group.
I'm trying to connect to a network server running Sql Server 2005 Express
from vb 2005. I can connect to it when I use:
DATA SOURCE=<servername>\SQLEXPRESS;INITIAL CATALOG=<cat>;Integrated
Security=SSPI;
However I need to be able to connect to it from the internet using TCP. I
have openned port 1433 on my firewall. I have set the server to allow remote
connections and it still comes back with an error when i trie to connect. I
have even tried using this on my local network. Here is my connection string:
Data Source=192.168.0.xxx,1433;Network Library=DBMSSOCN;Initial
Catalog=<cat>;User ID=<user>;Password=<password>;
Any help would be appreciated.
Figured it out. Might help if I use the correct IP Address!
"Jason" wrote:

> Hello,
> I hope I'm posting this in the right group.
> I'm trying to connect to a network server running Sql Server 2005 Express
> from vb 2005. I can connect to it when I use:
> DATA SOURCE=<servername>\SQLEXPRESS;INITIAL CATALOG=<cat>;Integrated
> Security=SSPI;
> However I need to be able to connect to it from the internet using TCP. I
> have openned port 1433 on my firewall. I have set the server to allow remote
> connections and it still comes back with an error when i trie to connect. I
> have even tried using this on my local network. Here is my connection string:
> Data Source=192.168.0.xxx,1433;Network Library=DBMSSOCN;Initial
> Catalog=<cat>;User ID=<user>;Password=<password>;
> Any help would be appreciated.
>

Connect with TCP

Hello,
I hope I'm posting this in the right group.
I'm trying to connect to a network server running Sql Server 2005 Express
from vb 2005. I can connect to it when I use:
DATA SOURCE=<servername>\SQLEXPRESS;INITIAL CATALOG=<cat>;Integrated
Security=SSPI;
However I need to be able to connect to it from the internet using TCP. I
have openned port 1433 on my firewall. I have set the server to allow remote
connections and it still comes back with an error when i trie to connect. I
have even tried using this on my local network. Here is my connection string
:
Data Source=192.168.0.xxx,1433;Network Library=DBMSSOCN;Initial
Catalog=<cat>;User ID=<user>;Password=<password>;
Any help would be appreciated.Figured it out. Might help if I use the correct IP Address!
"Jason" wrote:

> Hello,
> I hope I'm posting this in the right group.
> I'm trying to connect to a network server running Sql Server 2005 Express
> from vb 2005. I can connect to it when I use:
> DATA SOURCE=<servername>\SQLEXPRESS;INITIAL CATALOG=<cat>;Integrated
> Security=SSPI;
> However I need to be able to connect to it from the internet using TCP. I
> have openned port 1433 on my firewall. I have set the server to allow remo
te
> connections and it still comes back with an error when i trie to connect.
I
> have even tried using this on my local network. Here is my connection stri
ng:
> Data Source=192.168.0.xxx,1433;Network Library=DBMSSOCN;Initial
> Catalog=<cat>;User ID=<user>;Password=<password>;
> Any help would be appreciated.
>

Connect to SSAS on TCP/IP using Java + execute XMLA

Hi,

I have done this in .Net, but that is easy because you get .Net libraries to help you connect and send XMLA over TCP/IP.

I would want to do the same using Java:

Connect to SSAS 2005 on TCP/IP, or even SOAP over TCP/IP

Then execute XMLA commands

and retrieve XMLA responses.

How to accomplish this?

Regards

Vijay R

The TCP/IP bindings to XMLA that AS use as proprietrary and also patented, therefore you cannot connect directly over TCP/IP to AS. You can use HTTP instead.|||

Hi Mosha,

Thanks a lot,

But to use HTTP we need to use IIS,

any other way to do this?

Regards

Vijay R

|||

But to use HTTP we need to use IIS

Yes. What is a problem with using IIS ?

|||

Hi Mosha,

Thanks for the quick reply,

No problem with IIS, but the dependency increases and my customer does not want to spend extra on another server.

They use java based servers like JMS.

I have told them that either we need to use AMO.Net in an .Net code or use IIS.

The problem is because of the xmla specification and ssas 2005 information given in books,

My customer points out to me that we can do an SOAP over tcp/ip and pass XMLA commands, as printed in the books!

I am not finding a valid technical angle to tackle this.

apart from that I had another related question:

we can use oledb and connect to ssas2005, right?

1) can we pass xmla commands using oledb? command like <Create>, <Alter> etc

2) the new jdbc driver for sql 2005, does it allow to connect to ssas 2005?

Thanks once more mosha

Regards

|||

No problem with IIS, but the dependency increases and my customer does not want to spend extra on another server

There is no need to spend extra on another server. You can have IIS and Analysis Services server on the same machine.

My customer points out to me that we can do an SOAP over tcp/ip and pass XMLA commands, as printed in the books!

Your customer is wrong. He cannot do that. Microsoft's OLEDB driver and ADOMD.NET can do that, but as I pointed earlier the TCP/IP bindings to XMLA are proprietrary and patent protected.

we can use oledb and connect to ssas2005, right?

Correct

1) can we pass xmla commands using oledb? command like <Create>, <Alter> etc

Yes

2) the new jdbc driver for sql 2005, does it allow to connect to ssas 2005?

No

|||

Hi Mosha,

Thanks a lot :-)

I have been quite a fan of yours!! I am currently in the US, any chance that you are here?

If possible, I was hoping to meet you.

No problem anyway, bye

Thanks again.

Regards

Vijay R

|||

Hi Mosha,

I can java, but donn't like it, therevore i use .Net pure and can communicate with SSAS through XMLA over TCP from my own code without adomd.net and other proprietary junk. Yes I haven't compression and encription, but it runs!!!

What law I break?

|||

Hi,

I tried some java code,

that opens a socket connection and sends the xmla in a soap envelope as a string.

but the connections itself in ssas profiler displays as anonymous logon,

the query does not come through to the server at all !

Regards

Vijay R

|||

Hi all,

When reading the following statements by Mosha, i was very excited:

we can use oledb and connect to ssas2005, right?

Correct

1) can we pass xmla commands using oledb? command like <Create>, <Alter> etc

Yes

Then I had to ask... How? Do I need to use a different provider / connection string? Do I need to wrap my XMLA in anything? Where can I find further information on this.

Thankyou

Aranda

|||

You should send SSPI handshacke info. How to obtain it in java I don't know. In the .Net it is pretty easy.

|||

Hi,

can you please explain in detail as to how to send the SSPI handshake info In a .net program?

it would be helpful if you can give a code snippet that expains the procesure.

Regards

|||

Hi,

Mosha wrote "as I pointed earlier the TCP/IP bindings to XMLA are proprietrary and patent protected."

Therefore here is not a right place to speak it about.

Regards

|||

:-)

So how about this Vladimir Chtepa: vijay_rb@.yahoo.com

in any case, thanks for the interaction.

Regards

Connect to SSAS on TCP/IP using Java + execute XMLA

Hi,

I have done this in .Net, but that is easy because you get .Net libraries to help you connect and send XMLA over TCP/IP.

I would want to do the same using Java:

Connect to SSAS 2005 on TCP/IP, or even SOAP over TCP/IP

Then execute XMLA commands

and retrieve XMLA responses.

How to accomplish this?

Regards

Vijay R

The TCP/IP bindings to XMLA that AS use as proprietrary and also patented, therefore you cannot connect directly over TCP/IP to AS. You can use HTTP instead.|||

Hi Mosha,

Thanks a lot,

But to use HTTP we need to use IIS,

any other way to do this?

Regards

Vijay R

|||

But to use HTTP we need to use IIS

Yes. What is a problem with using IIS ?

|||

Hi Mosha,

Thanks for the quick reply,

No problem with IIS, but the dependency increases and my customer does not want to spend extra on another server.

They use java based servers like JMS.

I have told them that either we need to use AMO.Net in an .Net code or use IIS.

The problem is because of the xmla specification and ssas 2005 information given in books,

My customer points out to me that we can do an SOAP over tcp/ip and pass XMLA commands, as printed in the books!

I am not finding a valid technical angle to tackle this.

apart from that I had another related question:

we can use oledb and connect to ssas2005, right?

1) can we pass xmla commands using oledb? command like <Create>, <Alter> etc

2) the new jdbc driver for sql 2005, does it allow to connect to ssas 2005?

Thanks once more mosha

Regards

|||

No problem with IIS, but the dependency increases and my customer does not want to spend extra on another server

There is no need to spend extra on another server. You can have IIS and Analysis Services server on the same machine.

My customer points out to me that we can do an SOAP over tcp/ip and pass XMLA commands, as printed in the books!

Your customer is wrong. He cannot do that. Microsoft's OLEDB driver and ADOMD.NET can do that, but as I pointed earlier the TCP/IP bindings to XMLA are proprietrary and patent protected.

we can use oledb and connect to ssas2005, right?

Correct

1) can we pass xmla commands using oledb? command like <Create>, <Alter> etc

Yes

2) the new jdbc driver for sql 2005, does it allow to connect to ssas 2005?

No

|||

Hi Mosha,

Thanks a lot :-)

I have been quite a fan of yours!! I am currently in the US, any chance that you are here?

If possible, I was hoping to meet you.

No problem anyway, bye

Thanks again.

Regards

Vijay R

|||

Hi Mosha,

I can java, but donn't like it, therevore i use .Net pure and can communicate with SSAS through XMLA over TCP from my own code without adomd.net and other proprietary junk. Yes I haven't compression and encription, but it runs!!!

What law I break?

|||

Hi,

I tried some java code,

that opens a socket connection and sends the xmla in a soap envelope as a string.

but the connections itself in ssas profiler displays as anonymous logon,

the query does not come through to the server at all !

Regards

Vijay R

|||

Hi all,

When reading the following statements by Mosha, i was very excited:

we can use oledb and connect to ssas2005, right?

Correct

1) can we pass xmla commands using oledb? command like <Create>, <Alter> etc

Yes

Then I had to ask... How? Do I need to use a different provider / connection string? Do I need to wrap my XMLA in anything? Where can I find further information on this.

Thankyou

Aranda

|||

You should send SSPI handshacke info. How to obtain it in java I don't know. In the .Net it is pretty easy.

|||

Hi,

can you please explain in detail as to how to send the SSPI handshake info In a .net program?

it would be helpful if you can give a code snippet that expains the procesure.

Regards

|||

Hi,

Mosha wrote "as I pointed earlier the TCP/IP bindings to XMLA are proprietrary and patent protected."

Therefore here is not a right place to speak it about.

Regards

|||

:-)

So how about this Vladimir Chtepa: vijay_rb@.yahoo.com

in any case, thanks for the interaction.

Regards

Connect to SSAS on TCP/IP using Java + execute XMLA

Hi,

I have done this in .Net, but that is easy because you get .Net libraries to help you connect and send XMLA over TCP/IP.

I would want to do the same using Java:

Connect to SSAS 2005 on TCP/IP, or even SOAP over TCP/IP

Then execute XMLA commands

and retrieve XMLA responses.

How to accomplish this?

Regards

Vijay R

The TCP/IP bindings to XMLA that AS use as proprietrary and also patented, therefore you cannot connect directly over TCP/IP to AS. You can use HTTP instead.|||

Hi Mosha,

Thanks a lot,

But to use HTTP we need to use IIS,

any other way to do this?

Regards

Vijay R

|||

But to use HTTP we need to use IIS

Yes. What is a problem with using IIS ?

|||

Hi Mosha,

Thanks for the quick reply,

No problem with IIS, but the dependency increases and my customer does not want to spend extra on another server.

They use java based servers like JMS.

I have told them that either we need to use AMO.Net in an .Net code or use IIS.

The problem is because of the xmla specification and ssas 2005 information given in books,

My customer points out to me that we can do an SOAP over tcp/ip and pass XMLA commands, as printed in the books!

I am not finding a valid technical angle to tackle this.

apart from that I had another related question:

we can use oledb and connect to ssas2005, right?

1) can we pass xmla commands using oledb? command like <Create>, <Alter> etc

2) the new jdbc driver for sql 2005, does it allow to connect to ssas 2005?

Thanks once more mosha

Regards

|||

No problem with IIS, but the dependency increases and my customer does not want to spend extra on another server

There is no need to spend extra on another server. You can have IIS and Analysis Services server on the same machine.

My customer points out to me that we can do an SOAP over tcp/ip and pass XMLA commands, as printed in the books!

Your customer is wrong. He cannot do that. Microsoft's OLEDB driver and ADOMD.NET can do that, but as I pointed earlier the TCP/IP bindings to XMLA are proprietrary and patent protected.

we can use oledb and connect to ssas2005, right?

Correct

1) can we pass xmla commands using oledb? command like <Create>, <Alter> etc

Yes

2) the new jdbc driver for sql 2005, does it allow to connect to ssas 2005?

No

|||

Hi Mosha,

Thanks a lot :-)

I have been quite a fan of yours!! I am currently in the US, any chance that you are here?

If possible, I was hoping to meet you.

No problem anyway, bye

Thanks again.

Regards

Vijay R

|||

Hi Mosha,

I can java, but donn't like it, therevore i use .Net pure and can communicate with SSAS through XMLA over TCP from my own code without adomd.net and other proprietary junk. Yes I haven't compression and encription, but it runs!!!

What law I break?

|||

Hi,

I tried some java code,

that opens a socket connection and sends the xmla in a soap envelope as a string.

but the connections itself in ssas profiler displays as anonymous logon,

the query does not come through to the server at all !

Regards

Vijay R

|||

Hi all,

When reading the following statements by Mosha, i was very excited:

we can use oledb and connect to ssas2005, right?

Correct

1) can we pass xmla commands using oledb? command like <Create>, <Alter> etc

Yes

Then I had to ask... How? Do I need to use a different provider / connection string? Do I need to wrap my XMLA in anything? Where can I find further information on this.

Thankyou

Aranda

|||

You should send SSPI handshacke info. How to obtain it in java I don't know. In the .Net it is pretty easy.

|||

Hi,

can you please explain in detail as to how to send the SSPI handshake info In a .net program?

it would be helpful if you can give a code snippet that expains the procesure.

Regards

|||

Hi,

Mosha wrote "as I pointed earlier the TCP/IP bindings to XMLA are proprietrary and patent protected."

Therefore here is not a right place to speak it about.

Regards

|||

:-)

So how about this Vladimir Chtepa: vijay_rb@.yahoo.com

in any case, thanks for the interaction.

Regards

Connect to SQL-Databas over TCP/IP

Hi..

I am really new in C# Programming witf h Database. My problem is:

I have a SQL Database (in an other country) and My Application has to connect it for data transfer. How can I do that? Which alternatives do i have. Should I use a Web Service?

Thanks...

Hi,

You could use the following connection string;

Provider=sqloledb;Data Source=190.190.200.100,1433;Network Library=DBMSSOC;Initial Catalog=myDataBas;User ID=myUsername;Password=myPassword;

Obviously you will have to change the IP address to that of the server where SQL resides... also make sure you have the correct port which is the value after the comma (,) on the IP address