connect to New instance on SQL Server

I have install a new instance of SQL Server and I can
connect to the new instance inside the network. But we
have users who coonect to SQL Server from Remote location
using VPN and they cannot connect to this new sql
instance, the error this 'server not found'.
They are able to connect to default instance.
Thanks in advance.
TomHow about if they use the Client Network Utility to set up an alias for the
server without a backslash in it and specify the port (if using TCP/IP).
Also make sure their MDAC version is 2.6 or higher and check whether the VPN
allows UDP 1434.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"tom" <t@.gg.com> wrote in message
news:00e301c377ad$88a88960$a101280a@.phx.gbl...
I have install a new instance of SQL Server and I can
connect to the new instance inside the network. But we
have users who coonect to SQL Server from Remote location
using VPN and they cannot connect to this new sql
instance, the error this 'server not found'.
They are able to connect to default instance.
Thanks in advance.
Tom

Connect to Network SQL2k5 Database - ERROR

Hi,
eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also installed
on the same machine. When I started Microsoft SQL Server Management Studio
and tried to connect to another database running SQL 2005 using Windows
Authentication, I got following error.
TITLE: Microsoft SQL Server Management Studio
--
Unable to cast COM object of type 'System.__ComObject' to interface type
'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation failed
because the QueryInterface call on the COM component for the interface with
IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the following
error: No such interface supported (Exception from HRESULT: 0x80004002
(E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
--
Although, this error does not affect connection to the database. It connects
successfully and I am able to perform other stuff too. Just curious, why
this error is coming.
Any ideas why am I getting this kind of error.
Regards,
AtulLooks like you have problem with Visual Studio. Try to connect your database
from visual studio. Might be your installation file is corrupt or improper
installation.
--
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"Atul" wrote:
> Hi,
> eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also installed
> on the same machine. When I started Microsoft SQL Server Management Studio
> and tried to connect to another database running SQL 2005 using Windows
> Authentication, I got following error.
> TITLE: Microsoft SQL Server Management Studio
> --
> Unable to cast COM object of type 'System.__ComObject' to interface type
> 'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation failed
> because the QueryInterface call on the COM component for the interface with
> IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the following
> error: No such interface supported (Exception from HRESULT: 0x80004002
> (E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
> --
> Although, this error does not affect connection to the database. It connects
> successfully and I am able to perform other stuff too. Just curious, why
> this error is coming.
> Any ideas why am I getting this kind of error.
> Regards,
> Atul
>
>|||While installing SQL 2005, I did not give DataBase Instance name. Now when I
try to connect to local SQL 2005 database (I dont know where the MDF files
have been created for the same), it fails to connect, instead it connects to
SQL 2000 Database server.
This is another problem I am facing.
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:4F2D2233-BDDE-47FB-BB1C-7ED76E1D3359@.microsoft.com...
> Looks like you have problem with Visual Studio. Try to connect your
> database
> from visual studio. Might be your installation file is corrupt or improper
> installation.
> --
> Thanks,
> Sree
> [Please specify the version of Sql Server as we can save one thread and
> time
> asking back if its 2000 or 2005]
>
> "Atul" wrote:
>> Hi,
>> eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also
>> installed
>> on the same machine. When I started Microsoft SQL Server Management
>> Studio
>> and tried to connect to another database running SQL 2005 using Windows
>> Authentication, I got following error.
>> TITLE: Microsoft SQL Server Management Studio
>> --
>> Unable to cast COM object of type 'System.__ComObject' to interface type
>> 'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation
>> failed
>> because the QueryInterface call on the COM component for the interface
>> with
>> IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the following
>> error: No such interface supported (Exception from HRESULT: 0x80004002
>> (E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
>> --
>> Although, this error does not affect connection to the database. It
>> connects
>> successfully and I am able to perform other stuff too. Just curious, why
>> this error is coming.
>> Any ideas why am I getting this kind of error.
>> Regards,
>> Atul
>>

Connect to Network SQL2k5 Database - ERROR

Hi,
eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also installed
on the same machine. When I started Microsoft SQL Server Management Studio
and tried to connect to another database running SQL 2005 using Windows
Authentication, I got following error.
TITLE: Microsoft SQL Server Management Studio
Unable to cast COM object of type 'System.__ComObject' to interface type
'Microsoft.VisualStudio.OLE.Interop.IServiceProvid er'. This operation failed
because the QueryInterface call on the COM component for the interface with
IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the following
error: No such interface supported (Exception from HRESULT: 0x80004002
(E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
Although, this error does not affect connection to the database. It connects
successfully and I am able to perform other stuff too. Just curious, why
this error is coming.
Any ideas why am I getting this kind of error.
Regards,
Atul
Looks like you have problem with Visual Studio. Try to connect your database
from visual studio. Might be your installation file is corrupt or improper
installation.
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"Atul" wrote:

> Hi,
> eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also installed
> on the same machine. When I started Microsoft SQL Server Management Studio
> and tried to connect to another database running SQL 2005 using Windows
> Authentication, I got following error.
> TITLE: Microsoft SQL Server Management Studio
> --
> Unable to cast COM object of type 'System.__ComObject' to interface type
> 'Microsoft.VisualStudio.OLE.Interop.IServiceProvid er'. This operation failed
> because the QueryInterface call on the COM component for the interface with
> IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the following
> error: No such interface supported (Exception from HRESULT: 0x80004002
> (E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
> --
> Although, this error does not affect connection to the database. It connects
> successfully and I am able to perform other stuff too. Just curious, why
> this error is coming.
> Any ideas why am I getting this kind of error.
> Regards,
> Atul
>
>
|||While installing SQL 2005, I did not give DataBase Instance name. Now when I
try to connect to local SQL 2005 database (I dont know where the MDF files
have been created for the same), it fails to connect, instead it connects to
SQL 2000 Database server.
This is another problem I am facing.
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:4F2D2233-BDDE-47FB-BB1C-7ED76E1D3359@.microsoft.com...[vbcol=seagreen]
> Looks like you have problem with Visual Studio. Try to connect your
> database
> from visual studio. Might be your installation file is corrupt or improper
> installation.
> --
> Thanks,
> Sree
> [Please specify the version of Sql Server as we can save one thread and
> time
> asking back if its 2000 or 2005]
>
> "Atul" wrote:

Connect to Network SQL2k5 Database - ERROR

Hi,
eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also installed
on the same machine. When I started Microsoft SQL Server Management Studio
and tried to connect to another database running SQL 2005 using Windows
Authentication, I got following error.
TITLE: Microsoft SQL Server Management Studio
--
Unable to cast COM object of type 'System.__ComObject' to interface type
'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation failed
because the QueryInterface call on the COM component for the interface with
IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the followin
g
error: No such interface supported (Exception from HRESULT: 0x80004002
(E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
Although, this error does not affect connection to the database. It connects
successfully and I am able to perform other stuff too. Just curious, why
this error is coming.
Any ideas why am I getting this kind of error.
Regards,
AtulLooks like you have problem with Visual Studio. Try to connect your database
from visual studio. Might be your installation file is corrupt or improper
installation.
--
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and
time
asking back if its 2000 or 2005]
"Atul" wrote:

> Hi,
> eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also installed
> on the same machine. When I started Microsoft SQL Server Management Studio
> and tried to connect to another database running SQL 2005 using Windows
> Authentication, I got following error.
> TITLE: Microsoft SQL Server Management Studio
> --
> Unable to cast COM object of type 'System.__ComObject' to interface type
> 'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation fail
ed
> because the QueryInterface call on the COM component for the interface wit
h
> IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the follow
ing
> error: No such interface supported (Exception from HRESULT: 0x80004002
> (E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
> --
> Although, this error does not affect connection to the database. It connec
ts
> successfully and I am able to perform other stuff too. Just curious, why
> this error is coming.
> Any ideas why am I getting this kind of error.
> Regards,
> Atul
>
>|||While installing SQL 2005, I did not give DataBase Instance name. Now when I
try to connect to local SQL 2005 database (I dont know where the MDF files
have been created for the same), it fails to connect, instead it connects to
SQL 2000 Database server.
This is another problem I am facing.
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:4F2D2233-BDDE-47FB-BB1C-7ED76E1D3359@.microsoft.com...[vbcol=seagreen]
> Looks like you have problem with Visual Studio. Try to connect your
> database
> from visual studio. Might be your installation file is corrupt or improper
> installation.
> --
> Thanks,
> Sree
> [Please specify the version of Sql Server as we can save one thread an
d
> time
> asking back if its 2000 or 2005]
>
> "Atul" wrote:
>

Connect to MSDE with Limited User (not using sql authentication)

I have an MSDE installation that I need to connect to within a C# .NET
project as a Limited User (from the same machine, not via the network)
The MSDE instance is not in sql authentication mode, only windows
authentication. Is this possible? I've used the
'Trusted_Connection=True;' in the connection string, but a login fails
for the user with an error like:
"Cannot open database in login 'testdatabase'. Login fails. Login
failed for wkstn\limiteduser"
Do I need to grant any (additional) rights to the database itself?
Thanks for your help,
Tom
You can=B4t mix up the keyword "USER ID" and Trusted_connection, if you
choose "User ID" (SQL Server auth.) SQL Server will use SQL Server
authentication regardless of the Trusted_connection settings, see more
details here:
http://msdn.microsoft.com/library/de...n-us/adminsql=
/ad_security_47u6.asp
But you can (as you are working with C#) create a impersonated context
and connect with this...
http://www.codeproject.com/csharp/cpimpersonation1.asp
..=2E.and connect with this.
HTH, jens Suessmeyer.

Connect to enterprise manager

WIthin out network were all having issues connecting to SQL server, e.g. it
would allows connection when we can intermitadley connect.
Are the any know firewall issues or other known bugs?Hi,
Might be because of slow network, Try executing the below command from your
cleint PC
Ping <SQL Server IP Address> -t
If you get contineous "Request time out", then inform ur system / network
admin.
Thanks
Hari
MCDBA
"Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> WIthin out network were all having issues connecting to SQL server, e.g.
> it
> would allows connection when we can intermitadley connect.
> Are the any know firewall issues or other known bugs?|||Hari,
Seems as if it could be that. DB on on internal netowrk are fine. But the
problem db is with our hositng compnay: we have a 2 Meg brodband line
(operating a 1.6mbit/sec).
Any suggest of what I can say to our hositng company? I know our IP are in
there firewall, and thus sometimes we can connect; would a firewall with an
ISP tend to stop ping's?
Other options could be our router or our ISP.
THanks for you help on this!
regards
MAtthew.
"Hari Prasad" wrote:
> Hi,
> Might be because of slow network, Try executing the below command from your
> cleint PC
> Ping <SQL Server IP Address> -t
> If you get contineous "Request time out", then inform ur system / network
> admin.
> Thanks
> Hari
> MCDBA
> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> > WIthin out network were all having issues connecting to SQL server, e.g.
> > it
> > would allows connection when we can intermitadley connect.
> >
> > Are the any know firewall issues or other known bugs?
>
>|||Hi Matthew
If you're trying to ping a server at your ISP, it can very well be that they
don't allow pinging. In most cases pinging is blocked from outside a
firewall - not only on ISP's but also on most other companies.
I'd suggest that you call your ISP and talk to them about this issue because
you'd need to have the proper ports open to get into your SQL server. I
don't know if they will allow this or not, but if not you might be able to
do it via a VPN connection.
Regards
Steen
Matthew Burgess wrote:
> Hari,
> Seems as if it could be that. DB on on internal netowrk are fine. But
> the problem db is with our hositng compnay: we have a 2 Meg brodband
> line (operating a 1.6mbit/sec).
> Any suggest of what I can say to our hositng company? I know our IP
> are in there firewall, and thus sometimes we can connect; would a
> firewall with an ISP tend to stop ping's?
> Other options could be our router or our ISP.
> THanks for you help on this!
> regards
> MAtthew.
> "Hari Prasad" wrote:
>> Hi,
>> Might be because of slow network, Try executing the below command
>> from your cleint PC
>> Ping <SQL Server IP Address> -t
>> If you get contineous "Request time out", then inform ur system /
>> network admin.
>> Thanks
>> Hari
>> MCDBA
>> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
>> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
>> WIthin out network were all having issues connecting to SQL server,
>> e.g. it
>> would allows connection when we can intermitadley connect.
>> Are the any know firewall issues or other known bugs?|||I got a similar problem in my network but in my case the network connection
goes well until the user opens Enterprise Manager and start working. In some
moment the network connection is lost, PINGing the server will not respond.
My network is not a slow one. This problems occurs for more than one user.
Will you please indicate me how you resolved the problem or any workaround
for this? I am almost decided to format that server with all the work that it
implies and its impact on my users
Thanks
César
> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
> > Hari,
> >
> > Seems as if it could be that. DB on on internal netowrk are fine. But
> > the problem db is with our hositng compnay: we have a 2 Meg brodband
> > line (operating a 1.6mbit/sec).
> >
> > Any suggest of what I can say to our hositng company? I know our IP
> > are in there firewall, and thus sometimes we can connect; would a
> > firewall with an ISP tend to stop ping's?
> >
> > Other options could be our router or our ISP.
> >
> > THanks for you help on this!
> >
> > regards
> >
> > MAtthew.
> >
> > "Hari Prasad" wrote:
> >
> >> Hi,
> >>
> >> Might be because of slow network, Try executing the below command
> >> from your cleint PC
> >>
> >> Ping <SQL Server IP Address> -t
> >>
> >> If you get contineous "Request time out", then inform ur system /
> >> network admin.
> >>
> >> Thanks
> >> Hari
> >> MCDBA
> >>
> >> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> >> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> >> WIthin out network were all having issues connecting to SQL server,
> >> e.g. it
> >> would allows connection when we can intermitadley connect.
> >>
> >> Are the any know firewall issues or other known bugs?
>
>|||I have a similar problem. The network connection is OK but when the user
enters Enterprise manager and starts working with some DTS, the connection
with the server is lost. PINGing the server do not respond. It happens in
more than one user. I have changed the redundant NIC but it remains the same.
Will you please give me a hint how did you manage to solve it or if you
tried any workaround for this?
"Steen Persson" wrote:
> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
> > Hari,
> >
> > Seems as if it could be that. DB on on internal netowrk are fine. But
> > the problem db is with our hositng compnay: we have a 2 Meg brodband
> > line (operating a 1.6mbit/sec).
> >
> > Any suggest of what I can say to our hositng company? I know our IP
> > are in there firewall, and thus sometimes we can connect; would a
> > firewall with an ISP tend to stop ping's?
> >
> > Other options could be our router or our ISP.
> >
> > THanks for you help on this!
> >
> > regards
> >
> > MAtthew.
> >
> > "Hari Prasad" wrote:
> >
> >> Hi,
> >>
> >> Might be because of slow network, Try executing the below command
> >> from your cleint PC
> >>
> >> Ping <SQL Server IP Address> -t
> >>
> >> If you get contineous "Request time out", then inform ur system /
> >> network admin.
> >>
> >> Thanks
> >> Hari
> >> MCDBA
> >>
> >> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> >> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> >> WIthin out network were all having issues connecting to SQL server,
> >> e.g. it
> >> would allows connection when we can intermitadley connect.
> >>
> >> Are the any know firewall issues or other known bugs?
>
>

Connect to enterprise manager

WIthin out network were all having issues connecting to SQL server, e.g. it
would allows connection when we can intermitadley connect.
Are the any know firewall issues or other known bugs?
Hi,
Might be because of slow network, Try executing the below command from your
cleint PC
Ping <SQL Server IP Address> -t
If you get contineous "Request time out", then inform ur system / network
admin.
Thanks
Hari
MCDBA
"Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
> WIthin out network were all having issues connecting to SQL server, e.g.
> it
> would allows connection when we can intermitadley connect.
> Are the any know firewall issues or other known bugs?
|||Hari,
Seems as if it could be that. DB on on internal netowrk are fine. But the
problem db is with our hositng compnay: we have a 2 Meg brodband line
(operating a 1.6mbit/sec).
Any suggest of what I can say to our hositng company? I know our IP are in
there firewall, and thus sometimes we can connect; would a firewall with an
ISP tend to stop ping's?
Other options could be our router or our ISP.
THanks for you help on this!
regards
MAtthew.
"Hari Prasad" wrote:

> Hi,
> Might be because of slow network, Try executing the below command from your
> cleint PC
> Ping <SQL Server IP Address> -t
> If you get contineous "Request time out", then inform ur system / network
> admin.
> Thanks
> Hari
> MCDBA
> "Matthew Burgess" <MatthewBurgess@.discussions.microsoft.com> wrote in
> message news:E9A0AF8C-618F-4ECC-9775-0427625883B1@.microsoft.com...
>
>
|||Hi Matthew
If you're trying to ping a server at your ISP, it can very well be that they
don't allow pinging. In most cases pinging is blocked from outside a
firewall - not only on ISP's but also on most other companies.
I'd suggest that you call your ISP and talk to them about this issue because
you'd need to have the proper ports open to get into your SQL server. I
don't know if they will allow this or not, but if not you might be able to
do it via a VPN connection.
Regards
Steen
Matthew Burgess wrote:[vbcol=seagreen]
> Hari,
> Seems as if it could be that. DB on on internal netowrk are fine. But
> the problem db is with our hositng compnay: we have a 2 Meg brodband
> line (operating a 1.6mbit/sec).
> Any suggest of what I can say to our hositng company? I know our IP
> are in there firewall, and thus sometimes we can connect; would a
> firewall with an ISP tend to stop ping's?
> Other options could be our router or our ISP.
> THanks for you help on this!
> regards
> MAtthew.
> "Hari Prasad" wrote:
|||I got a similar problem in my network but in my case the network connection
goes well until the user opens Enterprise Manager and start working. In some
moment the network connection is lost, PINGing the server will not respond.
My network is not a slow one. This problems occurs for more than one user.
Will you please indicate me how you resolved the problem or any workaround
for this? I am almost decided to format that server with all the work that it
implies and its impact on my users
Thanks
César
> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
>
>
|||I have a similar problem. The network connection is OK but when the user
enters Enterprise manager and starts working with some DTS, the connection
with the server is lost. PINGing the server do not respond. It happens in
more than one user. I have changed the redundant NIC but it remains the same.
Will you please give me a hint how did you manage to solve it or if you
tried any workaround for this?
"Steen Persson" wrote:

> Hi Matthew
> If you're trying to ping a server at your ISP, it can very well be that they
> don't allow pinging. In most cases pinging is blocked from outside a
> firewall - not only on ISP's but also on most other companies.
> I'd suggest that you call your ISP and talk to them about this issue because
> you'd need to have the proper ports open to get into your SQL server. I
> don't know if they will allow this or not, but if not you might be able to
> do it via a VPN connection.
> Regards
> Steen
>
> Matthew Burgess wrote:
>
>

Connect SQL Server to Oracle 9i

I need to connect SQL Server 2000 to an Oracle database on another network for which we have permissions. The Oracle tech (they have no dba...a vendor set all of this up) created a schema for us and now I need to access it. They have provided a username and a password.

for example:

uname = test
pwd = testpwd
oracle box = ias4_192.x.x.x

In SQL Server how do I make this happen? Do I need to set up an ODBC connection, sp_addlinkedserver, etc. etc. I posted to another forum and was told something about a tnsnames.ora file and possibly a listener.ora file?!? Both the Oracle guy and myself are complete idiots when it comes to this kinda stuff. We each vaguely understand our own system but this heterogenous stuff is killing us! Please help. We need a step-by-step outline to make this happen. Any help would be GREATLY appreciated. Thanks!In order to connect the SQL Server via sp_addlinkedserver, you need to establish connectivity to the Oracle server.

You need to install the Oracle drivers onto the SQL Server (do a minimum install, just the drivers and the network connectivity tools).

Then you need to open your Oracle Network assistant and configure the connection settings (hostname or ip address and port number). You will need to give these settings a name (called a Net Service Name, I think).

Once these steps are complete, then you can use sp_addlinkedserver to specify the correct settings for SQL Server to "see" the Oracle server. You can also add it through the graphical utility in SQL's Enterprise Manager (under Security/Linked Servers). This latter method may be a bit easier for novices.

Please note, these are the steps that I have used for both Oracle 7.x and Oracle 8.x. They may be slightly different for 9i.

HTH,

hmscott

Connect SQL Server- Network

Hi,

I have 2 SQL 2K Servers set up on my home network. Both PC's are running Windows XP and as far as I can tell are configured identically, however I can connect to the Server A from PC B but not Server B from PC A (both work fine when I am on the same machine I try to connect to). Any ideas anyone, the error message I am getting is attached.Could one server be configured to listen on named pipes, but not the other? Could one client be configured to use Named Pipes as its default client, while the other was configured to use TCP/IP? My guess is that one of the machines has a problem with either the client or the server network configuration.

-PatP|||If I understand you correctly you are able to connect from A to B but not from B to A, both A and B have an installation of SQLServer up and running. From the errormessage attached and the fact that you are able to setup a connection from A to B, I'd look for network issues on B. Are you able to ping A from B? Is A listed in the network neighbourhood on B? On A, is the SQL Agent running?
EDIT: sniped on a friday!|||Ok solved it, A had not had file and print sharing set up, didn't even think to check this as I could see it on the network, so assumed it was setup correctly!

Confirming encryption when Replication is over SSL

We are using SSL to secure merge replication from client to server. Though
we can check through network monitor whether data is encrypted for normal
query to database, for replication how can we confirm that data is
encrypted - as data is already being send in binary format.
Could you please let me know how to check if data is encrypted when we do
replication over SSL.
Thanks,
Ganesh.Same process Ganesh. Run one of the Agents in Replication such as the
Distribution Agent and verify that the data being sent is encrypted using a
network sniffer or Microsoft Network Monitor. Running SQL Profiler will
show the data un-encrypted.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Kevin.
Ganesh.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:c4bYLAiLEHA.2364@.cpmsftngxa10.phx.gbl...
> Same process Ganesh. Run one of the Agents in Replication such as the
> Distribution Agent and verify that the data being sent is encrypted using
a
> network sniffer or Microsoft Network Monitor. Running SQL Profiler will
> show the data un-encrypted.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

Configuring SQLMail on Standalone PC

Hi,
I want to try some programs using SQL Mail on my Local/Standalone PC.
I do not have a network connection and only have a dialup connection.
How do I setup/configure SQLMail in SQL2000? When I read about it, it
says that I need to have mailbox/profile setup. But I don't have
Exchange Server too.
Somehow I got hold of Exchange Server 2000 120-Eval edition. But I am
unable to install the same, because it says that it needs Active
Directory to be setup first.
Now my Win2K Server is already installed and I don't have Active
Directory setup. Is it possible to setup Active Directory on a
Local/Standalone PC which doesn't have Network card.
Please let me know if there is any possible way to write and test some
programs on a Standalone Win2K Server with is not connected to any
server. What will be the prerequisites of Standalone PC to use
SQLMail locally for testing purpose.
Thanks,
KamleshCan you use SMTP instead? http://www.aspfaq.com/2403
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Kamlesh" <kamlesh2000@.yahoo.com> wrote in message
news:2644c0f6.0311212150.7bba5122@.posting.google.com...
> Hi,
> I want to try some programs using SQL Mail on my Local/Standalone PC.
> I do not have a network connection and only have a dialup connection.
> How do I setup/configure SQLMail in SQL2000? When I read about it, it
> says that I need to have mailbox/profile setup. But I don't have
> Exchange Server too.
> Somehow I got hold of Exchange Server 2000 120-Eval edition. But I am
> unable to install the same, because it says that it needs Active
> Directory to be setup first.
> Now my Win2K Server is already installed and I don't have Active
> Directory setup. Is it possible to setup Active Directory on a
> Local/Standalone PC which doesn't have Network card.
> Please let me know if there is any possible way to write and test some
> programs on a Standalone Win2K Server with is not connected to any
> server. What will be the prerequisites of Standalone PC to use
> SQLMail locally for testing purpose.
> Thanks,
> Kamlesh

configure sql server details

Hi everybody,

I'm installing a network monitoring tool (OpManager). During
installation I reached the following step: Configure the SQL Server
details.

Host Name: ?
Port: 1433
Database Name: xxx
User Name: ?
Password: ?

I don't know which host name I need to put in and also I don't know
which user name and password is required.

Please can anyone help me with this.

Thank you!(pearl146@.hotmail.com) writes:

Quote:

Originally Posted by

I'm installing a network monitoring tool (OpManager). During
installation I reached the following step: Configure the SQL Server
details.
>
Host Name: ?
Port: 1433
Database Name: xxx
User Name: ?
Password: ?
>
I don't know which host name I need to put in and also I don't know
which user name and password is required.
>
Please can anyone help me with this.

Since all this is information that is local to your site we cannot really
help you. But we can give some hints:

The host name is usually the machine which SQL Server is running on. If
you have SQL Server on a cluster, it's likely to be the virtual cluster
name. SQL Server can be installed with named instances, in case which
the server is accessed on the form "MACHINE\INSTANCE". I have no idea
what OpManager wants in this case, but since they ask for port number,
I would guess that they stll only want the machine name, and you would
have to use a different port number.

Username and password. By default, SQL Server is installed with
Windows Authentication. This means that when you log into SQL Server,
SQL Server gets your authentication information from Windows, and you
don't supply any user name or password at all. SQL Server can also be
configured for mixed authentication, so that SQL logins are accepted
as well. SQL Logins are username/password pairs.

What username you should specify in this case, I don't know. Probably
you need to create a login and give that the permissions needed by
OpManager. But if your server is not configured for mixed authentication,
there is all reason if you want to activate to run a certain application.
I would expect the app to work with Windows Authentication as well.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx