can we connect?

can we connect named instance through IP like in the network utility I just
defined the IP of the server where the named instance installed and define
the port...
Client Netowork Utility > Alias >
Alias: MyServer
Server: 209.45.23.55
Port : 1434
Protocol: TCP/IP
any thing else I need to do for connecting this... I did the above stuff but
I had failed to connect but why I can connect the default instance... please
guide me..
Thanks and I would highly appreciate if your prompt reply
thanks and have a great day
Hi,
Open the SQL Server error log under the folder
SQL_Server_installation_path>X\MSSQL$instance_name \LOG folder to make sure
that the SQL Server named instance runs well and to find the TCP port which
this named instance is listening.
As well as using Server network utility verify TCP/IP protocol is enabled.
Get the SQL Server name from Error log and use that name to connect from
query analyzer
Thanks
Hari
SQL Server MVP
"Rogers" <Rogers@.discussions.microsoft.com> wrote in message
news:DC15100C-5AC0-4C51-9CA3-8527DBF3DC23@.microsoft.com...
> can we connect named instance through IP like in the network utility I
> just
> defined the IP of the server where the named instance installed and define
> the port...
> Client Netowork Utility > Alias >
> Alias: MyServer
> Server: 209.45.23.55
> Port : 1434
> Protocol: TCP/IP
> any thing else I need to do for connecting this... I did the above stuff
> but
> I had failed to connect but why I can connect the default instance...
> please
> guide me..
> Thanks and I would highly appreciate if your prompt reply
> thanks and have a great day
>
|||First of all Hari, thanks for your reply... I can easily connect the named
instance on that same machine ... I am trying to connect that named instance
through my client machine and facing this problem...
"Hari Prasad" wrote:

> Hi,
> Open the SQL Server error log under the folder
> SQL_Server_installation_path>X\MSSQL$instance_nam e\LOG folder to make sure
> that the SQL Server named instance runs well and to find the TCP port which
> this named instance is listening.
> As well as using Server network utility verify TCP/IP protocol is enabled.
> Get the SQL Server name from Error log and use that name to connect from
> query analyzer
> Thanks
> Hari
> SQL Server MVP
>
> "Rogers" <Rogers@.discussions.microsoft.com> wrote in message
> news:DC15100C-5AC0-4C51-9CA3-8527DBF3DC23@.microsoft.com...
>
>

Can we connect to SQL server 2000 through Internet using a static IP?

Dear All,
Can we connect to SQL Server 2000 through internet using static ip?
We have a static IP in our office and we would like one of our customer to
connect to our database using this static IP. Is this possible?
Regards,
Peri> Can we connect to SQL Server 2000 through internet using static ip?
> We have a static IP in our office and we would like one of our customer to
> connect to our database using this static IP. Is this possible?
Yes, but typically not recommended. Without a firewall in place explicitly
allowing that specific IP in, your database is exposed to everyone on the
Internet.
So, the question on my mind is, have you tried it?
A|||Thanks a lot.
But can you please tell me which port should I open?
Regards,
Peri
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:uXu0vpemGHA.2316@.TK2MSFTNGP04.phx.gbl...
> Peri wrote:
> Certainly possible, but use extreme caution. Doing this will require an
> open port through your firewall. Opening that port will expose your
> server to the outside world. I would HIGHLY recommend configuring a
> firewall rule to allow ONLY connections from your customer's IP to connect
> to the newly opened port. Get your network people involved to make sure
> this is done securely.

Can we connect to SQL server 2000 through Internet using a static

Peri wrote:
> Dear All,
> Can we connect to SQL Server 2000 through internet using static ip?
> We have a static IP in our office and we would like one of our customer to
> connect to our database using this static IP. Is this possible?
> Regards,
> Peri
>
Certainly possible, but use extreme caution. Doing this will require an
open port through your firewall. Opening that port will expose your
server to the outside world. I would HIGHLY recommend configuring a
firewall rule to allow ONLY connections from your customer's IP to
connect to the newly opened port. Get your network people involved to
make sure this is done securely.Peri wrote:
> Thanks a lot.
> But can you please tell me which port should I open?
> Regards,
> Peri
>
Unless you changed it during the SQL Server install, it's the default
port 1433. Confirm with "netstat -a" at the command prompt.

Can the SQL Server Managament Studio connect to ODBC sources?

Hi,
Can the SQL Server Managament Studio connect to ODBC sources?
If so, how do you do it? I've not done much with ODBC before...
Thanks,
Alan
http://www.sadevelopment.com
Partition Boot Manager and Large Drive Tools utilities!SSMS does not use the ODBC API. However, you can connect to any SQL Server
via SSMS as long as you know the server name and login credentials. You can
get that information by viewing the properties of the existing SQL Server
ODBC data source or connection string.
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4623694e$0$23404$c3e8da3@.news.astraweb.com...
> Hi,
> Can the SQL Server Managament Studio connect to ODBC sources?
> If so, how do you do it? I've not done much with ODBC before...
> Thanks,
> Alan
> http://www.sadevelopment.com
> Partition Boot Manager and Large Drive Tools utilities!
>|||Hi Dan,

> SSMS does not use the ODBC API. However, you can connect to any SQL
> Server via SSMS as long as you know the server name and login credentials.
> You can get that information by viewing the properties of the existing SQL
> Server ODBC data source or connection string.
Too bad, I was hoping to connect to ODBC with it. Does anyone have any idea
what tool or tools I could use to connect and troubleshoot ODBC...
Alan
http://www.sadevelopment.com
Partition Boot Manager and Large Drive Tools utilities!|||Can you elaborate on what you mean by "connect and troubleshoot ODBC"? If
you are trying to test ODBC data source connectivity, the ODBC data source
setup has a button to test the connection.
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4623b9c6$0$873$c3e8da3@.news.astraweb.com...
> Hi Dan,
>
> Too bad, I was hoping to connect to ODBC with it. Does anyone have any
> idea what tool or tools I could use to connect and troubleshoot ODBC...
> Alan
> http://www.sadevelopment.com
> Partition Boot Manager and Large Drive Tools utilities!
>|||Hi,

> Can you elaborate on what you mean by "connect and troubleshoot ODBC"? If
> you are trying to test ODBC data source connectivity, the ODBC data source
> setup has a button to test the connection.
Yes, I'm looking for a tool that lets you connect to ODBC and use it much
the way the SQL management studio lets you connect to MSSQL...
Thanks,
Alan|||> Yes, I'm looking for a tool that lets you connect to ODBC and use it much
> the way the SQL management studio lets you connect to MSSQL...
So you need to query ODBC data sources other than Micosoft SQL Server? If
you need only SQL Server, I still don't understand why you have the ODBC
requirement.
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4627a5d7$0$4674$c3e8da3@.news.astraweb.com...
> Hi,
>
> Yes, I'm looking for a tool that lets you connect to ODBC and use it much
> the way the SQL management studio lets you connect to MSSQL...
> Thanks,
> Alan
>

Can the SQL Server Managament Studio connect to ODBC sources?

Hi,
Can the SQL Server Managament Studio connect to ODBC sources?
If so, how do you do it? I've not done much with ODBC before...
Thanks,
Alan
http://www.sadevelopment.com
Partition Boot Manager and Large Drive Tools utilities!
SSMS does not use the ODBC API. However, you can connect to any SQL Server
via SSMS as long as you know the server name and login credentials. You can
get that information by viewing the properties of the existing SQL Server
ODBC data source or connection string.
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4623694e$0$23404$c3e8da3@.news.astraweb.com...
> Hi,
> Can the SQL Server Managament Studio connect to ODBC sources?
> If so, how do you do it? I've not done much with ODBC before...
> Thanks,
> Alan
> http://www.sadevelopment.com
> Partition Boot Manager and Large Drive Tools utilities!
>
|||Hi Dan,

> SSMS does not use the ODBC API. However, you can connect to any SQL
> Server via SSMS as long as you know the server name and login credentials.
> You can get that information by viewing the properties of the existing SQL
> Server ODBC data source or connection string.
Too bad, I was hoping to connect to ODBC with it. Does anyone have any idea
what tool or tools I could use to connect and troubleshoot ODBC...
Alan
http://www.sadevelopment.com
Partition Boot Manager and Large Drive Tools utilities!
|||Can you elaborate on what you mean by "connect and troubleshoot ODBC"? If
you are trying to test ODBC data source connectivity, the ODBC data source
setup has a button to test the connection.
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4623b9c6$0$873$c3e8da3@.news.astraweb.com...
> Hi Dan,
>
> Too bad, I was hoping to connect to ODBC with it. Does anyone have any
> idea what tool or tools I could use to connect and troubleshoot ODBC...
> Alan
> http://www.sadevelopment.com
> Partition Boot Manager and Large Drive Tools utilities!
>
|||Hi,

> Can you elaborate on what you mean by "connect and troubleshoot ODBC"? If
> you are trying to test ODBC data source connectivity, the ODBC data source
> setup has a button to test the connection.
Yes, I'm looking for a tool that lets you connect to ODBC and use it much
the way the SQL management studio lets you connect to MSSQL...
Thanks,
Alan
|||> Yes, I'm looking for a tool that lets you connect to ODBC and use it much
> the way the SQL management studio lets you connect to MSSQL...
So you need to query ODBC data sources other than Micosoft SQL Server? If
you need only SQL Server, I still don't understand why you have the ODBC
requirement.
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4627a5d7$0$4674$c3e8da3@.news.astraweb.com...
> Hi,
>
> Yes, I'm looking for a tool that lets you connect to ODBC and use it much
> the way the SQL management studio lets you connect to MSSQL...
> Thanks,
> Alan
>

Can the SQL Server Managament Studio connect to ODBC sources?

Hi,
Can the SQL Server Managament Studio connect to ODBC sources?
If so, how do you do it? I've not done much with ODBC before...
Thanks,
Alan
http://www.sadevelopment.com
Partition Boot Manager and Large Drive Tools utilities!SSMS does not use the ODBC API. However, you can connect to any SQL Server
via SSMS as long as you know the server name and login credentials. You can
get that information by viewing the properties of the existing SQL Server
ODBC data source or connection string.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4623694e$0$23404$c3e8da3@.news.astraweb.com...
> Hi,
> Can the SQL Server Managament Studio connect to ODBC sources?
> If so, how do you do it? I've not done much with ODBC before...
> Thanks,
> Alan
> http://www.sadevelopment.com
> Partition Boot Manager and Large Drive Tools utilities!
>|||Hi Dan,
> SSMS does not use the ODBC API. However, you can connect to any SQL
> Server via SSMS as long as you know the server name and login credentials.
> You can get that information by viewing the properties of the existing SQL
> Server ODBC data source or connection string.
Too bad, I was hoping to connect to ODBC with it. Does anyone have any idea
what tool or tools I could use to connect and troubleshoot ODBC...
Alan
http://www.sadevelopment.com
Partition Boot Manager and Large Drive Tools utilities!|||Can you elaborate on what you mean by "connect and troubleshoot ODBC"? If
you are trying to test ODBC data source connectivity, the ODBC data source
setup has a button to test the connection.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4623b9c6$0$873$c3e8da3@.news.astraweb.com...
> Hi Dan,
>> SSMS does not use the ODBC API. However, you can connect to any SQL
>> Server via SSMS as long as you know the server name and login
>> credentials. You can get that information by viewing the properties of
>> the existing SQL Server ODBC data source or connection string.
> Too bad, I was hoping to connect to ODBC with it. Does anyone have any
> idea what tool or tools I could use to connect and troubleshoot ODBC...
> Alan
> http://www.sadevelopment.com
> Partition Boot Manager and Large Drive Tools utilities!
>|||Hi,
> Can you elaborate on what you mean by "connect and troubleshoot ODBC"? If
> you are trying to test ODBC data source connectivity, the ODBC data source
> setup has a button to test the connection.
Yes, I'm looking for a tool that lets you connect to ODBC and use it much
the way the SQL management studio lets you connect to MSSQL...
Thanks,
Alan|||> Yes, I'm looking for a tool that lets you connect to ODBC and use it much
> the way the SQL management studio lets you connect to MSSQL...
So you need to query ODBC data sources other than Micosoft SQL Server? If
you need only SQL Server, I still don't understand why you have the ODBC
requirement.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Default User" <nospam38925@.forme.com> wrote in message
news:4627a5d7$0$4674$c3e8da3@.news.astraweb.com...
> Hi,
>> Can you elaborate on what you mean by "connect and troubleshoot ODBC"?
>> If you are trying to test ODBC data source connectivity, the ODBC data
>> source setup has a button to test the connection.
> Yes, I'm looking for a tool that lets you connect to ODBC and use it much
> the way the SQL management studio lets you connect to MSSQL...
> Thanks,
> Alan
>

Can the JDBC Driver provided by Microsoft connect MSDE?

I plan to use MSDE because it sues my needs, but doese the
JDBC provided by MS connect to MSDE?
Yes, you can connect to an MSDE instance. You will have to specify the
instance name using the <servername>\<instancename> syntax in your
connection URL.
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
"Benny" <BennyInCanada2883@.hotmail.com> wrote in message
news:13cfc01c412b1$60b8ed60$a101280a@.phx.gbl...
> I plan to use MSDE because it sues my needs, but doese the
> JDBC provided by MS connect to MSDE?

Can SQL Server Connect with pcAnywhere?

If I establish a remove connection to a server with pcAnywhere, will I be
able to connect to SQL Server on that server programatically or with
Enterprise Manager?
Thanks for any help,
WayneM
To the best of my knowledge PCAnywhere is not like a VPN in that it allows
connections from your PC to the remote one. It simply allows you to control
the remote desktop as if you were there. So if you run EM on the remote
server via PCAnywhere then sure. But I don't think you can run EM from your
machine against the remote one if that is the only connection.
Andrew J. Kelly SQL MVP
"WayneM" <WayneM@.discussions.microsoft.com> wrote in message
news:1D919B19-5C5A-4242-B826-961BD215FE18@.microsoft.com...
> If I establish a remove connection to a server with pcAnywhere, will I be
> able to connect to SQL Server on that server programatically or with
> Enterprise Manager?
> Thanks for any help,
> WayneM
|||Just want to add.
Usually, though, before you can use software like pcAnywhere, RAdmin,
RemoteDesktop, and so on, you would have to establish some kind of 'trusted'
network connection first. Often, that would be VPN. So because of that, you
should be able to run your EM or any SQL Server client from your remote PC.
But I'm just speaking from my experience with the environments I have worked
with, and yours may differ.
Linchi
"WayneM" wrote:

> If I establish a remove connection to a server with pcAnywhere, will I be
> able to connect to SQL Server on that server programatically or with
> Enterprise Manager?
> Thanks for any help,
> WayneM
|||Good point Linchi.
Andrew J. Kelly SQL MVP
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C40DA762-A8ED-4F2F-B292-0A1FF804074E@.microsoft.com...[vbcol=seagreen]
> Just want to add.
> Usually, though, before you can use software like pcAnywhere, RAdmin,
> RemoteDesktop, and so on, you would have to establish some kind of
> 'trusted'
> network connection first. Often, that would be VPN. So because of that,
> you
> should be able to run your EM or any SQL Server client from your remote
> PC.
> But I'm just speaking from my experience with the environments I have
> worked
> with, and yours may differ.
> Linchi
> "WayneM" wrote:

Can SQL Server Connect with pcAnywhere?

If I establish a remove connection to a server with pcAnywhere, will I be
able to connect to SQL Server on that server programatically or with
Enterprise Manager?
Thanks for any help,
WayneMTo the best of my knowledge PCAnywhere is not like a VPN in that it allows
connections from your PC to the remote one. It simply allows you to control
the remote desktop as if you were there. So if you run EM on the remote
server via PCAnywhere then sure. But I don't think you can run EM from your
machine against the remote one if that is the only connection.
Andrew J. Kelly SQL MVP
"WayneM" <WayneM@.discussions.microsoft.com> wrote in message
news:1D919B19-5C5A-4242-B826-961BD215FE18@.microsoft.com...
> If I establish a remove connection to a server with pcAnywhere, will I be
> able to connect to SQL Server on that server programatically or with
> Enterprise Manager?
> Thanks for any help,
> WayneM|||Just want to add.
Usually, though, before you can use software like pcAnywhere, RAdmin,
RemoteDesktop, and so on, you would have to establish some kind of 'trusted'
network connection first. Often, that would be VPN. So because of that, you
should be able to run your EM or any SQL Server client from your remote PC.
But I'm just speaking from my experience with the environments I have worked
with, and yours may differ.
Linchi
"WayneM" wrote:

> If I establish a remove connection to a server with pcAnywhere, will I be
> able to connect to SQL Server on that server programatically or with
> Enterprise Manager?
> Thanks for any help,
> WayneM|||Good point Linchi.
Andrew J. Kelly SQL MVP
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C40DA762-A8ED-4F2F-B292-0A1FF804074E@.microsoft.com...[vbcol=seagreen]
> Just want to add.
> Usually, though, before you can use software like pcAnywhere, RAdmin,
> RemoteDesktop, and so on, you would have to establish some kind of
> 'trusted'
> network connection first. Often, that would be VPN. So because of that,
> you
> should be able to run your EM or any SQL Server client from your remote
> PC.
> But I'm just speaking from my experience with the environments I have
> worked
> with, and yours may differ.
> Linchi
> "WayneM" wrote:
>

Can SQL Query Analizer be desactivated?

Hi,

I have a weird situation I hope you can help me. When SQL Query Analizer is opened it displays a Window asking if you want to connect using Windows Authentication Mode or SQL Server mode.

Do you know if there is a way to desactivate the SQL Server mode, I mean that only the Windows Authentication Mode be enabled when Query Analizer is run.

I dont want users be able to connect with the SQL Query Analizer using a SQL Server password (there is a Sql user in the server and most of the developers know him), only by Windows Auth. Mode.

- Please help -

ThanksYour problem is not with Query Analyzer. If you block that, you still have to worry about people making connections through MS Access, the OSQL command line utility, or other methods. If you are really concerned about this, you can change your server so that it only allows NT security connections. At the moment, your server is likely in "mixed security" mode.

Regardless, you should be able to modify the SQL Server account for the user and either delete it or restrict it's access.

blindman|||Thanks Blindman, I know my problem is with the SQL Server configuration. The main problem is that there is a client application that it uses a SQL Server user and it can be disabled without modifying the client, that's why the server is in Mixed mode, but I don't want Developers enter to the production environment with that user.

It would be like a temp fix disabling the SQL Query Analizer, of course if there is a way.|||Hi have a look at Application Security Roles this may be what you require.|||You can't control database access through Query Analyzer. Consider that even if there is a Query Analyzer option that disabled SQL Server logins, you would have to enforce this on every copy of Query Analyzer and you'd have no way to prevent users from changing it back.

Are you concerned about users modifying data through Query Analyzer, or just about them modifiying the database schema? Make sure the login does not have permission to modify the database schema (the application shouldn't require this in order to function), and then if you need data security then Application Security roles are the way to go.

blindman|||Thanks for your comments. My concern is that developers modify data using the query analizer, it looks like Application Roles is the way to go but since the developers have the source code they would know the Application password to activate the role, well I think I could create a COM Object in the server to make the connection, so developers don't have access to the password of the role.

can see sql2k sp3, but cannot connect?

With Enterprise manager, I can see a remote sql 2000 sp3 instance. I can al
so
see that port 1433 is open.
But, when I try to connect to it, I get the connection could not be
estiablished.
sql server does not exist or access denied.
I have pretty much all the port except for 1433 tcp and udp blocked.
How can I troubleshoot getting this connected. It is located on my local
network - so it is not a connection problem.
--
Thanks in advance, Les CaudleI think it was a name resolution problem, with so few ports open.
When I created a registration by ip address rather than name, it connected
immediately.
Confusing that the name showed up in Enterprise Manager. Would be nice if i
t
would automatically try to use just the ip (which it must know, as it can se
e
it).
On Wed, 18 Aug 2004 19:17:14 -0500, Les Caudle <very@.tiredofspam.com> wrote:

>With Enterprise manager, I can see a remote sql 2000 sp3 instance. I can a
lso
>see that port 1433 is open.
>But, when I try to connect to it, I get the connection could not be
>estiablished.
>sql server does not exist or access denied.
>I have pretty much all the port except for 1433 tcp and udp blocked.
>How can I troubleshoot getting this connected. It is located on my local
>network - so it is not a connection problem.

can see sql2k sp3, but cannot connect?

With Enterprise manager, I can see a remote sql 2000 sp3 instance. I can also
see that port 1433 is open.
But, when I try to connect to it, I get the connection could not be
estiablished.
sql server does not exist or access denied.
I have pretty much all the port except for 1433 tcp and udp blocked.
How can I troubleshoot getting this connected. It is located on my local
network - so it is not a connection problem.
Thanks in advance, Les Caudle
I think it was a name resolution problem, with so few ports open.
When I created a registration by ip address rather than name, it connected
immediately.
Confusing that the name showed up in Enterprise Manager. Would be nice if it
would automatically try to use just the ip (which it must know, as it can see
it).
On Wed, 18 Aug 2004 19:17:14 -0500, Les Caudle <very@.tiredofspam.com> wrote:

>With Enterprise manager, I can see a remote sql 2000 sp3 instance. I can also
>see that port 1433 is open.
>But, when I try to connect to it, I get the connection could not be
>estiablished.
>sql server does not exist or access denied.
>I have pretty much all the port except for 1433 tcp and udp blocked.
>How can I troubleshoot getting this connected. It is located on my local
>network - so it is not a connection problem.

can Profiler display port number?

Where - in SQL Server Profiler - can I see the port number that someone has used to connect to a database?

e.g. given the connect string "tcp:MACHINE1\INSTANCE7,3045" - where in Profiler does it tell me that the connection is using port 3045? I looked at "audit login" and "existing connection" but I don't see a port number...

Any other SQL/Windows tools that I can use to monitor connections to databases on specific ports?

thanks

Hi,

open ports can be monitored using the commandline tool netstat -a.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

can pocpet pc direct connect to sql server 2005?

i plan to upgrade sql express to sql 2005 enterprise.

if i upgrade to enterprise can

i direct connect to sql server 2005, is it need to install other

software on pocket pc or on my server?

thank you

if you are creating a .NET Compact Framework application for your mobile device, then yes, you can use the System.Data.SqlClient namespace to execute queries directly against SQL Server 2005 Enterprise.

Darren

Can OWC and ASP.NET be used to connect to an OLAP cube running on SQL Server 2005 ?

Hello, I'm from Romania and I have a small problem. I recently found on MSDN an articol and an ASP.NET project showing how to browse an OLAP cube from a web page, using OWC controls. The cube was built using Analysis Services for SQL Server 2000.

My question is can the same be done with a cube running on SQL Server 2005 (browse it from ASP.NET page using OWC) ? If so, can anyone please give a link to an tutorial or sample project ?
Or if not, please offer a solution on how to browse an OLAP cube from SQL Server
2005 from ASP.NET.

Thanks.

For the client application using OWC all you need to do is to install new version of the AS OLEDB provider. OWC can work with both AS200 and AS2005. Same goes for Excel and all major Analysis Services clients.

You can install "Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider " from http://www.microsoft.com/downloads/details.aspx?FamilyID=df0ba5aa-b4bd-4705-aa0a-b477ba72a9cb&DisplayLang=en

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi. It's me again, I have downloaded and installed all necessary stuff, and project runs seems to run fine, but the Office Web Control says it cannot find the object specified by me.

Here's the OLAPconnection string :

value="Provider=MSOLAP.2;Data Source=http://localhost/elena;Initial Catalog=Aplicatie LogyCars;"

Here is the block of code where i attempt to connect ;

Try

Dim objPT As PivotTableClass = New PivotTableClass

objPT.ConnectionString = strOLAPConn

'strDataMember = "CubLogyCar"

strDataMember = "Cub LogyCar"

objPT.DataMember = strDataMember

m_XML = objPT.XMLData

objPT = Nothing

Catch err As Exception

m_XML = "<err>" & err.Source & " - " & err.Message & "</err>"

Finally

End Try

Return (m_XML)

End Function

There's no error, but still does not connect. "Cub LogyCar" is the name of the OLAP cube buuilt inside the Aplicatie LogyCars solution. Both of them are correctly written in code and web.config file.

Any Suggestions ?

|||For Analysis Service 2005, the provider should be MSOLAP.3

Can OWC and ASP.NET be used to connect to an OLAP cube running on SQL Server 2005 ?

Hello, I'm from Romania and I have a small problem. I recently found on MSDN an articol and an ASP.NET project showing how to browse an OLAP cube from a web page, using OWC controls. The cube was built using Analysis Services for SQL Server 2000.

My question is can the same be done with a cube running on SQL Server 2005 (browse it from ASP.NET page using OWC) ? If so, can anyone please give a link to an tutorial or sample project ?
Or if not, please offer a solution on how to browse an OLAP cube from SQL Server
2005 from ASP.NET.

Thanks.

For the client application using OWC all you need to do is to install new version of the AS OLEDB provider. OWC can work with both AS200 and AS2005. Same goes for Excel and all major Analysis Services clients.

You can install "Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider " from http://www.microsoft.com/downloads/details.aspx?FamilyID=df0ba5aa-b4bd-4705-aa0a-b477ba72a9cb&DisplayLang=en

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi. It's me again, I have downloaded and installed all necessary stuff, and project runs seems to run fine, but the Office Web Control says it cannot find the object specified by me.

Here's the OLAPconnection string :

value="Provider=MSOLAP.2;Data Source=http://localhost/elena;Initial Catalog=Aplicatie LogyCars;"

Here is the block of code where i attempt to connect ;

Try

Dim objPT As PivotTableClass = New PivotTableClass

objPT.ConnectionString = strOLAPConn

'strDataMember = "CubLogyCar"

strDataMember = "Cub LogyCar"

objPT.DataMember = strDataMember

m_XML = objPT.XMLData

objPT = Nothing

Catch err As Exception

m_XML = "<err>" & err.Source & " - " & err.Message & "</err>"

Finally

End Try

Return (m_XML)

End Function

There's no error, but still does not connect. "Cub LogyCar" is the name of the OLAP cube buuilt inside the Aplicatie LogyCars solution. Both of them are correctly written in code and web.config file.

Any Suggestions ?

|||For Analysis Service 2005, the provider should be MSOLAP.3

Can not run SQL Server 2005 Upgrade Advisor on server that does not use the standard port

I tried creating an alias to the server to get it to connect to analyze the server but it will not recognize the SQL 2000 server as a valid server to analyze. I can use the alias to connect in EM or SSMS. Any ideas? The server is not clustered and is at SP4. I've connected to several others in my environment but this one is causing me grief!

Thanks,

Linda

After trying several other things, insuing I had the correct permissions on the destination server, one issue was discovered and that was I had permissions on the instance of SQL server I wanted to look at but not the defautl. Adding me did not fix the problem.

The fix actually came using an alias for the full default instance name and not using the "detect" button on the server entry screen. The instance name also had to be manually typed in. This worked after setting up an alias to the full instance name and not just the server name for the default instance.

Can not remotely connect to instance of sql server 2000

I had a big problem on connecting sqlserver remotely from other machines on the network .....

From any computer in the network i wanna to register the instance of the sqlserver from the enterprise manager ..... the server instance doesn't appear within the available sqlserver list (the servername which equal to my machine is the only one that appear) ..... when i manualy write the servername\alias manually and i choose the connection type and then i write sqlserver username and password and then finish he give a message to me that access denied or sql server doesn't exist ... !!

by the way from the local machine i registered the local instance of sqlserver successfully and successfully i access the Databases .....

To be noted:

I previously uninstalled this alias and i then i reinstalled it again with the same name and i attached the previously exists Databes.

in the same time i installed on the same machine sqlserver 2005 connectivity clients not the server itself.

Why are you using aliases? Do select @.@.servername, and tell me if this is the exact name you're trying to connect to via enterprise manager.|||

thank you for trying to help me,

I am using an alias from a long time and it was working good until i uninstalled the server and installed it agian .......

when i make "select @.@.servername" it return back "magedsalah\maged" and as i told before it works well on the local machine where i can connect with the enterprise manager to magedsalah\maged without any problems ......

the problem when anybody wanna to register magedsalah\maged in the enterprise manager of another computer the magedsalah\maged doesn't appear in the servers list what appear is magedsalah and it can't be registered and sometimes and some there is nothing appear at all.....

for further details plz refer to original message in the thread.....

thanks

|||Did you ever figure out the solution to this, I'm having the exact same problem, it occured after I installed Sql 2005, and now i'm using named instances.|||

Hi,

After i trapped in solving this problem ..... i removed the existing sql server 2000 where i use the alias and then i installed it again without alias (the default case in setup) ..... then i reattached my databases ......... and it works fine now

|||

I ended up doing the same thing too, and mine works too now. There must be a trick to making it work with alias'/instance names too though, oh well.

Thanks

can not remote connect SQL 2000

Hello,
We have 3 SQL servers.
Server01 Win 2003 w/SQL 2000 192.168.1.1
Server02 Win 2003 w/SQL 2000 192.168.1.2
Server03 Win 2003 w/SQL 2005 192.168.1.3
Server02 can see Server01 and Server03.
Server01 and Server03 can find each other but can not see Server02.
I add 192.168.1.2 in Server03 SQL native client configuration.
The server03 error message said 'the SQL does not allow remote connection'
Whe I check Server02 SQL property, the remote connection is checked.
How can I fix this problem?
Thanks
It's more than just visibility. As I discuss in Chapter 9, you'll need to
enable the protocols and (in the case of SQL Server 2005) the SQL Browser
service to expose SQL Server to the network.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Newbie" <Newbie@.discussions.microsoft.com> wrote in message
news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
> Hello,
> We have 3 SQL servers.
> Server01 Win 2003 w/SQL 2000 192.168.1.1
> Server02 Win 2003 w/SQL 2000 192.168.1.2
> Server03 Win 2003 w/SQL 2005 192.168.1.3
> Server02 can see Server01 and Server03.
> Server01 and Server03 can find each other but can not see Server02.
> I add 192.168.1.2 in Server03 SQL native client configuration.
> The server03 error message said 'the SQL does not allow remote connection'
> Whe I check Server02 SQL property, the remote connection is checked.
> How can I fix this problem?
> Thanks
|||Hello,
My question is both SQL2000 can see SQL2005, but SQL2005 can not connect one
of SQL2000.
Thanks
"William (Bill) Vaughn" wrote:

> It's more than just visibility. As I discuss in Chapter 9, you'll need to
> enable the protocols and (in the case of SQL Server 2005) the SQL Browser
> service to expose SQL Server to the network.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Newbie" <Newbie@.discussions.microsoft.com> wrote in message
> news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
>
>

can not remote connect SQL 2000

Hello,
We have 3 SQL servers.
Server01 Win 2003 w/SQL 2000 192.168.1.1
Server02 Win 2003 w/SQL 2000 192.168.1.2
Server03 Win 2003 w/SQL 2005 192.168.1.3
Server02 can see Server01 and Server03.
Server01 and Server03 can find each other but can not see Server02.
I add 192.168.1.2 in Server03 SQL native client configuration.
The server03 error message said 'the SQL does not allow remote connection'
Whe I check Server02 SQL property, the remote connection is checked.
How can I fix this problem?
ThanksIt's more than just visibility. As I discuss in Chapter 9, you'll need to
enable the protocols and (in the case of SQL Server 2005) the SQL Browser
service to expose SQL Server to the network.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Newbie" <Newbie@.discussions.microsoft.com> wrote in message
news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
> Hello,
> We have 3 SQL servers.
> Server01 Win 2003 w/SQL 2000 192.168.1.1
> Server02 Win 2003 w/SQL 2000 192.168.1.2
> Server03 Win 2003 w/SQL 2005 192.168.1.3
> Server02 can see Server01 and Server03.
> Server01 and Server03 can find each other but can not see Server02.
> I add 192.168.1.2 in Server03 SQL native client configuration.
> The server03 error message said 'the SQL does not allow remote connection'
> Whe I check Server02 SQL property, the remote connection is checked.
> How can I fix this problem?
> Thanks|||Hello,
My question is both SQL2000 can see SQL2005, but SQL2005 can not connect one
of SQL2000.
Thanks
"William (Bill) Vaughn" wrote:

> It's more than just visibility. As I discuss in Chapter 9, you'll need to
> enable the protocols and (in the case of SQL Server 2005) the SQL Browser
> service to expose SQL Server to the network.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Newbie" <Newbie@.discussions.microsoft.com> wrote in message
> news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
>
>